cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3120
Views
0
Helpful
10
Replies

Sip Trunk Between CUCM 8.5 and Call manager 4.1 not Working

Shakti Chauhan
Level 1
Level 1

Hello Everyone,

I am having a hard time putting up a SIP trunk Between CUCM 8.5 and Call manager 4.1.

I am able to ring from 8.5 to the phones in 4.1 clusters. But as soon as the call is picked up from other 4.1 cluster phone, the call drops.

I gone through the traces and i have found SIP 503 (Service Unavailable) and Q850 Error =63.

Interestingly, prior to 8.5, I have tested the trunk on 8.0 (VM) Box and it worked absolutely fine while calling from 8.0 to 4.1.

I appreciate any help, in this regard.

Thanks,

Shakti

10 Replies 10

Chris Deren
Hall of Fame
Hall of Fame

I would not recommend using SIP on CUCM 4.1 as back on that version SIP implementation was not very robust, I would use Intercluster Trunk (H323 non-GK controlled) and it will work a lot more reliably.

In either way ensure that the Device Pool assigned to the trunk on each side has CUCM Group assigned that includes a CUCM server that is configured on the other side as the destination of the trunk.

HTH,

Chris

Jonathan Schulenberg
Hall of Fame
Hall of Fame

I agree with Chris here: use H.323 ICT when working with this old version.

The one thing that I could think of which may be causing this would be a codec mismatch without a transcoding (or MTP if only DTMF mismatch) resource available. That would explain why you do not see the 503 error until it tries to connect media. You could compare the SDP offers to see if there are differences or look for media resource manager getting invoked in the logs of either cluster.

Please remember to rate helpful responses and identify helpful or correct answers.

Shakti Chauhan
Level 1
Level 1

Thanks Friends for your valuable comments,

pls. find the sdi trace enclosed with this reply. We have a rfc constraint, therefore  we have to implement Sip Trunk between these cluster.

Calling Number : 49000/10.68.123.17   CUCM 10.69.0.25     Version 8.5

called number   :1702                          CUCM 172.21.1.17   Version 4.1

thanks

Shakti

SDI LOG Below:

[39318,NET]

SIP/2.0 200 OK

Via: SIP/2.0/TCP 10.68.123.17:50777;branch=z9hG4bKf674dcb9

From: <49000>;tag=34bdc82c372e0b458a829b17-8645c35a

To: <1>;tag=1396147534

Date: Mon, 28 Jan 2013 04:26:07 GMT

Call-ID: d470df00-1051fddf-f1-1900450a@10.69.0.25

CSeq: 1004 NOTIFY

Content-Length: 0

|1,100,57,1.13270^10.68.123.17^*

09:56:07.938 |//SIP/SIPHandler/ccbId=0/scbId=13414/ccsip_platform_delete_scb: scb mgmt deleted 0xaee16d40 (context_id=13221)|1,100,57,1.13270^10.68.123.17^*

09:56:07.941 |SIPSocketProtocol(1,100,9,460)::handleReadComplete send SdlReadRsp: size 377|*^*^*

09:56:07.941 |//SIP/SIPTcp/wait_SdlReadRsp: SdlRead bufferLen=377|1,100,57,1.13271^172.21.1.17^*

09:56:07.941 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 172.21.1.17 on port 5060 index 230 with 377 bytes:

[39319,NET]

SIP/2.0 100 Trying

Via: SIP/2.0/TCP 10.69.0.25:5060;branch=z9hG4bKfb1d930e5f

From: "JAIPUR-SHQ" <49000>;tag=13417~fe35675e-a436-4ec8-bf77-d6fc820b0f75-18288989

To: <1702>;tag=17257235

Date: Mon, 28 Jan 2013 04:39:35 GMT

Call-ID: d470df00-1051fddf-f4-1900450a@10.69.0.25

CSeq: 101 INVITE

Allow-Events: telephone-event

Content-Length: 0

|1,100,57,1.13271^172.21.1.17^*

09:56:07.941 |//SIP/SIPTcp/wait_SdlReadRsp: SignalCounter = 13269|1,100,57,1.13271^172.21.1.17^*

