Posts Tagged ‘lync’

Integrating Lync with a T1: What to make sure you and the customer ask the phone company

February 22, 2012 Leave a comment

When integrating Lync with a T1 PRI via a media gateway there are some questions that you might wish to ask the customer prior to beginning the Lync / Telephony integration that can save you and the customer some time:

• For calls to the PSTN: How does the T1 PRI expect to receive the Called Number and Calling Number fields from Lync? For example, should those numbers be 10 digits or 11 digits or is the T1 provider capable of accepting both?
• For calls from the PSTN: How will the T1 PRI provider send the Called Number and Calling number fields to the media gateway? For example, while they be 10 digits, or 11 digits, (Phone providers other than SIP providers won’t send E.164).
• What T1 PRI protocol(s) does the T1 PRI that has been provisioned support, (e.g. NI2, 5ESS, 4ESS or DMS100)? This is needed to configure the media gateway to communicate with the T1 PRI.
o Make sure to avoid the customer purchasing a T1 PRI that is utilizing CAS. CAS does not support CallerID, (i.e. you won’t know who is calling)
• What phone numbers are being routed to the T1 PRI? For example, is it a block of numbers or a list of numbers out of sequence? If all numbers are going to a single Lync server/pool, then the gateway can be configured to route all calls on the T1 PRI to Lync’s IP address. However, if you have multiple locations you may need to set up routing tables on the media gateway that depending on the Called Number may dictate to which Lync server/pool the call is routed.
• Before going onsite ask the customer, “Has the T1 PRI local loop has been turned-up and accepted”. When a phone provider, (i.e. the CLEC) technician goes onsite, they will connect the T1 to a box known as a DMARC (demarcation point). At that time the phone technician will verify that the T1 can communicate back to the phone company, (i.e. the “CO” – central office). After that is done, the customer will be asked to call the phone provider, and “accept the local loop” for that T1. At that time, the customer should ask the person on the phone to verify that BOTH the data and voice channels are “up”. Very often a phone provider will “turn up” the data channel, (the “D” channel) and not “turn up” the voice channels, (really).
• After the T1 PRI “turn up” is verified, then make sure that the customer also calls the phone provider to accept the block of phone numbers, (i.e. DIDs) that have been provisioned. This is a separate call since it will be a separate work order for the phone company, (really). The customer should tell the phone provider to go ahead and “point” those numbers to the new T1 even though the media gateway has not been yet connected.

Hopefully this is helpful when rolling out a media gateway with Lync and a T1 PRI by saving you some time onsite engaging in thumb-twiddling exercises 

Categories: Lync EV, Uncategorized Tags:

Lync Common Area Phones Quickstart

July 8, 2011 Leave a comment


One of the new features in Lync 2010 that was not supported in OCS 2007 R2 is the ability to deploy what are known as “Common Area Phones”. These are phones that you might find in the lobby of business that are used for guests. Unlike other Lync phones, Common Area Phones do not allow the entry of a username and password to logon to the network.


Unfortunately the Microsoft documentation for quickly setting up a Common Area Phone can be a bit challenging. This is especially true if you are in a situation that you would like to quickly configure and set up a Lync environment to use a Common Area Phone, (e.g. Lync pilot or when providing knowledge transfer to clients).


This document provides the steps necessary to quickly enable a Lync infrastructure to support the use of Common Area Phones.

General Steps:

There are 4 general steps to enabling the use of Common Area Phones:

• Add support for Lync Common Area Phones to the environments Windows based DHCP configuration.
• Enable PIN authorization support in Lync
• Create an AD SIP enabled contact record that is utilized by the Common Area Phone to login to the network
• Set a PIN for the Common Area Phone that is entered to initially use the phone for Lync

Detailed Steps:

Let’s suppose you have a Polycom CX500 phone. This phone can only connect to a Lync infrastructure using a PIN and only has an Ethernet connection, (i.e. no USB plug).

The steps below are intended to be utilized for the purpose of quickly connecting and testing Common Area Phones. There are plenty of complexities that can be taken advantage of, (i.e. dialing restrictions) that are not covered in this document. Please refer to the “Microsoft Lync Server 2010 Client and Device Deployment Guide” for further details.

Sample environment:

• AD Forest name:
• Lync Pool name:
• NTP time server already enabled.
• CX500 waiting to be configured in the “Building Main Lobby”
• Phone number to assign: 208 555 7000
• The following OU exists in AD: ou=phones,dc=numa,dc=us

Perform the following steps:

• DHCP Configuration
o Copy the program dhcputil.exe from C:\Program Files\Common Files\Microsoft Lync Server 2010 to a location accessible from your DHCP server
o Logon to your DHCP server
o Execute this command: dhcputil –sipserver runconfigscript
 This will add all the entries needed for DHCP to support a Common Area Phone
• Enable PIN authorization for Lync by typing the following Lync Management Shell (PS) cmdlet: set-cswebserviceconfiguration –identity Global –usepinauth $true
• Create a new SIP enabled contact record in AD that will be used by the Common Area Phone to logon to Lync
o New-CsCommonAreaPhone -LineUri “tel:+12085557000” -RegistrarPool “” -OU “OU=Phones,DC=numa,DC=us” -Description “Building Main Lobby” -DisplayName “Building Main Lobby” -DisplayNumber “1 (208) 555-7000”
• Set a PIN for the contact record created above that is enter when initially connecting the phone to the network:
o Set-csclientpin –identity “Building Main Lobby” –pin 1234

Now power up the CX500 and when prompted enter the pin value “1234”. The phone will then connect and login to Lync.

Categories: Uncategorized Tags: