09-04-2012 07:13 PM - edited 03-17-2019 11:43 PM
I have a 8710 that is registered to vcs (x7.1) with a sip trunk to CUCM(8.6) where my CTS rooms are registered.
Calling from the 8710 to the CTS rooms work fine, but dialing a conference room on the 8710 from the CTS endpoint does not work.
SIP packet sniff from TS endpoint shows a 'internal server error"
The 8710 reports the endpoint connecting, and then immediately disconnected.
I have the DN numbers used fro the call-in match paramenters'
I seem to get random errors from VCS; ie, call leg does not exist, request termination, etc.
ANyone have any idea what this might be?
Solved! Go to Solution.
09-05-2012 04:59 PM
Hi David,
You're hitting the bug CSCty07061 which is resolved in CUCM 9.0 and some engineering specials on the 8.6.2 train.
As a workaround you can create a bogus A Record so the resolution will work.
-Paul
Sent from Cisco Technical Support iPad App
09-05-2012 04:19 AM
HI David. Would be curious to know the versions on the CTS. From 1.7.4 or higher, you don't need to add the CTS's as endpoints in the TS.
Also, its important, if multiple screen CTS's are being used, its important to keep the call SIP to SIP without any interworking being involved here as some information is passed in the SIP headers to define the system as 3 screen system, single screen etc.
If the call is SIP to SIP, and its still failing, would be interested in seeing network log debug from VCS, and SIP log from TS to see what may be going on here.
If you can provide it, would be nice to see.
VR
Patrick
09-05-2012 08:54 AM
1.8.2 is the code rev for th CTS endpoints
attached are the TS SIP logs
and here are the VCS network logs for anything coming from the cucm
09-05-2012 09:57 AM
Hi David.
Seems the TS is constantly sending 200 Ok with SDP, but not getting an ACK back to start the call from the CUCM side perhaps. If you can, would need to confirm that the VCS is sending the 200 OK with SDP to the CUCM side, and would be interested in seeing if the CUCM is receiving it, and sending the ACK back to finish the call.
If you go to Maintanance>Diagnostics>Diagnostic Logging and set Network Log Level to Debug, and place the same call, this would show us the comms between the TS and the CUCM.
I'm wondering also if the CCM can't process the large SDP from the TS at the beginning here.
See Page 28 of 53. Can you verify the SIP MAX Incoming Message Size is increased here? I'd check here to see if this may be causing you your problem, and if this is set right, and it still fails, would need to see the network log level debug from the VCS.
VR
Patrick
09-05-2012 10:16 AM
i did change the SIP max incoming from 5000 to 12000. Calls still dont complete however.
09-05-2012 10:19 AM
HI David. Sounds good. If you can, would you be able to post the log, network log level set to debug on the diagnostics page would be helpful. Turn it on to debug, place the call, and lets take a look at the log so we can see whats happening.
Thanks.
VR
Patrick
09-05-2012 04:29 PM
I also tried using the vcs-interop normalization script, to no avail
Looked at this with my call manager expert and it appears that its the CM that is hanging up the call. from the RTMT it looks like a dns query is failing, and then the SIP timer expires:
|2,100,63,1.3508793^10.52.36.15^*
11:20:09.377 |//SIP/SIPDns(2,72,1)/wait_SdlDnsSrvRecordRsp: Received SdlDnsSrvRecordRsp ReqCode is -1|0,0,0,0.0^*^*
11:20:09.377 |//SIP/SIPDns(2,72,1)/copyRecordRspToRecordReq: Retry SRV query as an 1 query|0,0,0,0.0^*^*
11:20:09.377 |//SIP/SIPDns(2,72,1)/wait_SdlDnsSrvRecordRsp: (DNS A or AAAA query called as SRV query Fail):hostname=uc.supervalu.com
Contact: <sip:511001@uc.supervalu.com;gr=urn:uuid:b716ad28-2312-54db- 825f-4aca99cade58>;isfocus;x-cisco-tip
|2,100,63,1.3508793^10.52.36.15^*
11:20:09.377 |//SIP/SIPDns(2,72,1)/wait_SdlDnsSrvRecordRsp: Received SdlDnsSrvRecordRsp ReqCode is -1|0,0,0,0.0^*^*
11:20:09.377 |//SIP/SIPDns(2,72,1)/copyRecordRspToRecordReq: Retry SRV query as an 1 query|0,0,0,0.0^*^*
11:20:09.377 |//SIP/SIPDns(2,72,1)/wait_SdlDnsSrvRecordRsp: (DNS A or AAAA query called as SRV query Fail):hostname=uc.supervalu.com
not sure where its trying to get uc.supervalu.com as that is a domain not a hostname.
After a couple more hours of troubleshooting he suggested that its from this:
Contact: <sip:511001@uc.supervalu.com;gr=urn:uuid:b716ad28-2312-54db- 825f-4aca99cade58>;isfocus;x-cisco-tip
in the header, which is not received when dialing a jabber client.
09-05-2012 04:59 PM
Hi David,
You're hitting the bug CSCty07061 which is resolved in CUCM 9.0 and some engineering specials on the 8.6.2 train.
As a workaround you can create a bogus A Record so the resolution will work.
-Paul
Sent from Cisco Technical Support iPad App
09-06-2012 01:52 PM
bogus A record pointing at my vcs seems to have done the trick, thanks!
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