I would suggest that you start a diagnostics log on the VCS with Network Log Level = DEBUG.
Once the log is running, do a B2BUA service restart on the VCS, wait for a about a minute and then stop the diagnostics log and download it.
In this log you should see some key events:
- VCS performs a DNS lookup for the hostname defined in 'OCS/Lync signalling destination address', for instance
2012-06-08T10:52:49+02:00 vcs04 b2bua: UTCTime="2012-06-08 08:52:49,581" Module="network.dns" Level="DEBUG": Detail="Sending DNS query" Name="dirpool.ciscotp.com" Type="A and AAAA"
- VCS gets a response back from the DNS server:
2012-06-08T10:52:49+02:00 vcs04 b2bua: UTCTime="2012-06-08 08:52:49,582" Module="network.dns" Level="DEBUG": Detail="Resolved hostname to: ['IPv4''TCP''10.47.43.25'] (A/AAAA) ['IPv4''TCP''10.47.43.24'] (A/AAAA) Number of relevant records retrieved: 2"
- You should then see the B2BUA set up a TCP connection to one of the IP addresses retrieved from DNS:
Once the B2BUA receives the 200 OK response back from OCS/Lync, it knows that the host is up and Status > Applications > OCS/Lync B2BUA should show an 'Alive' status in the OCS/Lync section.
If this is not working for you, I recommend you grab a diagnostics log from this VCS and read through it, comparing the above reference events with the events you see in your log, to see where the chain stops in your case.
also make sure that the 'OCS/Lync signaling destination port' and 'OCS/Lync signaling transport' settings in your B2BUA configuration are consistent, e.g when transport is set to TCP port should be 5060, and when transport is set to TLS, port should be 5061.
I'm mentioning this since your initial post states that B2BUA is configured for TCP, which is wrong since your B2BUA is attempting to connect to 10.51.4.6 on TCP port 5061 (Which is the TLS port).
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...