Configuring a Pure-IP SIP Trunk in Lync 2013

Transcription

1 Configuring a Pure-IP SIP Trunk in Lync 2013 Contents Configuring a Pure-IP SIP Trunk in Lync Introduction - Product version: Microsoft Lync Server Pure-IP SIP Trunk configuration tasks... 3 Example Pure-IP SIP Trunk connection details... 3 Lync configuration... 4 Modify and Publish your Lync Topology... 4 Create a Route in the Lync Server Control Panel... 6 Create a Dial Plan to Route Outbound Calls to the Pure-IP SIP Trunk Trunk Configuration Validate Routing Configuration Enable Users for Enterprise Voice Appendix A. Lync Log Analysis with Snooper B. Configuring Lync s Unassigned Numbers to Prevent Call Loops using all Channels

2 Figures Figure 1: Lync Topology - Mediation Pools... 4 Figure 2: Lync Topology - PSTN Gateway... 5 Figure 3: Lync Topology - Publishing Wizard... 6 Figure 4: Lync Control Panel - Route... 7 Figure 5: Lync Control Panel - Route -Associated PSTN Gateway... 8 Figure 6: Lync Control Panel - Route - Committing Changes... 9 Figure 7: Lync Control Panel - Routing/Failover... 9 Figure 8: Lync Control Panel - Dial Plan Global Figure 9: Lync Control Panel - Dial Plan - Prefix Plus Normalization Rule Figure 10: Lync Control Panel - Voice Policy Global Figure 11: Lync Control Panel - Voice Policy - Linking PSTN Usages and Routes Figure 12: Lync Control Panel - Voice Policy - Committed Figure 13: Lync Control Panel - Trunk Configuration Figure 14: Lync Control Panel - Trunk Configuration - Outbound failover timer Figure 15: Lync Control Panel - Voice Routing TEST Figure 16: Lync Control Panel - Voice Routing Test Result Figure 17: Lync Control Panel - Users Figure 18: Lync Control Panel - Enabling Users for Enterprise Voice Figure 19: Snooper Overview Figure 20: Snooper Menu Figure 21: Snooper SIP Ladder...20 Figure 22: Snooper SIP Message Details...20 Figure 23: Lync Control Panel - Unassigned Number Table Voice Feature Introduction - Product version: Microsoft Lync Server 2013 In this document we examine the implementation steps required to connect Microsoft Lync Server 2013 to Pure-IP using a Session Initiation Protocol (SIP) trunk. The SIP trunk configuration is simple with Pure-IP and depending on your firewall, provides an opportunity to connect the SIP trunk without a Session Border Controller (SBC). 2

3 Pure-IP SIP Trunk configuration tasks 1. Configure the external firewall to allow communication between Pure-IP and your Lync Server with the Mediation Server role. 2. Modify and publish your Lync topology. 3. Create a route in the Lync Server Control Panel. 4. Create a dial plan to route outbound calls to the Pure-IP SIP trunks. 5. Configure Trunk Configuration settings. 6. Validate routing configuration. 7. Configure users for Enterprise Voice. Example Pure-IP SIP Trunk connection details Table 1. Example Pure-IP Lync Trunk communication details Inbound traffic to Lync mediation Pure-IP IP address Protocol Port Range London VoIP platform SIP connection uksbccll.pure-ip.com TCP/TLS 5060 / 5067 London VoIP platform Media uksbccll.pure-ip.com UDP 20,000 60,000 Slough VoIP platform SIP connection uksbcld5.pure-ip.com TCP/TLS 5060 / 5067 Slough VoIP platform Media uksbcld5.pure-ip.com UDP 20,000 60,000 By default Lync uses Port 5068 for SIP over TCP and UDP range 50,000 to 59,999 for Media. Table 2. Pure-IP SIP Trunk communication settings Call Format E.164 with leading + ANI Presentation E.164 with leading + Codecs Supported G.711a, G.711u, G.729 DTMF Relay Pure IP UK Monitoring Server RFC /ICMP 3

4 Lync configuration Modify and Publish your Lync Topology Topology Builder is a Lync Server 2013 tool that manages the components within your environment. A single Lync Mediation Server can communicate with multiple PSTN gateways (in this case the Pure-IP SIP trunks). By combining multiple Lync Mediation Servers with multiple Pure-IP SIP trunks, a redundant solution can be built for minimal cost. For illustration purposes the example below shows a single gateway and route configuration. 1. To open Topology Builder > click Start > click All Programs > click Microsoft Lync Server 2013 and then click Lync Server Topology Builder. 2. Expand Mediation pools and select the Standard or Enterprise pool. Right-click the pool and select Edit Properties. Figure 1: Lync Topology - Mediation Pools 1. Enable TCP by checking the Enable TCP port box, and then modify the Listening ports value from 5068 to By default, Pure-IP sends SIP communication over TCP/5060. Some firewalls, such as the Cisco ASA, require the SIP communication to be sent over TCP/5060 or UDP/5060, in order to utilize the integrated SBC functionality. This value enables the Mediation Server to open a listening port on all interfaces on the Mediation Server (by default). 4