09:56:07.942 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_TRYING value=500 retries=6|1,100,57,1.13271^172.21.1.17^*

09:56:07.942 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_EXPIRES value=180000 retries=0|1,100,57,1.13271^172.21.1.17^*

09:56:07.942 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_start_timer: type=SIP_TIMER_EXPIRES value=180000 retries=0|1,100,57,1.13271^172.21.1.17^*

09:56:07.951 |SIPSocketProtocol(1,100,9,460)::handleReadComplete send SdlReadRsp: size 571|*^*^*

09:56:07.951 |//SIP/SIPTcp/wait_SdlReadRsp: SdlRead bufferLen=571|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 172.21.1.17 on port 5060 index 230 with 571 bytes:

[39320,NET]

SIP/2.0 180 Ringing

Via: SIP/2.0/TCP 10.69.0.25:5060;branch=z9hG4bKfb1d930e5f

From: "JAIPUR-SHQ" <49000>;tag=13417~fe35675e-a436-4ec8-bf77-d6fc820b0f75-18288989

To: <1702>;tag=17257235

Date: Mon, 28 Jan 2013 04:39:35 GMT

Call-ID: d470df00-1051fddf-f4-1900450a@10.69.0.25

CSeq: 101 INVITE

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK

Allow-Events: telephone-event

Remote-Party-ID: "NOC (RajSWAN)" <1702>;party=called;screen=no;privacy=off

Contact: <1702>

Content-Length: 0

|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPTcp/wait_SdlReadRsp: SignalCounter = 13270|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPHandler/ccbId=0/scbId=0/extract_sdp: sipAppGetParticularContent failed to obtain SDP - result=2 len=0|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPHandler/ccbId=0/scbId=0/extractAssertedInfo: parseResult[1]|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPHandler/ccbId=0/scbId=0/copyConnectedInfoAdjustParseResult: identityParseResult[1] || rpidHdr|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPHandler/ccbId=0/scbId=0/copyConnectedInfoAdjustParseResult: rpidHdr values taken|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPHandler/ccbId=13417/scbId=0/findDevicePID: Routed to SIPD by ccbId/scbId|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPHandler/ccbId=0/scbId=0/parseContactHeader: Incoming Contact=[<1702>]|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPHandler/ccbId=13417/scbId=0/findDevicePID: Routed to SIPD by ccbId/scbId|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPD(1,67,1)/ccbId=0/scbId=0/getKeyBasedOnCiAndBranch: AddressingElement branch is 0 and ci is 18288989  mapKey is 18288989|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPD(1,67,1)/ccbId=0/scbId=0/getCdpcPidGivenCcbidAndCi: found Cdpc Pid (1,100,68,11) for mapKey 18288989|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPD(1,67,1)/ccbId=0/scbId=0/getKeyBasedOnCiAndBranch: AddressingElement branch is 0 and ci is 18288989  mapKey is 18288989|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPD(1,67,1)/ccbId=0/scbId=0/getCdpcPidGivenCcbidAndCi: found Cdpc Pid (1,100,68,11) for mapKey 18288989|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |//SIP/SIPCdpc(1,68,11)/ci=18288989/ccbId=13417/scbId=0/updateAllowedMethods: mEndpointAllowedMethods=007b|1,100,57,1.13272^172.21.1.17^*

09:56:07.951 |SIP DTMF Info: mLocalDtmfCaps...UNSOL=0, KPML=1, Inband=1(101) mEndppointsDtmfCaps...UNSOL=0, KPML=0, Inband=0(0) mDefaultTelephonyEvent=101, mDtmfPreference=1, mMtpAllocated=1|*^*^*

