Hi @aokanlawon,
Thank you very much for the detail explanation of the steps. It is helpful to understand the call flow in detail.
I am also glad that you look into this one in particular because I think it is a bug, but I don't want to open the TAC case, which I expect that I would have to jump through the hoops simply to hand the information in (well, on the plate too).
2. CUCM sends a Delayed offer to insert MOH or to resume Media stream
we also saw a DO sent to CUBE
.NB: CUCM expects a sendrecv offer with SDP to the DO. (NB:if cucm gets an inactive offer SDP in the 200 OK instead of providing a send-recv offer SDP, the media path remains in an inactive state and causes calls to dropcall will drop),CUCM sends an ACK with sendonly to the 200 OK
Here is where thing usually break. I suggest you look at the 200 OK received from the SBC..what is contained in the offer? is inactive?
The DO RE-INVITE is happening at time 10:30:03.932 (CUCM->CUBE) and 10:30:03.936 (CUBE->SBC).
=================================================================
Sep 11 10:30:03.936: //69305/47D1F6000004/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:+REMOTE_DN@FAR_END_SBC_IP:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP CUBE_IP:5060;branch=z9hG4bK79923D1
From: ;tag=5226AFD8-E3
To: ;tag=1355766~968f888f-ba3a-4701-bd83-3fce8ea74ec4-36044009
Date: Wed, 11 Sep 2013 00:30:03 GMT
Call-ID: 1ED9066E-19B011E3-916A8BFC-ED9F96AC@CUBE_IP
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 1204942336-0000065536-0000269049-3255516170
User-Agent: Cisco-SIPGateway/IOS-15.2.2.T1
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 103 INVITE
Max-Forwards: 70
Timestamp: 1378859403
Contact:
Expires: 180
Allow-Events: kpml, telephone-event
Session-Expires: 1800;refresher=uas
Content-Length: 0
=================================================================
Here is where thing usually break. I suggest you look at the 200 OK received from the SBC..what is contained in the offer?
is inactive?
The response from SBC @ 10:30:04.140
=================================================================
Sep 11 10:30:04.140: //69305/47D1F6000004/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP CUBE_IP:5060;branch=z9hG4bK79923D1
From: ;tag=5226AFD8-E3
To: ;tag=1355766~968f888f-ba3a-4701-bd83-3fce8ea74ec4-36044009
Call-ID: 1ED9066E-19B011E3-916A8BFC-ED9F96AC@CUBE_IP
CSeq: 103 INVITE
Timestamp: 1378859403
Date: Wed, 11 Sep 2013 00:30:03 GMT
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence, kpml
Supported: replaces
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uas
Require: timer
Remote-Party-ID: "JabberUser FullName" <8449>;party=called;screen=yes;privacy=off
Contact: <>
Content-Type: application/sdp
Content-Length: 1064
v=0
o=CiscoSystemsCCM-SIP 1355766 3 IN IP4 FAR_END_SBC_MEDIA_IP
s=SIP Call
b=TIAS:4000000
b=AS:4000
t=0 0
m=audio 58370 RTP/AVP 104 105 0 8 18 101
c=IN IP4 FAR_END_SBC_MEDIA_IP
a=rtpmap:104 G7221/16000
a=fmtp:104 bitrate=32000
a=rtpmap:105 G7221/16000
a=fmtp:105 bitrate=24000
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:18 G729/8000
a=ptime:20
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
m=video 58350 RTP/AVP 97
c=IN IP4 FAR_END_SBC_MEDIA_IP
b=TIAS:4000000
a=label:11
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42E01F;packetization-mode=0;max-fs=3601;level-asymmetry-allowed=1
a=imageattr:97 recv [x=[32:1:1280],y=[18:1:720],par=1.7778,q=1.00]
a=content:main
m=video 58322 RTP/AVP 97
c=IN IP4 FAR_END_SBC_MEDIA_IP
b=TIAS:4000000
a=label:12
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42E01F;packetization-mode=0;max-fs=3601;level-asymmetry-allowed=1
a=content:slides
m=application 58398 UDP/BFCP *
c=IN IP4 FAR_END_SBC_MEDIA_IP
a=floorctrl:c-s
a=floorid:2 mstrm:12
a=confid:7
a=userid:7
=================================================================
