Topic Last Modified: 2012-09-21
Before you can deploy a SIP trunk, you and your service provider must exchange some basic connection information about your respective SIP trunk endpoints.
Get the following information for each ITSP gateway that you will connect to:
Fully qualified domain name (FQDN)
|The service provider may ask you to connect to more than one ITSP gateway. In that case, you must configure a connection between each ITSP gateway and each Mediation Server in your pool.|
The information you give to your service provider depends on your SIP trunk connection type:
For Multiprotocol Label Switching (MPLS) or private network connections, give the ITSP the publicly routable IP Address of the router in your perimeter network (also known as DMZ, demilitarized zone, and screened subnet). Verify that the gateway or Session Border Controller (SBC) at the ITSP can reach this address. Also give the ITSP the FQDN of your Mediation Server.
For virtual private network (VPN) connections, give the ITSP the IP address of your VPN server.
To determine whether you need a certificate for SIP trunking, check with your ITSP about protocol support:
If your ITSP supports Transmission Control Protocol (TCP) only, you do not need a certificate.
If your ITSP supports Transport Layer Security (TLS), the ITSP must provide you with a certificate.
|SIP works in conjunction with real-time transport protocol (RTP) or secure real-time transport protocol (SRTP), the protocols that manage the actual voice data in Voice over Internet Protocol (VoIP) calls.|
To implement the Lync Server side of the SIP trunk connection, follow these steps:
Using the Lync Server Topology Builder, create and configure the SIP domain topology. For details, see Define and Configure a Topology in Topology Builder in the Deployment documentation.
Using the Lync Server Control Panel, configure voice routing for the new SIP domain. For details, see Configuring Trunks in the Deployment documentation.
Test connectivity by using the Test-CsPstnOutboundCall cmdlet. For details, see the Lync Server Management Shell documentation or Help for Lync Server Management Shell.