09:56:07.951 |//SIP/SIPCdpc(1,68,11)/ci=18288989/ccbId=13417/scbId=0/getIdentityIncomingSIPMsg: fIdParseRes=[11], fRemoteNum[1702], fRemoteNam[NOC (RajSWAN)], fRemoteNumPi[1], fRemoteNamPi[1], fRemoteSi[0]|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPCdpc(1,68,11)/ci=18288989/ccbId=13417/scbId=0/processRemoteIdentityInfo: numPi=1,mCnNumPi=0;namePi=1,remoteCnNamePi=0;name=NOC (RajSWAN),remoteCnName=,After update remoteCnName=NOC (RajSWAN);|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPCdpc(1,68,11)/ci=18288989/ccbId=13417/scbId=0/processRemoteIdentityInfo: identityFlag=[Changed:- Num PI;Name;Name PI;]|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPCdpc(1,68,10)/ci=18288988/ccbId=13413/scbId=0/getCcSignalCnNameAndNumberInfo: identityFlag=0xff|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPCdpc(1,68,10)/ci=18288988/ccbId=13413/scbId=0/setCnNameAndNumber: connectedData - Name NOC (RajSWAN) Number 1702 NumberPi 1 NamePi 1 Si 0, LocalData - NumberPi 1 NamePi 1|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPCdpc(1,68,10)/ci=18288988/ccbId=13413/scbId=0/setIdentityOutgoingSIPMsg: identityFlag=[RPID;], privacyType[0]|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPHandler/ccbId=0/scbId=0/setPresentationIndication: namePi[1], numPi[1]|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPHandler/ccbId=0/scbId=0/setScreeningIndication: si[0], oct3a[80]|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPHandler/ccbId=0/scbId=0/setIdentityHeaders: ccb[b67fc8e8], currLocalNum[1702], currLocalNam[NOC (RajSWAN)], callbackNumber[], localNumPi[1], localNamPi[1], id.flag[8], id.privacy[0]|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPHandler/ccbId=0/scbId=0/setRpidHeader: rpidHdrStr["NOC (RajSWAN)" <1702>;party=called;screen=no;privacy=off]|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPHandler/ccbId=13413/scbId=0/addContactHeader: Outgoing Contact=[<1>]|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPHandler/ccbId=13413/scbId=0/findDevicePID: Routed to SIPD by ccbId/scbId|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPCdpc(1,68,10)/ci=18288988/ccbId=13413/scbId=0/setSIPUpdateFlags: mIsUpdateForSignalingAllowed = 1  mIsUpdateForMediaAllowed = 0  mPendingOutgoingUpdate = 0|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPHandler/ccbId=13413/scbId=0/findDevicePID: Routed to SIPD by ccbId/scbId|1,100,57,1.13272^172.21.1.17^*

09:56:07.952 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.68.123.17 on port 50777 index 45

[39321,NET]

SIP/2.0 180 Ringing

Via: SIP/2.0/TCP 10.68.123.17:50777;branch=z9hG4bKd5b1eba1

From: "JAIPUR-SHQ" <49000>;tag=34bdc82c372e0b43a4061e52-f2ea0dc9

To: <1>;tag=13413~fe35675e-a436-4ec8-bf77-d6fc820b0f75-18288988

Date: Mon, 28 Jan 2013 04:26:07 GMT

Call-ID: 34bdc82c-372e0041-061e4a0c-acea8753@10.68.123.17

CSeq: 101 INVITE

Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY

Allow-Events: presence

Call-Info: ; security= NotAuthenticated; orientation= to; ui-state= ringout; gci= 1-12010; call-instance= 1

Send-Info: conference, x-cisco-conference

Remote-Party-ID: "NOC (RajSWAN)" <1702>;party=called;screen=no;privacy=off

Contact: <1>

Content-Length: 0

REGISTER sip:10.69.0.25 SIP/2.0

Via: SIP/2.0/TCP 10.71.231.4:52409;branch=z9hG4bKb5755018

From: <67550>;tag=34bdc82c37680a3a4fd83683-23407aaa

To: <67550>

Call-ID: 34bdc82c-37680066-d48d3a9a-1941a251@10.71.231.4

Max-Forwards: 70

Date: Mon, 28 Jan 2013 04:26:17 GMT

CSeq: 2700 REGISTER

User-Agent: Cisco-CP7942G/9.1.1

Contact: <3900BBBA-7616-4F29-B43E-B8C118DC62AB>;+sip.instance="";+u.sip!devicename.ccm.cisco.com="SEP34BDC82C3768";+u.sip!model.ccm.cisco.com="434"

