Enabling Users for Lync services

Enabling Users for Lync services 1) Login to collaborate.widevoice Server as admin user 2) Open Lync Server control Panel as Run As Administrator 3) Click on Users option and click Enable Users option 1 of 18

4) Click Add to open user search box. 2 of 18

5) Type the user name and click Find. Once you get the search result select the user and click Ok 6) Once user is selected and select Assign users to Pool option and select the value colaboratewidevoice.com and telephony option choose Enterprise Voice option and in Line URI enter user s extension number in this format tel:+1223870234 as shown below. 7) Click Enable to complete the process 3 of 18

Note: If you get any permission related or active directory related error that s because of the users security group or AD permission or replication issue. To overcome this you have to use Lync Shell Command to enable users 1) Login to LyncFE01 Server as Lyncadmin user 4 of 18

2) Open Lync server Management Shell as Run AS Administrator 3) Enter the below mentioned shell command To enable User Enable-CsUser -Identity "AD USER NAME" -RegistrarPool "collaborate.widevoice.com" - SipAddressType EmailAddress -SipDomain widevoice.com To set the Telephony feature (Optional) Set-CsUser Identity "AD USER NAME" -EnterpriseVoiceEnabled $True LineUri "TEL: +ExtensionNumber" 5 of 18

! Define a gateway in Topology Builder in Lync Server 2013 (For Outbound Call) Follow these steps to use Topology Builder to define a peer with which you can associate a Mediation Server to provide connectivity to the public switched telephone network (PSTN) for users enabled for Enterprise Voice. A peer to the Mediation Server can be a PSTN gateway, an IP-PBX, or a Session Border Controller (SBC) for an Internet Telephony Service Provider (ITSP) to which you connect by configuring a SIP trunk. To Define a SBC/Gateway for the Mediation Server (For Outbound Call) 1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Topology Builder. 2. Under Lync Server 2013, your site name, Shared Components, right-click the PSTN Gateways node, and then click New PSTN Gateway. 6 of 18

! 3. In Define New IP/PSTN Gateway, type the fully qualified domain name (FQDN) or IP address of the peer, and click Next. Note: If you specify Transport Layer Security (TLS) as the transport type, you must specify the FQDN instead of the IP address of the peer of the Mediation Server. 4. Define the listening mode (IPv4 or IPv6) of the IP address of your new PSTN gateway, and click Next. 7 of 18

! 5. Define a root trunk for the PSTN gateway. A trunk is a logical connection between a Mediation Server and a gateway uniquely identified by the tuple. {Mediation Server FQDN, Mediation Server listening port (TLS or TCP) : gateway IP and FQDN, gateway listening port} o When defining a PSTN gateway in Topology Builder, you must define a root trunk to successfully add the PSTN gateway to your topology. o The root trunk cannot be removed until the associated PSTN gateway is removed. 8 of 18

! 6. Under Listening Port for IP/PSTN Gateway, type the listening port that the gateway, PBX, or SBC will use for SIP messages from the Mediation Server that will be associated with the root trunk of the PSTN gateway. (By default, the ports are 5066 for Transmission Control Protocol (TCP) and 5067 for Transport Layer Security (TLS) on a PSTN gateway, PBX or SBC. On a Survivable Branch Appliance at a branch site, the default ports are 5081 for TCP and 5082 for TLS.) 7. Under SIP Transport Protocol, click the transport type that the peer uses, and then click OK. Under Associated Mediation Server, select the Mediation Server pool to associate with the root trunk of this this PSTN Gateway. 8. Under Associated Mediation Server port, type the listening port that the Mediation Server will use for SIP messages from the gateway. Note: 9 of 18

With multiple trunk support in Lync Server 2013, multiple SIP signaling ports can be defined on the Mediation Server to be used for communication with multiple PSTN gateways. When defining a trunk, the Associated Mediation Server port must be within the range of the listening ports for the respective protocol allowed by the Mediation Server. This port range is defined under Lync Server 2013 and Mediation Pools. Right-click the Mediation Server pool of interest, and select Edit Properties. Specify the port range in the Listening ports field. 9. Click Finish. To publish a topology 1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Topology Builder. 2. Select to open the topology from a local file. If you are on the computer where you defined the topology, this will be in the location where you saved it in earlier steps. Typically, this will be the Documents folder of the user who configured the topology. 3. Right-click the Lync Server 2013 node, and then click Publish Topology. 4. On the Publish the topology page, click Next. 5. On the Select Central Management Server page, select a Front End pool. 6. Click OK. 7. Click Next to complete the publishing process. 8. When the publish process has completed, click Finish. Create a voice route in Lync Server 2013 (For Outbound Call) To create a voice route by using the Lync Server Control Panel 1. Log on to the computer as a member of the RTCUniversalServerAdmins group, or as a member of the CsVoiceAdministrator, CsServerAdministrator, orcsadministrator administrative role. 2. Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel. 3. In the left navigation bar, click Voice Routing. 4. Click Route. 10 of 18

