Jump to: navigation, search

Creating a New PSTN Gateway

This section discusses the configuration on the Lync / Skype for Business Server that needs to be implemented so that the Genesys SIP Server can integrate with it. The prerequisite for the procedure described in this chapter is that Lync / Skype for Business needs to be deployed in the target network, and fielding voice calls through its Enterprise Voice option.

Purpose: To create a new public switched telephone network (PSTN) gateway. The SIP Server is seen by Lync / Skype for Business as a PSTN gateway that talks to the Mediation Server. PSTN gateways are configured in Lync / Skype for Business through the Topology Builder. The following screen shots that illustrate how to create a new PSTN gateway are taken from a Skype for Business deployment. Lync 2013 and 2010 have similar facilities.

1. Declare the host where SIP Server is running as the PSTN Gateway.

2. From the Skype for Business Server 2015 Topology Builder, go to Shared Components > PSTN gateways > New IP/PSTN Gateway.

3. Enter the FQDN of the SIP Server host.

LyncIntegTop.png

4. Define the root trunk:

  • Default trunk name – in the figure, g1-sngl-p.bep.com.
  • Listening port for IP/PSTN gateway: 5060 (this port corresponds to the value defined in the SIP Server option sip-port).
  • SIP Transport Protocol: TCP.
  • Associated Mediation Server: FQDN of Mediation Server.
  • Associated Mediation Server port: for example, 5068.

LyncIntegTop2.png

Important
If TCP is not offered as a SIP transport protocol during trunk definition, it means that it has not been enabled on the Mediation Server.

To enable TCP:

1. Go to Skype for Business Server 2015 > Mediation Pool > [FQDN of mediation pool] (as in the following figure):

LyncIntegTop3.png

2. Select the Enable TCP port check box (as shown below).

LyncIntegTop4.png

3. Publish the Topology.

Tip
When you publish the topology, you may have an alert in the Skype for Business Topology Builder if you have used an FQDN that was not declared as a computer in Active Directory. This may happen when you use a second A or a CNAME record used to declare the SIP Server, if it runs on the same host that UC Connector. This is not an error and can be ignored.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on June 27, 2016, at 16:15.