The only difference I was able to find between the working and nonworking is that the Create Connection Response is received before the outgoing invite in the working scenario: Create Connection: 16:15:17.423 |MGCPHandler send msg SUCCESSFULLY to: 10.128.0.2 CRCX 1822574 S0/SU0/DS1-0/[email protected] MGCP 0.1 C: D000000002e69403000000F58000051d X: b L: p:20, a:PCMU, s:off, t:b8 M: recvonly R: D/[0-9ABCD*#] Q: process,loop |2,100,153,1.1390558^10.128.0.2^*
Create Connection Response: 16:15:17.433 |MGCPHandler received msg from: 10.128.0.2 200 1822574 OK I: D2D7 v=0 c=IN IP4 10.128.0.2 m=audio 19388 RTP/AVP 0 100 a=rtpmap:100 X-NSE/8000 a=fmtp:100 192-194,200-202 a=X-sqn:0 a=X-cap: 1 audio RTP/AVP 100 a=X-cpar: a=rtpmap:100 X-NSE/8000 a=X-cpar: a=fmtp:100 192-194,200-202 a=X-cap: 2 image udptl t38 |2,100,152,1.5650860^10.128.0.2^* Outgoing Invite: 16:15:17.468 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.14.0.46 on port 5460 index 2245 [3153414,NET] INVITE sip:[email protected]:5460 SIP/2.0 Via: SIP/2.0/TCP 10.128.4.10:5060;branch=z9hG4bK9ddfe2fc1b6c2 From: <sip:[email protected] >;tag=918923~30427db0-275c-441d-b31f-5c77cf1a9379-48665604 To: <sip:[email protected]> Date: Sat, 29 Mar 2014 20:15:17 GMT Call-ID: [email protected] Supported: timer,resource-priority,replaces Min-SE: 1800 User-Agent: Cisco-CUCM8.5 Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY CSeq: 101 INVITE Expires: 300 Allow-Events: presence Supported: X-cisco-srtp-fallback Supported: Geolocation Cisco-Guid: 3604545024-0000065536-0000204906-0168067082 Session-Expires: 1800 P-Asserted-Identity: <sip:[email protected]> Remote-Party-ID: <sip:[email protected] >;party=calling;screen=yes;privacy=off Contact: <sip:[email protected]:5060;transport=tcp> Max-Forwards: 70 Content-Type: application/sdp Content-Length: 210 v=0 o=CiscoSystemsCCM-SIP 2000 1 IN IP4 10.128.4.10 s=SIP Call c=IN IP4 10.128.4.10 t=0 0 m=audio 28102 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=ptime:20 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 Here's what the nonworking looks like: Create Connection: 16:17:47.391 |MGCPHandler send msg SUCCESSFULLY to: 10.128.4.12 CRCX 1822579 S0/SU3/DS1-0/[email protected] MGCP 0.1 C: D000000002e69406000000F58000048a X: e L: p:20, a:PCMU, s:off, t:b8 M: recvonly R: D/[0-9ABCD*#] Q: process,loop |2,100,153,1.1390562^10.128.4.12^* OpenLogicalChannelAck from MTP: 383984245 |2014/03/29 16:17:47.406 |100 |SdlSig-I |MXAgenaOpenLogicalChannelAck |outCall_waitOLCAck |SIPCdpc(2,100,68,205070) |MediaTerminationPointControl(1,100,122,3) |1,100,50,1.79616142^10.128.4.10^MTP_3 |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] rc=0 partyId=34213137 port=28106 ipAddrType=0 ipv4=10.128.4.10 Outgoing invite with a=inactive: 16:17:47.407 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 10.14.0.46 on port 5460 index 2245 [3153448,NET] INVITE sip:[email protected]:5460 SIP/2.0 Via: SIP/2.0/TCP 10.128.4.10:5060;branch=z9hG4bK9de045e6642c From: <sip:[email protected] >;tag=918936~30427db0-275c-441d-b31f-5c77cf1a9379-48665607 To: <sip:[email protected]> Date: Sat, 29 Mar 2014 20:17:47 GMT Call-ID: [email protected] Supported: timer,resource-priority,replaces Min-SE: 1800 User-Agent: Cisco-CUCM8.5 Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY CSeq: 101 INVITE Expires: 300 Allow-Events: presence Supported: X-cisco-srtp-fallback Supported: Geolocation Cisco-Guid: 0809577728-0000065536-0000204907-0168067082 Session-Expires: 1800 P-Asserted-Identity: <sip:[email protected]> Remote-Party-ID: <sip:[email protected] >;party=calling;screen=yes;privacy=off Contact: <sip:[email protected]:5060;transport=tcp> Max-Forwards: 70 Content-Type: application/sdp Content-Length: 222 v=0 o=CiscoSystemsCCM-SIP 2000 1 IN IP4 10.128.4.10 s=SIP Call c=IN IP4 10.128.4.10 t=0 0 m=audio 28106 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=ptime:20 a=inactive a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 Create connection response comes after this: 16:17:47.408 |MGCPHandler received msg from: 10.128.4.12 200 1822579 OK I: 1430EE v=0 c=IN IP4 10.128.4.12 m=audio 18048 RTP/AVP 0 100 a=rtpmap:100 X-NSE/8000 a=fmtp:100 192-194 It could be a potential race condition. He's running 8.5.1 base so definitely huge bug potential here. I found https://tools.cisco.com/bugsearch/bug/CSCtk77040 which seems to be a good match based on the conditions. I would try getting rid of the MTP Required on the SIP Trunk and see if that resolves the issue. If so, you should probably upgrade to the latest 8.5.1 SU if you need to send Early Media. -Brian Meade On Sun, Mar 30, 2014 at 3:38 PM, Amit Kumar <[email protected]> wrote: > Seems to be 8.5.1 , 16:11:57.327 HDR|03/29/2014 > CCM,StandAloneCluster,10.128.4.10,Detailed,8.5.1.10000-26|*^*^* > 16:11:57.327 | > > checking traces Raj > > > On Sun, Mar 30, 2014 at 11:18 PM, Heim, Dennis <[email protected]>wrote: > >> CUCM version is? >> >> >> >> *Dennis Heim | Solution Architect (Collaboration)* >> >> World Wide Technology, Inc. | 314-212-1814 >> >> >> >> *PS Engineering: ** Innovate & Ignite.* >> >> >> >> >> >> *From:* cisco-voip [mailto:[email protected]] *On >> Behalf Of *Rajkumar Yadav >> *Sent:* Sunday, March 30, 2014 3:16 AM >> *To:* [email protected] >> *Subject:* [cisco-voip] SIP call issue, call get connected after 10 sec. >> >> >> >> Hi, >> >> >> >> Please kind request to help me for the attached logs. >> >> >> >> setup is like this >> >> >> >> PSTN--MGCP---CUCM--SIP Trunk--Genesys Contact center. >> >> >> >> Option selected in SIP trunk is MTP checked (DTMF interoperabiltiy), from >> SIP profile Early offer. >> >> >> >> Issue is sometime call goes good and sometime call connected after 10 sec. >> >> >> >> We get media inactive and reinvite makes the connection goes good. >> >> >> >> For good call Call-ID: [email protected] >> >> >> >> For Bad call Call-ID: [email protected] >> >> >> >> Kind Regards, >> >> Raaj. >> >> >> >> >> >> _______________________________________________ >> cisco-voip mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-voip >> >> > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
