02-06-2013 05:50 AM - edited 03-18-2019 12:33 AM
Guys,
We have a deployment on the integration of VCS to Microsoft Lync.
Details as below:
VCS-Control: v7.2.1
VCS-Control (Lync-Gateway): v7.2.1
VCS-Expressway: v7.2.1
Microsoft Lync 2010
All licenses needed for this integration is available except for the FINDME option key.
We have followed the configuration guide on this but in vain.
Both sides trust hosts is done properly.
Current temporary deployment we are using TCP to Microsoft Lync 2010 from VCS-Control (Lync-Gateway).
Below is the status of the B2BUA:
VCS
<sip:localservice:localdomain:5061;transport=tls;lr>
Standard
Alive
<sip:xxx.xxx.xxx.xxx:5060;transport=tcp;lr;ds>
Microsoft
No response
Far end is not running or not listening on the configured port.
Need your expertise on this. Please let us know if you see something wrong.
02-06-2013 06:11 AM
Hi,
my initial thought/question would be to ask why you're not using SIP TLS between VCS/B2BUA and Lync, since that is the configuration the deployment guide provides instructions for?
Lync 2010 by default does not listen for SIP TCP on port 5060, which would explain the 'Far end is not running or not listening on the configured port' diagnostics message.
SIP TLS is preferred over SIP TCP for the trunk between B2BUA and Lync since it is secure and allows for encrypted media.
If you did try setting up SIP TLS to begin with, could you elaborate on the problems you ran into with this configuration?
- Andreas
02-06-2013 10:27 PM
Hi Andreas,
Thanks for the reply.
We have successfully integrate w Lync using TLS.
Thanks again.
Sent from Cisco Technical Support iPhone App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide