Over the last 6 months or so I have been working with a number of companies that are using Cisco ISR’s as the PSTN gateway for Lync. I have come across a number of important settings that are a must know for this interoperability scenario. One thing to keep in mind is that while Cisco ISR’s are a supported gateway they do only provide basic functionalities. Behaviors for basic gateways can differ from that of an enhanced gateway. Support for SIP Refer is a good example.
Some of the information below has been taken from other posts on topics concerning this interoperability situation.
How do I set comfort noise on the ISR for interoperability with Lync?
There are two ways to configure comfort noise on the gateway. First off you can disable Voice Activity Detection all together on the outbound dial peer. The second option is to change the payload type for comfort noise to the compatible format. It’s pretty common for people to turn VAD off by default so some people may not have realized this issues existed. Previous Cisco documentation for OCS R2 has VAD enabled which it is by default so people migrating to Lync hoping to take advantage of media bypass might be caught out.
Option 1
dial-peer voice 1999 voip
tone ringback alert-no-PI
description TO Lync
destination-pattern 55555
session protocol sipv2
session target ipv4:192.168.1.250:5068
session transport tcp
dtmf-relay rtp-nte
codec g711ulaw
fax protocol none
no vad
Option 2
dial-peer voice 1999 voip
tone ringback alert-no-PI
description TO Lync
destination-pattern 55555
session protocol sipv2
session target ipv4:192.168.1.250:5068
session transport tcp
dtmf-relay rtp-nte
codec g711ulaw
fax protocol none
rtp payload-type comfort-noise 13
How do I disable SIP refer on a Cisco Router and in Lync for Media Bypass?
Cisco Router configuration to disable SIP refer -
Router(config)#voice service voip
Router(conf-voi-serv)#no supplementary-service sip refer
There are two options to disable SIP refer in Lync the first is through the Lync Control Panel and the second is in PowerShell. In this case disabling Refer in PowerShell is probably the easiest since you will need to do a few other things while you are there.
Disable Refer in Lync Control Panel:
Disable Refer in PowerShell:
Set-CsTrunkConfiguration –Idenity <Xds Identity> -EnableReferSupport $false
To find your trunk identity:
Get-CsTrunkConfiguration
Below is a screen shot of the full command parameters.
How do I disable RTCP and session timers in Lync?
Disabling RTCP and its timers are required for similar reasons as they were in OCS R2. I wrote a blog article outlining the reasons for disabling RTCP and session timers for OCS R2 a while ago and while the product has changed into Lync the reasons for disabling both of these are still the same.
http://voipnorm.blogspot.com/2010/07/kb-article-981218-rtcp-timer-confusion.html
Disabling both of these will remove 30 minute call drops due to RTCP incompatibilities between the two platforms. I am not going to go into a whole RFC thing of who’s right and wrong so just know this is something you have to do otherwise you will run into call drop issues.
Below is a screen shot of what the trunk will look like when you run the Get-CsTrunkConfiguration command before you change the required settings. By default both session timers and RTCP are enabled.
Below shows disabling the required settings:
The full command is:
Set-CsTrunkConfiguration –Identity <see example> -EnableSessionTimer $false –RTCPActiveCalls $false –RTCPCallsOnHold $false
Hopefully this will save someone from having to call support to set up this configuration.
VoIPNorm