Supported: replaces,join,sdp-anat,norefersub,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-5.1.0,X-cisco-xsi-8.5.1

Content-Length: 0

Expires: 3600

|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |//SIP/SIPTcp/wait_SdlReadRsp: SignalCounter = 13275|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.231.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.231.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.71.231.4 on port 52409 index 120

[39335,NET]

SIP/2.0 100 Trying

Via: SIP/2.0/TCP 10.71.231.4:52409;branch=z9hG4bKb5755018

From: <67550>;tag=34bdc82c37680a3a4fd83683-23407aaa

To: <67550>

Date: Mon, 28 Jan 2013 04:26:11 GMT

Call-ID: 34bdc82c-37680066-d48d3a9a-1941a251@10.71.231.4

CSeq: 2700 REGISTER

Content-Length: 0

|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.231.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |//SIP/SIPHandler/ccbId=13422/scbId=0/findDevicePID: Routed to SIPStationInit|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |SIPStationInit: connID=120, SEP34BDC82C3768, 10.71.231.4:52409, checkTcpConnection:  Connection index 120 matches|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |SIPStationInit: connID=120, SEP34BDC82C3768, 10.71.231.4:52409, Routing to D (1,100,59,120), regCount=125|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |SIPStationD(1,100,59,120), SEP34BDC82C3768, 10.71.231.4:52409, primaryDN=67550, Received REGISTER from 67550@10.71.231.4:52409|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |SIPStationD(1,100,59,120), SEP34BDC82C3768, 10.71.231.4:52409, primaryDN=67550, Register refresh #124 for line 1|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.231.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:11.896 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.71.231.4 on port 52409 index 120

[39336,NET]

SIP/2.0 200 OK

Via: SIP/2.0/TCP 10.71.231.4:52409;branch=z9hG4bKb5755018

From: <67550>;tag=34bdc82c37680a3a4fd83683-23407aaa

To: <67550>;tag=143467458

Date: Mon, 28 Jan 2013 04:26:11 GMT

Call-ID: 34bdc82c-37680066-d48d3a9a-1941a251@10.71.231.4

CSeq: 2700 REGISTER

Expires: 120

Contact: <3900BBBA-7616-4F29-B43E-B8C118DC62AB>;+sip.instance="";+u.sip!devicename.ccm.cisco.com="SEP34BDC82C3768";+u.sip!model.ccm.cisco.com="434"

Supported: X-cisco-srtp-fallback,X-cisco-sis-5.1.0

Content-Length: 0

|1,100,57,1.13277^10.71.231.4^SEP34BDC82C3768

09:56:13.427 |//SIP/SIPTcp/wait_SdlReadRsp: SdlRead bufferLen=850|1,100,57,1.13278^10.71.207.4^*

09:56:13.427 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.71.207.4 on port 51608 index 121 with 850 bytes:

[0,NET]

REGISTER sip:10.69.0.25 SIP/2.0

Via: SIP/2.0/TCP 10.71.207.4:51608;branch=z9hG4bK634f8d76

From: <1028>;tag=34bdc8c6d9880a887baf1093-15a42b6c

To: <1028>

Call-ID: 34bdc8c6-d988000c-19a01d49-3038f3e3@10.71.207.4

Max-Forwards: 70

Date: Mon, 28 Jan 2013 04:26:21 GMT

CSeq: 2789 REGISTER

User-Agent: Cisco-CP7942G/9.1.1

Contact: <176CA576-A254-42A6-B628-BDFFD8B7C438>;+sip.instance="";+u.sip!devicename.ccm.cisco.com="SEP34BDC8C6D988";+u.sip!model.ccm.cisco.com="434"

Supported: replaces,join,sdp-anat,norefersub,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-5.1.0,X-cisco-xsi-8.5.1

Content-Length: 0

Expires: 3600

|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |//SIP/SIPTcp/wait_SdlReadRsp: SignalCounter = 13276|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.207.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.207.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.71.207.4 on port 51608 index 121

[39338,NET]

SIP/2.0 100 Trying

Via: SIP/2.0/TCP 10.71.207.4:51608;branch=z9hG4bK634f8d76