5 2. Under Shared Components, right click PSTN gateways and then click New IP/PSTN Gateway. Figure 2: Lync Topology - PSTN Gateway 3. Enter the Gateway FQDN or IP Address provided by Pure-IP, click Next twice, then select TCP, and then enter 5060 as the Listening port - in this example uksbccll.pure-ip.com and 5060 was entered. Click OK to save the configuration. Click OK again to close the Mediation pool properties. Note: A new PSTN gateway with the FQDN or IP Address entered in the previous step will automatically be displayed under PSTN gateways. 4. After completing the addition of the configuration changes, the topology must be published. Select Lync Server 2013, right-click, and select Publish topology. 5. In the Publish Topology dialog box, click next. After publishing is complete, review the status provided and click Finish to complete the process. 5

6 Figure 3: Lync Topology - Publishing Wizard 6. Close Lync Topology Builder. Create a Route in the Lync Server Control Panel After the topology is updated, define a route in the Lync Server Control Panel. This document covers only the implementation of a SIP trunk into a working Lync Server 2013 environment, meaning that Lync Server 2013 is functioning internally and externally with the exception of Enterprise Voice. 1. Launch the Lync Server Control Panel on the server 2. Click on Voice Routing, and then click Route. 3. By default, a route named Local Route is listed. Select the route, click Edit, and then click Delete. 4. Click New to create a new route. 6

7 Figure 4: Lync Control Panel - Route 5. Enter a name in the route, such as SIP trunk to Pure-IP, and an optional description. Scroll down to Build a Pattern to Match, and notice the default is set to '.*' or all calls. 6. The associated trunks list defines which PSTN gateways are defined in the Lync Server Topology Builder. Click Add to display the list. 7

8 Figure 5: Lync Control Panel - Route -Associated PSTN Gateway 7. Select the previously defined gateway, and click OK. 8. Under Associated PSTN Usages, click Select to open the Select PSTN Usage Record dialog box. 9. Select Long Distance from the list, and click OK. 10. Click OK to complete the creation of the new route. 11. To finalize the changes, click Commit, and click Commit All. 8

9 Figure 6: Lync Control Panel - Route - Committing Changes If both Pure-IP PSTN gateways/trunks are added to the same route, outbound calls will exhibit a round robin effect. This provides little control over outbound routing which may become necessary should either one of Pure-IP s geo-redundant VoIP platforms ever require maintenance or experience issues. For routing/gateway failover, we recommend you create two separate routes, one for each Pure-IP VoIP platform. The routing priority will be handled by the order of the routes in the routing list. Figure 7: Lync Control Panel - Routing/Failover 9

10 Create a Dial Plan to Route Outbound Calls to the Pure-IP SIP Trunk In a simple SIP trunk to Pure-IP configuration, creation of a dial plan to Pure-IP is simple and straightforward. All calls routed through the trunk must be in the E.164 format. Formatting is automated by the Normalization rules found in the Dial Plans. You may change or create additional Dial Plans, and normalize those rules to match your environment. 1. Click Dial Plan to display the current dial plans in the environment. Double-click the Global dial plan to open the dial plan properties. Figure 8: Lync Control Panel - Dial Plan Global 2. Scroll down to the Associated Normalization Rules. The Keep All rule is present by default. 3. Click New to open the New Normalization Rule window. 4. Enter a name in the rule, such as Keep All Prefix Plus, and an optional description. Scroll down to Length, select Any from the drop-down box. 0 digits to remove. + digits to add. 10

11 Figure 9: Lync Control Panel - Dial Plan - Prefix Plus Normalization Rule 5. Click OK to complete the creation of the normalization rule. The new rule is now listed in the rules list. 6. After the required normalization rules are created, click OK to complete the Dial Plan. Click Commit, and then select Commit All to save the normalization rules. 7. Click Voice Policy to update the Global policy. 8. Double-click Global to open the Edit Voice Policy - Global window. 11

12 Figure 10: Lync Control Panel - Voice Policy Global 9. Scroll down to Associated PSTN Usages, and click Select. 10. Select Long Distance from the Select PSTN Usage Record dialog box, and then click OK. 12

13 Figure 11: Lync Control Panel - Voice Policy - Linking PSTN Usages and Routes Note: Notice the Long Distance PSTN usage record is associated with the newly created SIP trunk to Pure-IP route - the glue that ties the route to the policy. 11. Click OK to close Voice Policy, click Commit, and then click Commit All to complete the changes. 13

14 Figure 12: Lync Control Panel - Voice Policy - Committed Trunk Configuration 1. In the Lync control panel > Voice Routing > click Trunk Configuration, double click Global Configuration and ensure Refer support is set to None, centralized media processing and enable forward call history is ticked while all other options are un-ticked (including enable outbound routing failover). 14

