...
Apart from your router/firewall configuration (that we won't cover hereplease check PrivateGSM installation pre-requisites) and your network design/topology, from the PrivateServer point of view the only known thing is that the appliance is configured on a private IP address but the requests of the encrypted voice service are made to an external and public IP address. To avoid wrong replies the PrivateServer must know of this setup and be configured accordingly. Thus if you fall in the described scenario access to the "NAT Configuration" form (showed in
| Xref | ||
|---|---|---|
|
By default this option is disabled, so to enable it you first need to select "YES" in "NAT" option. If you have enabled the NAT then it's mandatory to configure the remaining options as well.
| Info | ||
|---|---|---|
| ||
The "Keep-alive Frequency" is part of a new feature that is not directly connected to the NAT setup. To better understand what a keep-alive is, please refer to PSOM 1.0 Accounts and Groups. |
External media address
This is the public IP address used for the RTP delivery. It means that this is the secured voice IP you want to use.
| Warning | ||
|---|---|---|
| ||
| Unless you need to specify for some reason a specific IP address for RTP, you'd better leave this field empty and let Asterisk do the job for you! |
External SIP address
This is the public IP address used for the SIP delivery. It means that this is the IP you want to use for SIP signalling.
...
If you are using the keep-alive option (please refer to PSOM 1.0 Accounts and Groups) then you may find this option handy. You can define here how many seconds should pass between each keep-alive request sent by the server to each client configured with the keep-alive option.
...