From: <1028>;tag=34bdc8c6d9880a887baf1093-15a42b6c

To: <1028>

Date: Mon, 28 Jan 2013 04:26:13 GMT

Call-ID: 34bdc8c6-d988000c-19a01d49-3038f3e3@10.71.207.4

CSeq: 2789 REGISTER

Content-Length: 0

|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.207.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |//SIP/SIPHandler/ccbId=13423/scbId=0/findDevicePID: Routed to SIPStationInit|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |SIPStationInit: connID=121, SEP34BDC8C6D988, 10.71.207.4:51608, checkTcpConnection:  Connection index 121 matches|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |SIPStationInit: connID=121, SEP34BDC8C6D988, 10.71.207.4:51608, Routing to D (1,100,59,121), regCount=125|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |SIPStationD(1,100,59,121), SEP34BDC8C6D988, 10.71.207.4:51608, primaryDN=1028, Received REGISTER from 1028@10.71.207.4:51608|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.427 |SIPStationD(1,100,59,121), SEP34BDC8C6D988, 10.71.207.4:51608, primaryDN=1028, Register refresh #124 for line 1|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.428 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.207.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.428 |//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:13.428 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.71.207.4 on port 51608 index 121

[39339,NET]

SIP/2.0 200 OK

Via: SIP/2.0/TCP 10.71.207.4:51608;branch=z9hG4bK634f8d76

From: <1028>;tag=34bdc8c6d9880a887baf1093-15a42b6c

To: <1028>;tag=2012702236

Date: Mon, 28 Jan 2013 04:26:13 GMT

Call-ID: 34bdc8c6-d988000c-19a01d49-3038f3e3@10.71.207.4

CSeq: 2789 REGISTER

Expires: 120

Contact: <176CA576-A254-42A6-B628-BDFFD8B7C438>;+sip.instance="";+u.sip!devicename.ccm.cisco.com="SEP34BDC8C6D988";+u.sip!model.ccm.cisco.com="434"

Supported: X-cisco-srtp-fallback,X-cisco-sis-5.1.0

Content-Length: 0

|1,100,57,1.13278^10.71.207.4^SEP34BDC8C6D988

09:56:14.695 |//SIP/SIPTcp/wait_SdlReadRsp: SdlRead bufferLen=847|1,100,57,1.13279^10.71.85.4^*

09:56:14.695 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.71.85.4 on port 51690 index 17 with 847 bytes:

[0,NET]

REGISTER sip:10.69.0.25 SIP/2.0

Via: SIP/2.0/TCP 10.71.85.4:51690;branch=z9hG4bK2e675217

From: <1056>;tag=34bdc82ca5d90a9f865da98f-b5f5f197

To: <1056>

Call-ID: 34bdc82c-a5d90011-4ef80c3f-ac4b29c6@10.71.85.4

Max-Forwards: 70

Date: Mon, 28 Jan 2013 04:26:17 GMT

CSeq: 2811 REGISTER

User-Agent: Cisco-CP7942G/9.1.1

Contact: <32295DF1-6143-441A-B9BD-1A2483A6E505>;+sip.instance="";+u.sip!devicename.ccm.cisco.com="SEP34BDC82CA5D9";+u.sip!model.ccm.cisco.com="434"

Supported: replaces,join,sdp-anat,norefersub,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-5.1.0,X-cisco-xsi-8.5.1

Content-Length: 0

Expires: 3600

|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.695 |//SIP/SIPTcp/wait_SdlReadRsp: SignalCounter = 13277|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.695 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.85.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.85.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.71.85.4 on port 51690 index 17

[39341,NET]

SIP/2.0 100 Trying

Via: SIP/2.0/TCP 10.71.85.4:51690;branch=z9hG4bK2e675217

From: <1056>;tag=34bdc82ca5d90a9f865da98f-b5f5f197

To: <1056>

Date: Mon, 28 Jan 2013 04:26:14 GMT

Call-ID: 34bdc82c-a5d90011-4ef80c3f-ac4b29c6@10.71.85.4

CSeq: 2811 REGISTER

Content-Length: 0

