...
| Subtitle | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Apart from your router/firewall configuration (that we won't cover here) 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 | ||
|---|---|---|
|
...
| 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
dfglknsgldsnThis is the public IP address used for the RTP delivery. It means that this is the secured voice IP you want to use.
External SIP address
sdglknsdgThis is the public IP address used for the SIP delivery. It means that this is the IP you want to use for SIP signalling.
External port
sdlkgnsgkldIf you want to perform a PAT (Port Address Translation) in addition to the NAT, then please use this option to explain to the appliance which port number is used on the external interface for providing the encrypted SIP service.
2.4.6 Keep-alive Frequency
If you are using the appliance in an internal nekeep-alive option
Navbar