Re: B2BUA - No response from LYNC

Ronny Setereng · ‎06-08-2012

Hi

B2BUA is setup by the book, but B2BUA status shows No response :-(

I have followed the Lync integration deployment guide and the cerificate creation guide for X.7.x.

The B2BUA setup is now 5060 TCP, but have tried 5061 TLS.

I can do a telnet to the LYNC server on both ports and the VCS C and Lync FE is in the same subnet.

Any suggestions?

Martin Koch · ‎06-08-2012

as you think you can use 5060/tcp its nice and cleartext, what does a tcpdump say?

Also a diagnostic logging on the vcs, lync-trace and wireshark on lync can be helpful, ...

Please remember to rate helpful responses and identify

awinter2 · ‎06-08-2012

Hi Ronny,

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[23161]: 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[23161]: 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:

2012-06-08T10:52:52+02:00 vcs04 b2bua[23161]: UTCTime="2012-06-08 08:52:52,589" Module="network.tcp" Level="DEBUG": Src-ip="10.47.43.19" Src-port="46734" Dst-ip="10.47.43.24" Dst-port="5061" Detail="TCP Connecting"

2012-06-08T10:52:52+02:00 vcs04 b2bua[23161]: UTCTime="2012-06-08 08:52:52,589" Module="network.tcp" Level="DEBUG": Src-ip="10.47.43.19" Src-port="46734" Dst-ip="10.47.43.24" Dst-port="5061" Detail="TCP Connection Established"

- Once the TCP (TLS in this case) connection is established, the B2BUA will send a SIP OPTIONS request towards the OCS/Lync host (This is the aliveness check):

2012-06-08T10:52:52+02:00 vcs04 b2bua[23161]: UTCTime="2012-06-08 08:52:52,612" Module="network.sip" Level="DEBUG": Dst-ip="10.47.43.24" Dst-port="5061"

SIPMSG:

|OPTIONS sip:dirpool.ciscotp.com:5061;transport=tls SIP/2.0

Via: SIP/2.0/TLS 10.47.43.19:65072;branch=z9hG4bK03dd0f7e3026fe1ada160ba81935a8aa2;rport

Call-ID: 3c2e617632b40605@127.0.0.1

CSeq: 32964 OPTIONS

From: ;tag=93f1def96f68c855

To:

Max-Forwards: 0

User-Agent: TANDBERG/4352 (X7.2Alpha6-b2bua-1.0)

Content-Length: 0

- The OCS/Lync host should respond to this OPTIONS request with a 200 OK response:

2012-06-08T10:52:52+02:00 vcs04 b2bua[23161]: UTCTime="2012-06-08 08:52:52,613" Module="network.sip" Level="DEBUG": Src-ip="10.47.43.24" Src-port="5061"

SIPMSG:

|SIP/2.0 200 OK

Via: SIP/2.0/TLS 10.47.43.19:65072;branch=z9hG4bK03dd0f7e3026fe1ada160ba81935a8aa2;rport;received=10.47.43.19;ms-received-port=46734;ms-received-cid=2A5A00

Call-ID: 3c2e617632b40605@127.0.0.1

CSeq: 32964 OPTIONS

From: ;tag=93f1def96f68c855

To: ;tag=109D5D251D0C6BEA6467E198A9D92E8F

User-Agent: RTC/4.0

Supported: msrtc-event-categories,com.microsoft.msrtc.presence,ms-piggyback-first-notify,ms-benotify,adhoclist,eventlist

Content-Length: 0

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.

Hope this helps,

Andreas

Ronny Setereng · ‎06-08-2012

I have now logged the network traffic on the VCS:

Jun 8 12:40:01 vcsc ivy: UTCTime="2012-06-08 10:40:01,615" Module="network.dns" Level="DEBUG": Detail="Resolved hostname to: ['IPv4''TCP''10.51.4.6'] (A/AAAA) Number of relevant records retrieved: 1"

Jun 8 12:40:01 vcsc ivy: UTCTime="2012-06-08 10:40:01,615" Module="network.tcp" Level="DEBUG": Src-ip="10.51.4.3" Src-port="42358" Dst-ip="10.51.4.6" Dst-port="5061" Detail="TCP Connecting"

Jun 8 12:40:04 vcsc ivy: UTCTime="2012-06-08 10:40:04,621" Module="network.tcp" Level="ERROR": Src-ip="10.51.4.3" Src-port="42358" Dst-ip="10.51.4.6" Dst-port="5061" Detail="TCP Connection Failed"

So, now we try to change from FQDN to IP in TrustedApplication on the LYNC server. I'll be updating you soon.

Ronny

awinter2 · ‎06-08-2012

Ronny,

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).

- Andreas

Alok Jaiswal · ‎06-08-2012

Hi Ronny,

you can check whether Lync is listening on port 5060 or not using the command.

netstat -an | more

this will give you the port information.

although as you said you can telnet on port 5060 so i think it must be working.

the only thing can be done is as suggested by Andreas and Martin to collect the dump and log and try to match the events.

Also i am not sure but i think with TCP you better use the ip of VCS in trusted application rather than the FQDN.

check this thread as well, may be of some important to you.

https://supportforums.cisco.com/thread/2104813

Thanks

Alok

Ronny Setereng · ‎06-14-2012

Case closed! The customer had set the LYNC server in a private VLAN. So next time I'll start with a ping to the Front End :-)