5. Click New to display the New Voice Route dialog box. 6. In Name, type a descriptive name for the voice route. 7. (Optional) In Description, type additional descriptive information for the voice route. 8. To specify the patterns that you want this route to accommodate, you can either use the Build a pattern to match tool to generate a regular expression, or write the regular expression manually. o To use the Build a pattern to match tool to generate a regular expression, enter values as follows. You can specify two types of pattern matching: Starting digits for numbers that you want to allow: Enter prefix values that this route must accommodate (including the leading + if needed). For example, type +1425, and then click Add. Repeat this for each prefix value that you want to include in the route. Exceptions: If you want to specify one or more exceptions for a prefix value, highlight the prefix and click Exceptions. Type in one or more values for the matching patterns that you do not want this route to accommodate. For example, to exclude numbers starting with +1425237 from the route, enter a value of +1425237 in the Exceptions field, and then click OK. o To define the matching pattern manually, click Edit in the Build a pattern to match tool and then type in a.net Framework regular expression to specify the matching pattern for destination phone numbers to which the route is applied. 9. Select Suppress caller ID if you do not want the ID of the phone making the outbound call to appear to the call recipient. If you select this option, you must specify an Alternate caller ID that will appear on the recipient s caller ID display. 10. To associate one or more trunks with the voice route, click Add and then select a trunk from the list. Note: If your deployment includes any Microsoft Office Communications Server 2007 R2 Mediation Servers, they will also be available in the list. 11. To associate one or more public switched telephone network (PSTN) usages with the voice route, click Select and choose a record from the list of PSTN usage records that have been defined for your Enterprise Voice deployment. 12. Arrange the PSTN usage records for optimum performance. To change a record s position in the list, highlight the record name and click the up or down arrow. 11 of 18

Note: In contrast to a voice policy, where the order in which PSTN usage records are listed is important, the order in which PSTN usage records are listed in the voice route is insignificant. However, we recommend that you organize the list by frequency of use. (Optional) Type a value into the Enter a translated number to test field and click Go. The test results are displayed under the field. 13. Click OK to save the voice route. Important: Whenever you create a voice route, you must run the Commit All command to publish the configuration change. 12 of 18

Define a gateway in Topology Builder in Lync Server 2013 (For Inbound Call) Important Note: For Inbound call Just Add SBC/Gateway entry on Lync topology builder and publish (follow below steps). No need to create Voice Route for Inbound call. Inbound call should be controlled by SBC. Follow these steps to use Topology Builder to define a peer with which you can associate a Mediation Server to provide connectivity to the public switched telephone network (PSTN) for users enabled for Enterprise Voice. A peer to the Mediation Server can be a PSTN gateway, an IP-PBX, or a Session Border Controller (SBC) for an Internet Telephony Service Provider (ITSP) to which you connect by configuring a SIP trunk. To Define a SBC/Gateway for the Mediation Server (For Inbound Call) 10. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Topology Builder. 11. Under Lync Server 2013, your site name, Shared Components, right-click the PSTN Gateways node, and then click New PSTN Gateway. 13 of 18

! 12. In Define New IP/PSTN Gateway, type the fully qualified domain name (FQDN) or IP address of the peer, and click Next. 14 of 18

! Note: If you specify Transport Layer Security (TLS) as the transport type, you must specify the FQDN instead of the IP address of the peer of the Mediation Server. 13. Define the listening mode (IPv4 or IPv6) of the IP address of your new PSTN gateway, and click Next. 15 of 18

! 14. Define a root trunk for the PSTN gateway. A trunk is a logical connection between a Mediation Server and a gateway uniquely identified by the tuple. {Mediation Server FQDN, Mediation Server listening port (TLS or TCP) : gateway IP and FQDN, gateway listening port} o When defining a PSTN gateway in Topology Builder, you must define a root trunk to successfully add the PSTN gateway to your topology. o The root trunk cannot be removed until the associated PSTN gateway is removed. 16 of 18

! 15. Under Listening Port for IP/PSTN Gateway, type the listening port that the gateway, PBX, or SBC will use for SIP messages from the Mediation Server that will be associated with the root trunk of the PSTN gateway. (By default, the ports are 5066 for Transmission Control Protocol (TCP) and 5067 for Transport Layer Security (TLS) on a PSTN gateway, PBX or SBC. On a Survivable Branch Appliance at a branch site, the default ports are 5081 for TCP and 5082 for TLS.) 16. Under SIP Transport Protocol, click the transport type that the peer uses, and then click OK. Under Associated Mediation Server, select the Mediation Server pool to associate with the root trunk of this this PSTN Gateway. 17. Under Associated Mediation Server port, type the listening port that the Mediation Server will use for SIP messages from the gateway. Note: 17 of 18

With multiple trunk support in Lync Server 2013, multiple SIP signaling ports can be defined on the Mediation Server to be used for communication with multiple PSTN gateways. When defining a trunk, the Associated Mediation Server port must be within the range of the listening ports for the respective protocol allowed by the Mediation Server. This port range is defined under Lync Server 2013 and Mediation Pools. Right-click the Mediation Server pool of interest, and select Edit Properties. Specify the port range in the Listening ports field. 18. Click Finish. To publish a topology 9. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Topology Builder. 10. Select to open the topology from a local file. If you are on the computer where you defined the topology, this will be in the location where you saved it in earlier steps. Typically, this will be the Documents folder of the user who configured the topology. 11. Right-click the Lync Server 2013 node, and then click Publish Topology. 12. On the Publish the topology page, click Next. 13. On the Select Central Management Server page, select a Front End pool. 14. Click OK. 15. Click Next to complete the publishing process. 16. When the publish process has completed, click Finish. 18 of 18