VCS-Lync integration - Calls to MCU fail

[Oscar Jaime]

Hi,

Wer'e deploying VCS-Lync integration and having trouble making Lync to/from MCU calls to work. It seems to be an ecryption problem as we're getting an "encryption levels don't match" error when looking at the search rules. We have setup the Lync side from encryption required to supported and after that we had calls from the MCU to Lync clients work on H323 only. However calls from Lync to MCU still don't work. All other calls to MCU work fine. The MCU and Neighbor Zones are setup not to force encryption either. We've noticed the MCU don't have an encryption option key. Can someone verify that this key is needed in either case? Any other ideas?

We have setup the domains as shown in the Deployment guide. Calls from Lync clients to VCS Control registered endpoints work fine also.

Thanks

[Martin Koch]

Do you have the encryption key on the VCS?

How is your MCU registered? H323 or/and SIP, if SIP do you use SIP TLS?

Did you check the call flow of the call does it use the protocols as you would

expect or does it behave different?

Do you use the b2bua or a sip route to the vcs (and with or without tls?

Which VCS and MCU software version do you use, do you have the enhanced

collaboration key on one of the VCS in the path?

Also read the lync vcs deployment guide, for example:

Cisco VCS Deployment Guide: Microsoft Lync 2010 and Cisco VCS X7.2 Page 56 of 80 



Encryption mismatch 
Look for the reason for the 488. If it mentions encryption levels do not match, ensure that you have configured encryption appropriately, either: 
 “Lyncgateway”VCShasenhancedcollaborationoptionkeyincluded,or 






Appendix 1 – Troubleshooting 




 Lyncisconfiguredsuchthatencryptionissupported(orsetas“DoNotSupportEncryption”)–note that if the encryption support is changed on Lync then a short time must be left for the change to propagate through Lync server and then the Lync client must be signed off and then signed back in again to pick up the new configuration. 

[Oscar Jaime]

Hi Martin,

Thanks for the response. Please see answers to your questions below

Do you have the encryption key on the VCS?   Yes

How is your MCU registered? H323 or/and SIP, if SIP do you use SIP TLS?

Registered using both SIP and H323  -  no TLS

Did you check the call flow of the call does it use the protocols as you would

expect or does it behave different?

When Lync is set to “support encryption” then the call works (the last leg of the call between the MCU and VCSC is Interworked to H323).  If Lync is set to “require encryption”, then the call fails.

Do you use the b2bua or a sip route to the vcs (and with or without tls?

We’re using the B2BUA – and we also have a static route in place to support calls to ad hoc conferences on the MCU.

Which VCS and MCU software version do you use,

VCS = X7.2.1,  MCU 4510= 4.1.x (need to verify) Lync version is 2010

do you have the enhanced collaboration key on one of the VCS in the path?

Yes, the “Lync Gateway VCS” has the Enhanced OCS Collaboration key.

Also read the lync vcs deployment guide, for example:

We have followed the Deployment guide you mention for the integration. We have looked at the Troubleshooting section thouroughly and verified everything is as recommended.

Thanks and looking forward to your advice

[Chris Price]

I would suggest you get the encryption key for the MCU, it's free after all! A TAC case is probably the best route.

Chris

Sent from Cisco Technical Support iPhone App