15 Figure 13: Lync Control Panel - Trunk Configuration Note: The above trunk configuration is a recommendation based upon support experience for common Lync trunk issues but may need to be amended depending on your particular needs. We advise setting Refer support to None as this has caused numerous issues with call transfer for many customer implementations. Ticking Enable forward call history provides additional SIP headers to ensure all call types are billed correctly. Un-ticking the Enable outbound routing failover timer on the Trunk Configuration tab prevents Lync from cancelling calls prematurely after 10 seconds. It is not unusual for calls to mobiles and international destinations to take longer than 10 seconds before a 18x response is returned (but entirely within SIP standards). 15

16 Figure 14: Lync Control Panel - Trunk Configuration - Outbound failover timer Validate Routing Configuration 1. When configuration is complete, validation is performed using the Lync Server Control Panel. At the top of the current window, select the down arrow to display the test case. Figure 15: Lync Control Panel - Voice Routing TEST 2. In the Dialled number box, enter any number, and then verify the normalization rule works as expected. The Results dialog box will indicate which Normalized Rule, Normalized number, First PSTN usage, and First route will be used when presented with the test number. Note: All numbers (local or long distance) will use the 'Long Distance' PSTN Usage in this current setup. PSTN usages are used to add calling restrictions and are not used in this example configuration. Figure 16: Lync Control Panel - Voice Routing Test Result 16

17 3. As per the above picture enter the number you want to test and press run, the results will be displayed and error messages if any. Enable Users for Enterprise Voice The final configuration step requires that users are enabled and configured with a unique Line URI. The Direct Inward Dialling (DID) numbers, provided by the SIP trunk provider, must be directly associated with the user accounts' Line URI Enterprise Voice properties within Lync Server Control Panel. Inbound communications are received in the E.164 format, so inbound call manipulation does not occur. When inbound calls are received, an automatic phone number lookup, based on the line URI of the user account is performed. If there is a match, the Mediation Server routes the call appropriately. 1. Click Users in the Lync Server Control Panel to change to the Users configuration. 2. The User Search window is blank until a query is made and results found. By clicking Find without any input, all enabled users are returned in the query. Figure 17: Lync Control Panel - Users 3. Double-click a user to edit the properties of the user. 4. Select the Telephony drop-down box and pick Enterprise Voice. 5. In the Line URI field, type the DID that you want to use in the E.164 format. This format starts with a plus sign (+) followed by the country code, area code, and phone number. An example of a valid line URI would be tel:

18 Figure 18: Lync Control Panel - Enabling Users for Enterprise Voice 6. Click Commit to complete the changes. 7. Wait for domain replication to occur. After the object properties replicate through Active Directory Domain Services, the system is ready for inbound and outbound calls. 18

19 Appendix A. Lync Log Analysis with Snooper Purpose: How to use Snooper.exe to assist with troubleshooting Lync server logs. Information: The Lync logs are in a standard text format and you can use Notepad.exe or any other programs that will allow you to open and read a text file. However, the Snooper.exe tool is designed to read and parse the logging output from the Lync logs. Snooper is included with the Lync Server 2013 Debug Tools that are available as a separate download. The Snooper.exe can be located on the network drive H:\3_Software+Products\Snooper.exe. The Lync Server 2013 Debug Tools can also be downloaded here: Snooper.exe The following screenshots show the tool s features Figure 19: Snooper Overview Figure 20: Snooper Menu 19

20 Snooper also has Flow Chart (call flow sip ladder) functionality, which allows you to follow and jump between SIP messages. Figure 21: Snooper SIP Ladder Click on any call flow arrow to get further details. Figure 22: Snooper SIP Message Details Additional Comments: Useful link: 20

21 B. Configuring Lync s Unassigned Number Table to Prevent Call Loops using all Call Channels Purpose: How to prevent unnecessary call channel usage often resulting in channel limits being breached and calls being blocked. This issue is caused by inbound calls looping between Pure-IP and customer Lync deployments, when the inbound numbers are not assigned to a user, response group or in the unassigned number table. This results in the unmatched inbound calls being re-routed back out the Pure-IP Trunk (forming the loop). This issue is described in the following link: Information: Either the number in question needs to be assigned to a user, response group or Microsoft Lync s unassigned number table needs to be configured in order the resolve the call loop issue. The unassigned number table can be configured using the information described in the following link: The unassigned number table feature is located in the Lync control panel under the Voice Features section. All number ranges owned by the customer should be configured in the unassigned number table feature as this feature is only used when the number is not assigned to a Lync user or response group. There is a known bug, which prevents the unassigned number table feature from working when the Trunk Configuration (in the Voice Routing section of the Lync control panel) has assigned pstn usages. This issue is described in the following link: 21

22 Figure 23: Lync Control Panel - Unassigned Number Table Voice Feature Additional Comments: The procedure to configure the unassigned number table feature is the same for both 2010 and 2013 deployments. Lync 2010 links: