Good day
CUBE---------dtmf ?----------Third Party Server
I would like to know what DTMF is negotiated on a CUBE by looking at Debugs.
I configured dtmf sip-info (out of band) on a dial-peer linking to a 3rd party server.
The 3rd party server administrator claims he is receiving inband dtmf, but he should be receving sip-info dtmf (out of band)
You will find bellw the debug CCSIP message that includes the sdp sent by the CUBE and the sdp received from the 3rd party
How can I know if sip-info or sip-notify or rtp-nte was negotiated ?
Thanks
1373372: *Aug 22 21:37:03.609: //279311/C34DF8EC9940/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:*30018322148610@198.20.53.102:5060 SIP/2.0
Via: SIP/2.0/UDP 198.20.55.250:5060;branch=z9hG4bKA61421574
From: "Telecom" <sip:+16134531300@cube2>;tag=1758F4B4-2556
To: <sip:*30018322148610@198.20.53.102>
Date: Sat, 22 Aug 2015 21:37:03 GMT
Call-ID: C34E4700-484C11E5-9946DFEA-8EA6030D@cube2
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 3276667116-1212944869-2571165674-2393244429
User-Agent: Cisco-SIPGateway/IOS-15.4.3.M3
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1440279423
Contact: <sip:+16134531300@198.20.55.250:5060>
Expires: 60
Allow-Events: telephone-event
Max-Forwards: 18
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 194
v=0
o=CiscoSystemsSIP-GW-UserAgent 1179 6211 IN IP4 198.20.55.250
s=SIP Call
c=IN IP4 198.20.55.250
t=0 0
m=audio 19986 RTP/AVP 0
c=IN IP4 198.20.55.250
a=rtpmap:0 PCMU/8000
a=ptime:20
1373373: *Aug 22 21:37:03.613: //279311/C34DF8EC9940/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP 198.20.55.250:5060;branch=z9hG4bKA61421574
From: "Telecom" <sip:+16134531300@cube2>;tag=1758F4B4-2556
To: <sip:*30018322148610@198.20.53.102>
Call-ID: C34E4700-484C11E5-9946DFEA-8EA6030D@cube2
CSeq: 101 INVITE
Server: Semafone CCM V.3.1.4
Content-Length: 0
1373374: *Aug 22 21:37:03.617: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:*30018322148610@198.20.55.251:5060 SIP/2.0
Record-Route: <sip:198.20.53.134;r2=on;lr=on;ftag=1758F4B4-2556;TenantID=A>
Record-Route: <sip:198.20.53.102;r2=on;lr=on;ftag=1758F4B4-2556;TenantID=A>
Via: SIP/2.0/UDP 198.20.53.134;branch=z9hG4bK4f3f.c3f014181b86bfbeb1d90d35cccb4fbd.0
Via: SIP/2.0/UDP 198.20.55.250:5060;branch=z9hG4bKA61421574
From: "Telecom" <sip:+16134531300@cube2>;tag=1758F4B4-2556
To: <sip:*30018322148610@198.20.53.102>
Date: Sat, 22 Aug 2015 21:37:03 GMT
Call-ID: C34E4700-484C11E5-9946DFEA-8EA6030D@cube2
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 3276667116-1212944869-2571165674-2393244429
User-Agent: Cisco-SIPGateway/IOS-15.4.3.M3
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1440279423
Contact: <sip:+16134531300@198.20.55.250:5060>
Expires: 60
Allow-Events: telephone-event
SEMA-DPM-Target: http://198.20.53.11:8443
Max-Forwards: 16
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 194
v=0
o=CiscoSystemsSIP-GW-UserAgent 1179 6211 IN IP4 198.20.55.250
s=SIP Call
c=IN IP4 198.20.55.250
t=0 0
m=audio 19986 RTP/AVP 0
c=IN IP4 198.20.55.250
a=rtpmap:0 PCMU/8000
a=ptime:20
1373375: *Aug 22 21:37:03.619: //279312/C34DF8EC9940/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 198.20.53.134;branch=z9hG4bK4f3f.c3f014181b86bfbeb1d90d35cccb4fbd.0,SIP/2.0/UDP 198.20.55.250:5060;branch=z9hG4bKA61421574
From: "Telecom" <sip:+16134531300@cube2>;tag=1758F4B4-2556
To: <sip:*30018322148610@198.20.53.102>
Date: Sat, 22 Aug 2015 21:37:03 GMT
Call-ID: C34E4700-484C11E5-9946DFEA-8EA6030D@cube2
Timestamp: 1440279423
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.4.3.M3
Content-Length: 0