|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.85.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |//SIP/SIPHandler/ccbId=13424/scbId=0/findDevicePID: Routed to SIPStationInit|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |SIPStationInit: connID=17, SEP34BDC82CA5D9, 10.71.85.4:51690, checkTcpConnection:  Connection index 17 matches|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |SIPStationInit: connID=17, SEP34BDC82CA5D9, 10.71.85.4:51690, Routing to D (1,100,59,17), regCount=129|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |SIPStationD(1,100,59,17), SEP34BDC82CA5D9, 10.71.85.4:51690, primaryDN=1056, Received REGISTER from 1056@10.71.85.4:51690|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |SIPStationD(1,100,59,17), SEP34BDC82CA5D9, 10.71.85.4:51690, primaryDN=1056, Register refresh #128 for line 1|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=10.71.85.4, Source Port=5060, IpAddress Type=0|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.696 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.71.85.4 on port 51690 index 17

[39342,NET]

SIP/2.0 200 OK

Via: SIP/2.0/TCP 10.71.85.4:51690;branch=z9hG4bK2e675217

From: <1056>;tag=34bdc82ca5d90a9f865da98f-b5f5f197

To: <1056>;tag=928814696

Date: Mon, 28 Jan 2013 04:26:14 GMT

Call-ID: 34bdc82c-a5d90011-4ef80c3f-ac4b29c6@10.71.85.4

CSeq: 2811 REGISTER

Expires: 120

Contact: <32295DF1-6143-441A-B9BD-1A2483A6E505>;+sip.instance="";+u.sip!devicename.ccm.cisco.com="SEP34BDC82CA5D9";+u.sip!model.ccm.cisco.com="434"

Supported: X-cisco-srtp-fallback,X-cisco-sis-5.1.0

Content-Length: 0

|1,100,57,1.13279^10.71.85.4^SEP34BDC82CA5D9

09:56:14.814 |SIPSocketProtocol(1,100,9,460)::handleReadComplete send SdlReadRsp: size 482|*^*^*

09:56:14.814 |//SIP/SIPTcp/wait_SdlReadRsp: SdlRead bufferLen=482|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 172.21.1.17 on port 5060 index 230 with 482 bytes:

[39343,NET]

SIP/2.0 503 Service Unavailable

Via: SIP/2.0/TCP 10.69.0.25:5060;branch=z9hG4bKfb1d930e5f

From: "JAIPUR-SHQ" <49000>;tag=13417~fe35675e-a436-4ec8-bf77-d6fc820b0f75-18288989

To: <1702>;tag=17257235

Date: Mon, 28 Jan 2013 04:39:35 GMT

Call-ID: d470df00-1051fddf-f4-1900450a@10.69.0.25

CSeq: 101 INVITE

Allow-Events: telephone-event

Remote-Party-ID: "NOC (RajSWAN)" <1702>;party=called;screen=no;privacy=off

Content-Length: 0

|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |//SIP/SIPTcp/wait_SdlReadRsp: SignalCounter = 13278|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_EXPIRES value=180000 retries=0|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |//SIP/SIPHandler/ccbId=0/scbId=0/ccsip_api_call_disconnected: ccb->cc_disc_cause (63); ccb->sip_disc_cause(503)|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 172.21.1.17 on port 5060 index 230

[39344,NET]

ACK sip:1702@172.21.1.17:5060 SIP/2.0

Via: SIP/2.0/TCP 10.69.0.25:5060;branch=z9hG4bKfb1d930e5f

From: "JAIPUR-SHQ" <49000>;tag=13417~fe35675e-a436-4ec8-bf77-d6fc820b0f75-18288989

To: <1702>;tag=17257235

Date: Mon, 28 Jan 2013 04:26:07 GMT

Call-ID: d470df00-1051fddf-f4-1900450a@10.69.0.25

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: presence, kpml

Content-Length: 0

|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |//SIP/SIPHandler/ccbId=13417/scbId=0/findDevicePID: Routed to SIPD by ccbId/scbId|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |SIPSocketProtocol(1,100,9,460)::handleWriteComplete|*^*^*

