NAT Configuration

The SIP Soft Switch supports most types of NAT servers and several combinations of placement SIP Soft Switch and endpoints with respect to the NAT.

STUN is required when Ivanti Voice is in a different NAT network than the softphone clients, and is used to properly identify the IP address to send data to the softphone clients. Ivanti Voice softphones (Communicator and Agent Dashboard) both support STUN. Ivanti provides a STUN server at VOIP-stun.sassit.com, which is configured as the default.

At a minimum, the Ivanti Voice softphone must be able to resolve the domain name of the STUN server, even if STUN is not in use. Failure to do so may result in the phone not registering properly or returning Busy signals. If your configuration does not support resolving external domain names and STUN is not required; you can alleviate the issue by using the following procedure to allow the Ivanti Voice server to provide a resolvable name.

STUN Server Settings

1.Back up the HostConfiguration.XML file from the data subdirectory of your Ivanti Voice installation.

2.Open the HostConfiguration.XML file in a text editor.

3.Find the section for VPSIPServer shown below:

<Application ServiceName="VPSIPServer" Type="SIPServer" ID="3" Autostart="true" Name="SIP Server">

  <Server MappedPort="60210" MappedHost="dev-voip.saasit.com"MappedStunPort="3478"MappedStunHost="VOIP-stun.saasit.com" />

</Application>

4.Edit the following items:

•Change the MappedSTUNHost setting to be the fully qualified domain name of the Ivanti Voice server, such as: VOIP1 or VOIP1.mycompany.com. It must be resolvable by all softphones.

•Change the MappedStunPort setting to be 5060.

5.In settings for Communicator, ensure that STUN is not checked in the STUN tab.