09:56:14.814 |//SIP/SIPD(1,67,1)/ccbId=0/scbId=0/getKeyBasedOnCiAndBranch: AddressingElement branch is 0 and ci is 18288989  mapKey is 18288989|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |//SIP/SIPD(1,67,1)/ccbId=0/scbId=0/getCdpcPidGivenCcbidAndCi: found Cdpc Pid (1,100,68,11) for mapKey 18288989|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |ViprUtils::uploadVCRifRequired VcrUploadNeeded[0] FeatureData NOT added|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |//SIP/SIPCdpc(1,68,11)/ci=0/ccbId=13417/scbId=0/uploadVCRifRequired: VcrUploadNeeded 0|1,100,57,1.13280^172.21.1.17^*

09:56:14.814 |//SIP/SIPCdpc(1,68,11)/ci=18288989/ccbId=13417/scbId=0/getDefAe: SIPCdpc=11, nodeId=1, processNumber=67  ci=18288989, branch=0|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPD(1,67,1)/ccbId=0/scbId=0/getKeyBasedOnCiAndBranch: AddressingElement branch is 0 and ci is 18288989  mapKey is 18288989|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPD(1,67,1)/ccbId=0/scbId=0/getCdpcPid: found Cdpc Pid (1,100,68,11) for mapKey 18288989|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPHandler/ccbId=13417/scbId=0/findDevicePID: Routed to SIPD by ccbId/scbId|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPCdpc(1,68,10)/ci=18288988/ccbId=13413/scbId=0/appendReasonHdr: appendReasonHdr - Invalid Disconnect Cause(cause=1459617833), No Reason Header Appended|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPCdpc(1,68,11)/ci=18288989/ccbId=13417/scbId=0/updateCallStatsForCallCompletion: SIPCdpc=11, nodeId=1, processNumber=67|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPCdpc(1,68,11)/ci=18288989/ccbId=13417/scbId=0/terminateOobDtmf: Termination not required.|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_EXPIRES value=180000 retries=0|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPD(1,67,1)/ccbId=13417/scbId=0/restart0_DStopInd: Removing Cdpc Pid (1,100,68,11) with  mapKey 0 from mCiToPid table|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_CONNECT value=500 retries=6|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_start_timer: type=SIP_TIMER_CONNECT value=500 retries=6|1,100,57,1.13280^172.21.1.17^*

09:56:14.815 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.68.123.17 on port 50777 index 45

[39345,NET]

SIP/2.0 503 Service Unavailable

Via: SIP/2.0/TCP 10.68.123.17:50777;branch=z9hG4bKd5b1eba1

From: "JAIPUR-SHQ" <49000>;tag=34bdc82c372e0b43a4061e52-f2ea0dc9

To: <1>;tag=13413~fe35675e-a436-4ec8-bf77-d6fc820b0f75-18288988

Date: Mon, 28 Jan 2013 04:26:07 GMT

Call-ID: 34bdc82c-372e0041-061e4a0c-acea8753@10.68.123.17

CSeq: 101 INVITE

Allow-Events: presence

Content-Length: 0

|1,100,57,1.13280^172.21.1.17^*

09:56:14.816 |//SIP/SIPTcp/wait_SdlSPISignal: received a spi signal ...|1,100,57,1.13280^172.21.1.17^*

09:56:14.816 |//SIP/SIPTcp/wait_SdlSPISignal: Did not find table entry in Close Msg,Index = 230|1,100,57,1.13280^172.21.1.17^*

09:56:14.816 |//SIP/SIPHandler/ccbId=0/scbId=0/getRemoteAddrInfo: RemoteAddrInfo = 172.21.1.17:5060|1,100,57,1.13280^172.21.1.17^*

09:56:14.816 |//SIP/SIPD(1,67,1)/ccbId=0/scbId=0/restart0_SIPConnControlInd: mTsp.DeviceName[RSDC-SIP-TRUNK] - Rcvd ConnControl with operation = 1, connIdx = 230, X.509 Name = |1,100,57,1.13280^172.21.1.17^*

09:56:14.816 |//SIP/SIPD(1,67,1)/ccbId=0/scbId=0/restart0_SIPConnControlInd: mTsp.DeviceName[RSDC-SIP-TRUNK] - Cannot find TLSConnTbl entry, connIdx = 230, X.509 Name = |1,100,57,1.13280^172.21.1.17^*

09:56:14.823 |//SIP/SIPTcp/wait_SdlReadRsp: SdlRead bufferLen=405|1,100,57,1.13281^10.68.123.17^*

09:56:14.823 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.68.123.17 on port 50777 index 45 with 405 bytes:

[39346,NET]

ACK sip:1@10.69.0.25;user=phone SIP/2.0

Via: SIP/2.0/TCP 10.68.123.17:50777;branch=z9hG4bKd5b1eba1

From: "JAIPUR-SHQ" <49000>;tag=34bdc82c372e0b43a4061e52-f2ea0dc9

To: <1>;tag=13413~fe35675e-a436-4ec8-bf77-d6fc820b0f75-18288988

Call-ID: 34bdc82c-372e0041-061e4a0c-acea8753@10.68.123.17

Date: Mon, 28 Jan 2013 04:26:14 GMT

CSeq: 101 ACK

Content-Length: 0

|1,100,57,1.13281^10.68.123.17^*

09:56:14.823 |//SIP/SIPTcp/wait_SdlReadRsp: SignalCounter = 13279|1,100,57,1.13281^10.68.123.17^*

09:56:14.823 |//SIP/SIPHandler/ccbId=13413/scbId=0/findDevicePID: Routed to SIPD by ccbId/scbId|1,100,57,1.13281^10.68.123.17^*

09:56:14.823 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_CONNECT value=500 retries=6|1,100,57,1.13281^10.68.123.17^*

09:56:14.823 |//SIP/SIPCdpc(1,68,10)/ci=18288988/ccbId=13413/scbId=0/updateCallStatsForCallCompletion: SIPCdpc=10, nodeId=1, processNumber=59|1,100,57,1.13281^10.68.123.17^*

09:56:14.823 |//SIP/SIPCdpc(1,68,10)/ci=18288988/ccbId=13413/scbId=0/terminateOobDtmf: Termination not required.|1,100,57,1.13281^10.68.123.17^*

09:56:14.846 |//SIP/SIPTcp/wait_SdlReadRsp: SdlRead bufferLen=852|1,100,57,1.13282^10.71.235.4^*

09:56:14.846 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.71.235.4 on port 52553 index 123 with 852 bytes:

Following is pic to understand the Scenario

Shakti

This SDI output is missing the SIP INVITE message from that call. So unless you're doing Early Invite it appears that SDP is never getting exchanged. How does the SIP dialog a working call from 8.0 compare against the 8.5 failed call?

Also, what RFC requirement would preclude you from using H.323 ICT?

Please remember to rate helpful responses and identify helpful or correct answers.

Shakti Chauhan
Level 1
Level 1

Shanpshot of Configuration on CUCM 4.1

SIP Trunk

Route Pattern

PT and CSS

Thanks

Shakti

Hi

can you post the sip trunk security profiles configuration that you have in both cucm for the sip trunk?

Note:

Also i agree with chris solution

Please rate all useful posts Regards Chrysostomos ""The Most Successful People Are Those Who Are Good At Plan B""

Shakti Chauhan
Level 1
Level 1

Hello Friends,

RFC Contraint is the Trunk Should be using SIP with RSVP to Route the call between two cluster.

The screenshots of CUCM 8.5  Sip Security Profile, Sip Profile, Sip Trunk Profile and Route Pattern is attach with this message.

I'll be uploading the the Complete SDI and SDL loggs soon.

Thanks

Shakti

Shakti Chauhan
Level 1
Level 1

Pls. find the SDi trace attached with this message

Thxs

Shakti,

Your trace still doesnt contain the beginning of the call. We do not see the original Invite from CUCM8.6 to CUCM4.1. The trace begins with a trying coming back from CUCM4.1. We also did not see the SCCP/SIP traces for the device originating the call on CUCM8.6. You need to send the full traces. Both on CUCM8.6 and CUCM4.1. We are seeing a service unavailable coming from CUCM4.1 but we dont have traces for that

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts