Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

what debug for seeing DTMF tones via CUBE -SIP?

On a 3845 running 12.4 20, the DTMF tones (for menu options) are not getting passed from the PSTN into the network after the call is established.  The router is using CUBE software and passes the call to the PSTN via SIP trunking/SIP server.  The call is established at G729. I'm using debug voip ccapi inout and debug sip messages, but I don't see the digits being passed.

1.  Am I using the right debugs?  If not, which ones do I use?

2.  At G729, are the tones compressed, or are they out of band?

Everyone's tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: what debug for seeing DTMF tones via CUBE -SIP?

Then this is all you need to get:

debug voip ccapi inout

debug ccsip all

debug voip rtp sess name

You can look at the 'ccsip all' debug and see where it says 'negotiated dtmf relay' on each leg to ensure that rtp-nte was negotiated, and what payload type was negotiated.

Who is the SIP provider?  If it is Verizon, you need to configure 'dtmf-interworking rtp-nte' configured under 'voice service voip since there are timing issues with thier SBC regarding the RTP-NTE packets.

26 REPLIES
New Member

Re: what debug for seeing DTMF tones via CUBE -SIP?

Depends on what you have configured on your voip dial peer that is used to send to your SIP provider.

Most SIP providers support RFC2833 for dtmf relay, on the voip dial peer it would be configured as dtmf-relay rtp-nte.

The debug to see this would be "debug voip rtp session named-event".

Cisco Employee

Re: what debug for seeing DTMF tones via CUBE -SIP?

Depends on the DTMF payload type.  If it's RFC2833 DTMF then they will be a special type of RTP packet sent in-band.  If it is KPML or SIP-Notify DTMF then it would be out-of-band  in SIP messages.

For 2833 DTMF use debug voip rtp session named-event to see the in-band DTMF packets as they hit the router.

Check out http://www.cisco.com/en/US/docs/ios/12_3/sip/configuration/guide/chapter8.html#wp1037760 for examples of OOB DTMF.

Re: what debug for seeing DTMF tones via CUBE -SIP?

Thanks for the response.  Would the call, at some point, go to H323 within the CUBE and get picked up by the debugs I was doing?

Cisco Employee

Re: what debug for seeing DTMF tones via CUBE -SIP?

d.anthony.hadley wrote:

Thanks for the response.  Would the call, at some point, go to H323 within the CUBE and get picked up by the debugs I was doing?

Only if CM is doing H323 to CUBE.  Then you'd see DTMF via h245-signal from CM, shown with an h245 asn1 debug.

Re: what debug for seeing DTMF tones via CUBE -SIP?

I found that the problem happens when they use G729.  Since the RFC2833 DTMF tones are inband, would G729 compress the tones so that they are not recognized?  Or, could there be something else going on here?  Thanks.

Cisco Employee

Re: what debug for seeing DTMF tones via CUBE -SIP?

RTP-NTE is not in-band audio.  A lot of people refer to RTP-NTE as in0band, but I think that's a bad way to describe it.  It's in the media path, sure, but

I consider in-band to mean in-the-audio which RTP-NTE isn't since the payload type is different (and the digits are transmitted via data, not g.7xx audio)

Hence, g.729 does not effect RTP-NTE digits in any way.  g.729 would only affect digits that are in the actual audio stream, which won't happen in a CUCM environment unless you invoke a transcoder and have dtmf-relay on one side and not the other.

If you still have DTMF issues, it's a misconfiguration somewhere.  Likely a dial-peer match is incorrect, or the SIP side isn't using PT 101 for RTP-NTE.  Collect:

debug voip rtp sess name

debug h245 asn1

debug h225 asn1

debug cch323 all

debug voip ccapi inout

debug ccsip all

Collect the debugs in the following manner, place a test call, and hit some DTMF:

Router(config)# service sequence
Router(config)# service timestamps debug datetime msec
Router(config)# logging buffered 10000000 7
Router(config)# no logging con
Router(config)# no logging mon
Router(config)# voice iec syslog

Router# term len 0

Router# sh logg

Re: what debug for seeing DTMF tones via CUBE -SIP?

I'm working on setting up another test.  All the dial peers have the dtmf relay rtp-nte command on them.  Could it be a misconfig somewhere else?  I don't have access to the SIP side.  What do I ask about the PT 101 for RTP-NTE?  Would it be in their traces?  Thanks.

Cisco Employee

Re: what debug for seeing DTMF tones via CUBE -SIP?

debug ccsip mess will show RTP NTE cap in the SDP...something like

m=audio XXX RTP/AVP  101 
a=rtpmap:101 telephone-event/8000

101 is the payload type.  101 is default and can be changed.

deb voip rtp session named-event   will show you rfc2833 packets with PT=101 for dtmf events/digits.

HTH,

DK

Cisco Employee

Re: what debug for seeing DTMF tones via CUBE -SIP?

Your H323 dial-peer should have 'dtmf-relay h245-alpha' confiugred on it, not rtp-nte.

Make sure calls from CUCM via H323 to CUBE match the right inbound dial-peer, which should be an H323 dial-peer.  Verify with 'sh call active voice br' and look at the pid: for the first leg for that (or run debug voip ccapi inout).  If you're matching a SIP peer on the inbound leg when the call comes in from H323, you need to correct your dial-peer matching.

EDIT: Although I'm not sure if you are using H323 or SIP to CM.

Re: what debug for seeing DTMF tones via CUBE -SIP?

These are the dial peers in and out that the call is hitting.  Do I need the 'dtmf-relay h245-alpha' command on both of these?  Almost all of the calls use these two dial peers, according to the 'sho call active voice brief' and they are sip call legs.  There are no h323 call legs.

This is the dial peer it's hitting on the way in according to the debug 'voip ccapi inout'

017203: Oct  5 09:25:06 EDT:
   Incoming Dial-peer=101, Progress Indication=NULL(0), Calling IE Present=TRUE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=

dial-peer voice 101 voip
description from CUCM
session protocol sipv2
incoming called-number ^001T
dtmf-relay rtp-nte digit-drop
fax rate disable
fax protocol none
no vad

This is the outgoing dial peer according to the debug


017218: Oct  5 09:25:06 EDT:
   Destination=, Calling IE Present=TRUE, Mode=0,
   Outgoing Dial-peer=100, Params=0x73E5D890, Progress Indication=NULL(0)


dial-peer voice 100 voip
description outbound voice to SIP
translation-profile outgoing strip
destination-pattern ^001T
voice-class sip options-ping 90
voice-class sip early-offer forced
session protocol sipv2
session target ipv4:X.X.X.X:5535
dtmf-relay rtp-nte
fax protocol none
no vad

Cisco Employee

Re: what debug for seeing DTMF tones via CUBE -SIP?

Hmm...not clear if you are using h323 or  SIP between cube and ccm ?

If its SIP, the dialpeers look good. If h323, you'd add  dtmf-relay h245-alpha h245-sig

to the dialpeer towards CCM.

What do u see for negotiated dtmf-relay in show call active voice and show sip call ?

Re: what debug for seeing DTMF tones via CUBE -SIP?

All the call legs are SIP.

Cisco Employee

Re: what debug for seeing DTMF tones via CUBE -SIP?

Then this is all you need to get:

debug voip ccapi inout

debug ccsip all

debug voip rtp sess name

You can look at the 'ccsip all' debug and see where it says 'negotiated dtmf relay' on each leg to ensure that rtp-nte was negotiated, and what payload type was negotiated.

Who is the SIP provider?  If it is Verizon, you need to configure 'dtmf-interworking rtp-nte' configured under 'voice service voip since there are timing issues with thier SBC regarding the RTP-NTE packets.

Re: what debug for seeing DTMF tones via CUBE -SIP?

I saw the DTMF in the debug.   In this case, I was looking for a number 9.  You'll see it in the debug below.  It was a call from the network, through a CUBE router, into the telco (Verizon) SIP cloud.  The user on the outside would hit the 9 button to triger an option.  This was seen from both my side (network side) and the SIP side.  Debug was on the CUBE.

Look for "Relaying Digit 9 to dstCallId"

066011: Oct 11 14:19:03 EDT: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event: ccsip_spi_get_msg_type returned: 3 for event 15
066012: Oct 11 14:19:03 EDT: //1454496/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin:
   Consume mask is not set. Relaying Digit 9 to dstCallId 0x16319F
066013: Oct 11 14:19:03 EDT: //1454496/xxxxxxxxxxxx/CCAPI/cc_relay_digit_begin_for_3way_conference:
   Check DTMF relay digit begin for 3way conf
066014: Oct 11 14:19:03 EDT:          s=VoIP d=DSP payload 0x65 ssrc 0x301AAA14 sequence 0x5B2 timestamp 0x3193F4
066015: Oct 11 14:19:03 EDT:  << Pt:101    Evt:9       Pkt:0A 01 40

Thanks for all the help and responses.

New Member

Re: what debug for seeing DTMF tones via CUBE -SIP?

Was there a resolution to this issue?


Thanks.

Re: what debug for seeing DTMF tones via CUBE -SIP?


Yes, there was a resolution.  It was the three debugs noted previously in the posts,
debug voip ccapi inout

debug ccsip all

debug voip rtp sess name

I was looking for the digit 9 to pass through.  You can see it in the debug ccapi as "Relaying Digit 9 to dstCallId"

New Member

what debug for seeing DTMF tones via CUBE -SIP?

Hi,

Can anyone suggest what Cisco DTMF method can be configured under the Dial-Peer that will transmit the digits within the g.7xx audio i.e. pure in-band DTMF payload ?

Regards,

Tiberie

Cisco Employee

what debug for seeing DTMF tones via CUBE -SIP?

Hi Tiberie,

Not sure why would you want to do that but in that case you want to configure no dtmf-relay CLI under dialpeer to carry the dtmf digits in the voice codec.

HTH,

DK

New Member

what debug for seeing DTMF tones via CUBE -SIP?

Thanks Dilip,

The service provider SIP platform supports the DTMF standard under RFC2833  or in other words, pure in-band (DTMF tones in the actual audio stream). So, in some situation when the call goes to certain AA/IVR systems, the relayed DTMF tones are not relayed and properly recognized by the other side.

I've read that "rtp-nte" is not actualy doing in-band transmition of the DTFM tones, rather the digits are transmitted via data, not in-the-audio of the g.7xx codec.

That's why, I was asking if there is a way to configure the SIP dial-peers on the CUBE to send the compatible DTMF tones to the SP.

Wll try the "no dtmf-relay" metod.

Thank You for the assistance.

Regards,

Tiberie

Cisco Employee

what debug for seeing DTMF tones via CUBE -SIP?

Hmm, if the SP SIP gear supports RFC2833 dtmf method then what you really want on the CUBE dialpeer is dtmf-relay rtp-nte. Some consider RFC2833 to be inband as dtmf  digits are carried in the RTP stream (using a different payload type than voice)

Infact rt-nte/rfc2833 is  actually out of band as dtmf is simply signaled using RTP events to the other side and not really processed through the voice codec.

Thanks.

DK

New Member

what debug for seeing DTMF tones via CUBE -SIP?

An UPDATE:

I used the commands:"dtmf-interworking standard" under the two dial-peers (cucm/cube & cube/SP) and the DTMF tones were transmitted/received fine from then onwards. The SIP SP is accepting only In-band tones for telephony events i.e. as part of the voice waveform. See http://tools.ietf.org/html/rfc4733#

While the command "dtmf rtp-nte" is sending telephony events out-of-band but within the RTP session, which is not in reality an in-band method.

VIP Super Bronze

what debug for seeing DTMF tones via CUBE -SIP?

Tiberie,

I am curious to see what the sip messages look like..can you do a test call to itsp and send debug ccsip messages

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

what debug for seeing DTMF tones via CUBE -SIP?

Sure. But it might take me a while since the client mentioned to me that they are super busy today and the following week. Will update once I have the debug output.

New Member

what debug for seeing DTMF tones via CUBE -SIP?

HI aokanlawon ,

I finaly managed to get the debuf output from the "debug ccsip messages" and "debug voice ccapi inout" command.

Sorry for the long debug log, I don't have chance anywhere to upload the file. Also, I'm sending at the end, an output from the command "debug voip rtp session named-event"

Can You explain to me what's going on with the type of DTMF beeing transmitted?

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.02.19 17:18:31 =~=~=~=~=~=~=~=~=~=~=~=

Feb 19 17:21:03.254: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:0038923248XXX@10.2.115.15:5060 SIP/2.0

Via: SIP/2.0/UDP 10.2.115.5:5060;branch=z9hG4bK4cce15b002c71

From: "Caller" <>;tag=659027~d01f1c4f-fe32-4ce8-bb98-06bd76f12320-33263464

To: <0038923248XXX>

Date: Wed, 19 Feb 2014 16:21:03 GMT

Call-ID: d2504700-3041d9ef-47e32-573020a@10.2.115.5

Supported: timer,resource-priority,replaces

Min-SE:  1800

User-Agent: Cisco-CUCM9.1

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

CSeq: 101 INVITE

Expires: 180

Allow-Events: presence

Supported: X-cisco-srtp-fallback,X-cisco-original-called

Cisco-Guid: 3528476416-0000065536-0000002046-0091423242

Session-Expires:  1800

P-Asserted-Identity: "Caller" <>

Remote-Party-ID: "Caller" <>;party=calling;screen=yes;privacy=off

Contact: <>

Max-Forwards: 69

Content-Length: 0

Feb 19 17:21:03.258: //-1/D25047000000/CCAPI/cc_api_display_ie_subfields:

   cc_api_call_setup_ind_common:

   cisco-username=+38923167XXX

   ----- ccCallInfo IE subfields -----

   cisco-ani=sip:+38923167XXX@10.2.115.5

   cisco-anitype=0

   cisco-aniplan=0

   cisco-anipi=0

   cisco-anisi=1

   dest=sip:0038923248XXX@10.2.115.15:5060

   cisco-desttype=0

   cisco-destplan=0

   cisco-rdie=FFFFFFFF

   cisco-rdn=

   cisco-rdntype=0

   cisco-rdnplan=0

   cisco-rdnpi=-1

   cisco-rdnsi=-1

   cisco-redirectreason=-1   fwd_final_type =0

   final_redirectNumber =

   hunt_group_timeout =0

Feb 19 17:21:03.262: //-1/D25047000000/CCAPI/cc_api_call_setup_ind_common:

   Interface=0x31340418, Call Info(

   Calling Number=sip:+38923167XXX@10.2.115.5,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),

   Called Number=sip:0038923248XXX@10.2.115.15:5060(TON=Unknown, NPI=Unknown),

   Calling Translated=FALSE, Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE,

   Incoming Dial-peer=10, Progress Indication=NULL(0), Calling IE Present=TRUE,

   Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=176022

Feb 19 17:21:03.262: //-1/D25047000000/CCAPI/ccCheckClipClir:

   In: Calling Number=sip:+38923167XXX@10.2.115.5(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)

Feb 19 17:21:03.262: //-1/D25047000000/CCAPI/ccCheckClipClir:

   Out: Calling Number=sip:+38923167XXX@10.2.115.5(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)

Feb 19 17:21:03.262: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb 19 17:21:03.262: :cc_get_feature_vsa malloc success

Feb 19 17:21:03.262: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb 19 17:21:03.262:  cc_get_feature_vsa count is 1

Feb 19 17:21:03.262: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb 19 17:21:03.262: :FEATURE_VSA attributes are: feature_name:0,feature_time:833881656,feature_id:160387

Feb 19 17:21:03.262: //176022/D25047000000/CCAPI/cc_api_call_setup_ind_common:

   Set Up Event Sent;

   Call Info(Calling Number=(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),

   Called Number=(TON=Unknown, NPI=Unknown))

Feb 19 17:21:03.262: //176022/D25047000000/CCAPI/cc_process_call_setup_ind:

   Event=0x31845110

Feb 19 17:21:03.262: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:

   Try with the demoted called number 0038923248XXX

Feb 19 17:21:03.262: //176022/D25047000000/CCAPI/ccCallSetContext:

   Context=0x2B07195C

Feb 19 17:21:03.262: //176022/D25047000000/CCAPI/cc_process_call_setup_ind:

   >>>>CCAPI handed cid 176022 with tag 10 to app "_ManagedAppProcess_Default"

Feb 19 17:21:03.262: //176022/D25047000000/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 10.2.115.5:5060;branch=z9hG4bK4cce15b002c71

From: "Caller" <>;tag=659027~d01f1c4f-fe32-4ce8-bb98-06bd76f12320-33263464

To: <0038923248XXX>

Date: Wed, 19 Feb 2014 16:21:03 gmt

Call-ID: d2504700-3041d9ef-47e32-573020a@10.2.115.5

CSeq: 101 INVITE

Allow-Events: telephone-event

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

Feb 19 17:21:03.262: //176022/D25047000000/CCAPI/ccCallProceeding:

   Progress Indication=NULL(0)

Feb 19 17:21:03.262: //-1/xxxxxxxxxxxx/CCAPI/ccGetMemPoolFromContainer:

   mempool not found from usrContainer(31823634)

Feb 19 17:21:03.262: //-1/xxxxxxxxxxxx/CCAPI/ccCreateMemPoolInContainer:

   Mempool(2AFD4B64) created in usrContainer(31823634)

Feb 19 17:21:03.266: //176022/D25047000000/CCAPI/ccCallSetupRequest:

   Destination=, Calling IE Present=TRUE, Mode=0,

   Outgoing Dial-peer=20, Params=0x2B06551C, Progress Indication=NULL(0)

Feb 19 17:21:03.266: //176022/D25047000000/CCAPI/ccCheckClipClir:

   In: Calling Number=sip:+38923167XXX@10.2.115.5(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)

Feb 19 17:21:03.266: //176022/D25047000000/CCAPI/ccCheckClipClir:

   Out: Calling Number=sip:+38923167XXX@10.2.115.5(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)

Feb 19 17:21:03.266: //176022/D25047000000/CCAPI/ccCallSetupRequest:

   Destination Pattern=.T, Called Number=0038923248XXX, Digit Strip=FALSE

Feb 19 17:21:03.266: //176022/D25047000000/CCAPI/ccCallSetupRequest:

   Calling Number=sip:+38923167XXX@10.2.115.5(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),

   Called Number=0038923248XXX(TON=Unknown, NPI=Unknown),

   Redirect Number=, Display Info=Caller

   Account Number=+38923167XXX, Final Destination Flag=TRUE,

   Guid=D2504700-0001-0000-0000-07FE0573020A, Outgoing Dial-peer=20

Feb 19 17:21:03.266: //176022/D25047000000/CCAPI/cc_api_display_ie_subfields:

   ccCallSetupRequest:

   cisco-username=+38923167XXX

   ----- ccCallInfo IE subfields -----

   cisco-ani=sip:+38923167XXX@10.2.115.5

   cisco-anitype=0

   cisco-aniplan=0

   cisco-anipi=0

   cisco-anisi=1

   dest=0038923248XXX

   cisco-desttype=0

   cisco-destplan=0

   cisco-rdie=FFFFFFFF

   cisco-rdn=

   cisco-rdntype=0

   cisco-rdnplan=0

   cisco-rdnpi=-1

   cisco-rdnsi=-1

   cisco-redirectreason=-1   fwd_final_type =0

   final_redirectNumber =

   hunt_group_timeout =0

Feb 19 17:21:03.266: //176022/D25047000000/CCAPI/ccIFCallSetupRequestPrivate:

   Interface=0x31340418, Interface Type=3, Destination=, Mode=0x0,

   Call Params(Calling Number=sip:+38923167XXX@10.2.115.5,(Calling Name=Caller)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),

   Called Number=0038923248XXX(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,

   Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE, Outgoing Dial-peer=20, Call Count On=FALSE,

   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)

Feb 19 17:21:03.266: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb 19 17:21:03.266: :cc_get_feature_vsa malloc success

Feb 19 17:21:03.266: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb 19 17:21:03.266:  cc_get_feature_vsa count is 2

Feb 19 17:21:03.266: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb 19 17:21:03.266: :FEATURE_VSA attributes are: feature_name:0,feature_time:833881880,feature_id:160388

Feb 19 17:21:03.266: //176023/D25047000000/CCAPI/ccIFCallSetupRequestPrivate:

   SPI Call Setup Request Is Success; Interface Type=3, FlowMode=1

Feb 19 17:21:03.266: //176023/D25047000000/CCAPI/ccCallSetContext:

   Context=0x2B0654CC

Feb 19 17:21:03.266: //176022/D25047000000/CCAPI/ccSaveDialpeerTag:

   Outgoing Dial-peer=20

Feb 19 17:21:03.266: //176023/D25047000000/CCAPI/cc_api_call_proceeding:

   Interface=0x31340418, Progress Indication=NULL(0)

Feb 19 17:21:03.270: //176023/D25047000000/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:0038923248XXX@172.25.255.164:5060 SIP/2.0

Via: SIP/2.0/UDP 10.126.98.37:5060;branch=z9hG4bK31F165A

Remote-Party-ID: "Caller" <>;party=calling;screen=yes;privacy=off

From: sip:+38923167XXX@10.2.115.5;tag=B8DD5C04-CE

To: <0038923248XXX>

Date: Wed, 19 Feb 2014 16:21:03 gmt

Call-ID: A9472160-98B811E3-897DFE89-917343ED@10.126.98.37

Supported: 100rel,timer,resource-priority,replaces,sdp-anat

Min-SE:  1800

Cisco-Guid: 3528476416-0000065536-0000002046-0091423242

User-Agent: Cisco-SIPGateway/IOS-12.x

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

CSeq: 101 INVITE

Timestamp: 1392826863

Contact: <>

Expires: 180

Allow-Events: telephone-event

Max-Forwards: 68

Session-Expires:  1800

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 331

v=0

o=CiscoSystemsSIP-GW-UserAgent 9057 1587 IN IP4 10.126.98.37

s=SIP Call

c=IN IP4 10.126.98.37

t=0 0

m=audio 19826 RTP/AVP 0 8 18 101 19

c=IN IP4 10.126.98.37

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=yes

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=rtpmap:19 CN/8000

Feb 19 17:21:03.286: //176023/D25047000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 10.126.98.37:5060;branch=z9hG4bK31F165A

From: sip:+38923167XXX@10.2.115.5;tag=B8DD5C04-CE

To: <0038923248XXX>

Call-ID: A9472160-98B811E3-897DFE89-917343ED@10.126.98.37

CSeq: 101 INVITE

Timestamp: 1392826863

Feb 19 17:21:03.362: //176023/D25047000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 183 Session Progress

Via: SIP/2.0/UDP 10.126.98.37:5060;branch=z9hG4bK31F165A

From: sip:+38923167XXX@10.2.115.5;tag=B8DD5C04-CE

To: <0038923248XXX>;tag=SDraqe898-2700717777

Call-ID: A9472160-98B811E3-897DFE89-917343ED@10.126.98.37

CSeq: 101 INVITE

Timestamp: 1392826863

Content-Length: 0

Contact: <>

Server: Patton SN4940 1E30V 00A0BA097588 R6.T 2013-04-04_RFE2204 H323 RBS SIP M5T SIP Stack/4.1.12.18

Feb 19 17:21:03.362: //176023/D25047000000/CCAPI/cc_api_event_indication:

   Event=97, Call Id=176023

Feb 19 17:21:03.362: //176023/D25047000000/CCAPI/cc_api_event_indication:

   Event Is Sent To Conferenced SPI(s) Directly

Feb 19 17:21:03.362: //176023/D25047000000/CCAPI/cc_api_call_cut_progress:

   Interface=0x31340418, Progress Indication=NULL(0), Signal Indication=NOT PRESENT(255),

   Cause Value=0

Feb 19 17:21:03.362: //176023/D25047000000/CCAPI/cc_api_call_cut_progress:

   Call Entry(Responsed=TRUE)

Feb 19 17:21:03.362: //176022/D25047000000/CCAPI/ccCallCutProgress:

   Progress Indication=NULL(0), Signal Indication=NOT PRESENT(255), Cause Value=0

   Voice Call Send Alert=FALSE, Call Entry(Alert Sent=FALSE)

Feb 19 17:21:03.362: //176022/D25047000000/CCAPI/ccCallCutProgress:

   Call Entry(Responsed=TRUE)

Feb 19 17:21:03.362: //176022/D25047000000/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 183 Session Progress

Via: SIP/2.0/UDP 10.2.115.5:5060;branch=z9hG4bK4cce15b002c71

From: "Caller" <>;tag=659027~d01f1c4f-fe32-4ce8-bb98-06bd76f12320-33263464

To: <0038923248XXX>;tag=B8DD5C64-7FF

Date: Wed, 19 Feb 2014 16:21:03 gmt

Call-ID: d2504700-3041d9ef-47e32-573020a@10.2.115.5

CSeq: 101 INVITE

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

Allow-Events: telephone-event

Remote-Party-ID: <0038923248XXX>;party=called;screen=no;privacy=off

Contact: <0038923248XXX>

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

Feb 19 17:21:03.506: //176023/D25047000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 10.126.98.37:5060;branch=z9hG4bK31F165A

From: sip:+38923167XXX@10.2.115.5;tag=B8DD5C04-CE

To: <0038923248XXX>;tag=SDraqe898-2700717777

Call-ID: A9472160-98B811E3-897DFE89-917343ED@10.126.98.37

CSeq: 101 INVITE

Timestamp: 1392826863

Content-Length: 0

Contact: <>

Server: Patton SN4940 1E30V 00A0BA097588 R6.T 2013-04-04_RFE2204 H323 RBS SIP M5T SIP Stack/4.1.12.18

Feb 19 17:21:03.506: //176023/D25047000000/CCAPI/cc_api_call_alert:

   Interface=0x31340418, Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)

Feb 19 17:21:03.506: //176023/D25047000000/CCAPI/cc_api_call_alert:

   Call Entry(Retry Count=0, Responsed=TRUE)

Feb 19 17:21:03.506: //176022/D25047000000/CCAPI/ccCallAlert:

   Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)

Feb 19 17:21:03.506: //176022/D25047000000/CCAPI/ccCallAlert:

   Call Entry(Responsed=TRUE, Alert Sent=TRUE)

Feb 19 17:21:03.506: //176022/D25047000000/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 10.2.115.5:5060;branch=z9hG4bK4cce15b002c71

From: "Caller" <>;tag=659027~d01f1c4f-fe32-4ce8-bb98-06bd76f12320-33263464

To: <0038923248XXX>;tag=B8DD5C64-7FF

Date: Wed, 19 Feb 2014 16:21:03 gmt

Call-ID: d2504700-3041d9ef-47e32-573020a@10.2.115.5

CSeq: 101 INVITE

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

Allow-Events: telephone-event

Remote-Party-ID: <0038923248XXX>;party=called;screen=no;privacy=off

Contact: <>

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

Feb 19 17:21:03.730: //176023/D25047000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.126.98.37:5060;branch=z9hG4bK31F165A

From: sip:+38923167XXX@10.2.115.5;tag=B8DD5C04-CE

To: <0038923248XXX>;tag=SDraqe898-2700717777

Call-ID: A9472160-98B811E3-897DFE89-917343ED@10.126.98.37

CSeq: 101 INVITE

Timestamp: 1392826863

Content-Length: 274

Contact: <>

Content-Type: application/sdp

Supported: replaces

Server: Patton SN4940 1E30V 00A0BA097588 R6.T 2013-04-04_RFE2204 H323 RBS SIP M5T SIP Stack/4.1.12.18

v=0

o=MxSIP 0 18772 IN IP4 172.25.255.196

s=SIP Call

c=IN IP4 172.25.255.196

t=0 0

m=audio 20452 RTP/AVP 0 8 18 101

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:18 G729/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:18 annexb=no

a=fmtp:101 0-15

a=sendrecv

Feb 19 17:21:03.734: //176023/D25047000000/CCAPI/cc_api_caps_ind:

   Destination Interface=0x0, Destination Call Id=-1, Source Call Id=176023,

   Caps(Codec=0x1, Fax Rate=0x2, Vad=0x2,

   Modem=0x0, Codec Bytes=160, Signal Type=2)

Feb 19 17:21:03.734: //176023/D25047000000/CCAPI/cc_api_caps_ind:

   Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms),

   Playout Max=1000(ms), Fax Nom=300(ms))

Feb 19 17:21:03.734: //176022/D25047000000/CCAPI/cc_api_caps_ack:

   Destination Interface=0x0, Destination Call Id=176023, Source Call Id=176022,

   Caps(Codec=g711ulaw(0x1), Fax Rate=FAX_RATE_VOICE(0x2), Vad=ON(0x2),

   Modem=OFF(0x0), Codec Bytes=160, Signal Type=2, Seq Num Start=1348)

Feb 19 17:21:03.734: //176023/D25047000000/CCAPI/cc_api_event_indication:

   Event=162, Call Id=176023

Feb 19 17:21:03.734: //176023/D25047000000/CCAPI/cc_api_event_indication:

   Event Is Sent To Conferenced SPI(s) Directly

Feb 19 17:21:03.734: //176023/D25047000000/CCAPI/cc_api_call_connected:

   Interface=0x31340418, Data Bitmask=0x1, Progress Indication=NULL(0),

   Connection Handle=0

Feb 19 17:21:03.734: //176023/D25047000000/CCAPI/cc_api_call_connected:

   Call Entry(Connected=TRUE, Responsed=TRUE, Retry Count=0)

Feb 19 17:21:03.734: //176022/D25047000000/CCAPI/ccConferenceCreate:

   (confID=0x2AFC22A8, callID1=0x2AF96, gcid=A945E877-98B811E3-897AFE89-917343ED, tag=0x0)

Feb 19 17:21:03.734: //176023/D25047000000/CCAPI/ccConferenceCreate:

   (confID=0x2AFC22A8, callID2=0x2AF97, gcid=A945E877-98B811E3-897AFE89-917343ED, tag=0x0)

Feb 19 17:21:03.734: //176022/D25047000000/CCAPI/ccConferenceCreate:

   Conference Id=0x2AFC22A8, Call Id1=176022, Call Id2=176023, Tag=0x0

Feb 19 17:21:03.734: //176022/D25047000000/CCAPI/ccConferenceCreate:

Feb 19 17:21:03.734: ccConferenceCreate: ret1=0, codecMask1=1, bytes1=160, negot1=0, dtmf1=6

                    ret2=0, codecMask2=1, bytes2=160, negot2=1, dtmf2=6,

                    tx_dynamic_pt1=0, rx_dynamic_pt1=0, codec_mode1=0, params_bitmap1 =0

                    tx_dynamic_pt2=0, rx_dynamic_pt2=0, codec_mode2=0, params_bitmap2 =0

Feb 19 17:21:03.734: //176022/D25047000000/CCAPI/ccConferenceCreate:

   delay media to slow start case, codec negotation is not done

Feb 19 17:21:03.734: //176022/xxxxxxxxxxxx/CCAPI/cc_api_get_xcode_stream:

Feb 19 17:21:03.734: cc_api_get_xcode_stream : 4682

Feb 19 17:21:03.734: //176022/D25047000000/CCAPI/cc_api_bridge_done:

   Conference Id=0xF2EA, Source Interface=0x31340418, Source Call Id=176022,

   Destination Call Id=176023, Disposition=0x0, Tag=0x0

Feb 19 17:21:03.734: //176023/xxxxxxxxxxxx/CCAPI/cc_api_get_xcode_stream:

Feb 19 17:21:03.734: cc_api_get_xcode_stream : 4682

Feb 19 17:21:03.734: //176023/D25047000000/CCAPI/cc_api_bridge_done:

   Conference Id=0xF2EA, Source Interface=0x31340418, Source Call Id=176023,

   Destination Call Id=176022, Disposition=0x0, Tag=0x0

Feb 19 17:21:03.734: //176022/D25047000000/CCAPI/cc_generic_bridge_done:

   Conference Id=0xF2EA, Source Interface=0x31340418, Source Call Id=176023,

   Destination Call Id=176022, Disposition=0x0, Tag=0x0

Feb 19 17:21:03.734: //176022/D25047000000/CCAPI/ccConferenceCreate:

   Call Entry(Conference Id=0xF2EA, Destination Call Id=176023)

Feb 19 17:21:03.734: //176023/D25047000000/CCAPI/ccConferenceCreate:

   Call Entry(Conference Id=0xF2EA, Destination Call Id=176022)

Feb 19 17:21:03.734: //176022/D25047000000/CCAPI/cc_process_notify_bridge_done:

   Conference Id=0xF2EA, Call Id1=176022, Call Id2=176023

Feb 19 17:21:03.738: //176023/D25047000000/SIP/Msg/ccsipDisplayMsg:

Sent:

ACK sip:+38923248XXX@172.25.255.164:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.126.98.37:5060;branch=z9hG4bK31F171A4E

From: sip:+38923167XXX@10.2.115.5;tag=B8DD5C04-CE

To: <0038923248XXX>;tag=SDraqe898-2700717777

Date: Wed, 19 Feb 2014 16:21:03 gmt

Call-ID: A9472160-98B811E3-897DFE89-917343ED@10.126.98.37

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: telephone-event

Content-Length: 0

Feb 19 17:21:03.738: //176022/D25047000000/CCAPI/ccCallConnect:

   Progress Indication=NULL(0), Data Bitmask=0x1

Feb 19 17:21:03.738: //176022/D25047000000/CCAPI/ccCallConnect:

   Call Entry(Connected=TRUE, Responsed=TRUE)

Feb 19 17:21:03.738: //176022/D25047000000/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.2.115.5:5060;branch=z9hG4bK4cce15b002c71

From: "Caller" <>;tag=659027~d01f1c4f-fe32-4ce8-bb98-06bd76f12320-33263464

To: <0038923248XXX>;tag=B8DD5C64-7FF

Date: Wed, 19 Feb 2014 16:21:03 gmt

Call-ID: d2504700-3041d9ef-47e32-573020a@10.2.115.5

CSeq: 101 INVITE

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

Allow-Events: telephone-event

Remote-Party-ID: <0038923248XXX>;party=called;screen=no;privacy=off

Contact: <0038923248XXX>

Supported: replaces

Supported: sdp-anat

Server: Cisco-SIPGateway/IOS-12.x

Supported: timer

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 268

v=0

o=CiscoSystemsSIP-GW-UserAgent 4524 2325 IN IP4 10.2.115.15

s=SIP Call

c=IN IP4 10.2.115.15

t=0 0

m=audio 28154 RTP/AVP 0 101 19

c=IN IP4 10.2.115.15

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=rtpmap:19 CN/8000

a=ptime:20

Feb 19 17:21:03.750: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:0038923248XXX@10.2.115.15:5060 SIP/2.0

Via: SIP/2.0/UDP 10.2.115.5:5060;branch=z9hG4bK4cce29f57702

From: "Caller" <>;tag=659027~d01f1c4f-fe32-4ce8-bb98-06bd76f12320-33263464

To: <0038923248XXX>;tag=B8DD5C64-7FF

Date: Wed, 19 Feb 2014 16:21:03 GMT

Call-ID: d2504700-3041d9ef-47e32-573020a@10.2.115.5

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: presence

Content-Type: application/sdp

Content-Length: 233

v=0

o=CiscoSystemsCCM-SIP 659027 1 IN IP4 10.2.115.5

s=SIP Call

c=IN IP4 10.2.52.17

b=TIAS:64000

b=AS:64

t=0 0

m=audio 16388 RTP/AVP 0 101

a=rtpmap:0 PCMU/8000

a=ptime:20

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

Feb 19 17:21:03.754: //176022/D25047000000/CCAPI/cc_api_caps_ind:

   Destination Interface=0x31340418, Destination Call Id=176023, Source Call Id=176022,

   Caps(Codec=0x1, Fax Rate=0x2, Vad=0x2,

   Modem=0x0, Codec Bytes=160, Signal Type=2)

Feb 19 17:21:03.754: //176022/D25047000000/CCAPI/cc_api_caps_ind:

   Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms),

   Playout Max=1000(ms), Fax Nom=300(ms))

Feb 19 17:21:03.754: //176023/D25047000000/CCAPI/cc_api_caps_ack:

   Destination Interface=0x31340418, Destination Call Id=176022, Source Call Id=176023,

   Caps(Codec=g711ulaw(0x1), Fax Rate=FAX_RATE_VOICE(0x2), Vad=ON(0x2),

   Modem=OFF(0x0), Codec Bytes=160, Signal Type=2, Seq Num Start=1)

Feb 19 17:21:03.754: //176022/D25047000000/CCAPI/cc_api_event_indication:

   Event=162, Call Id=176022

Feb 19 17:21:03.754: //176022/D25047000000/CCAPI/cc_api_event_indication:

   Event Is Sent To Conferenced SPI(s) Directly

Feb 19 17:21:03.754: //176022/D25047000000/CCAPI/cc_api_caps_ind:

   Destination Interface=0x31340418, Destination Call Id=176023, Source Call Id=176022,

   Caps(Codec=0x1, Fax Rate=0x2, Vad=0x2,

   Modem=0x0, Codec Bytes=160, Signal Type=2)

Feb 19 17:21:03.754: //176022/D25047000000/CCAPI/cc_api_caps_ind:

   Caps(Playout Mode=1, Playout Initial=60(ms), Playout Min=40(ms),

   Playout Max=1000(ms), Fax Nom=300(ms))

Feb 19 17:21:03.754: //176023/D25047000000/CCAPI/cc_api_caps_ack:

   Destination Interface=0x31340418, Destination Call Id=176022, Source Call Id=176023,

   Caps(Codec=g711ulaw(0x1), Fax Rate=FAX_RATE_VOICE(0x2), Vad=ON(0x2),

   Modem=OFF(0x0), Codec Bytes=160, Signal Type=2, Seq Num Start=1)

Feb 19 17:21:14.410: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

BYE sip:0038923248XXX@10.2.115.15:5060 SIP/2.0

Via: SIP/2.0/UDP 10.2.115.5:5060;branch=z9hG4bK4cce43ae98389

From: "Caller" <>;tag=659027~d01f1c4f-fe32-4ce8-bb98-06bd76f12320-33263464

To: <0038923248XXX>;tag=B8DD5C64-7FF

Date: Wed, 19 Feb 2014 16:21:03 GMT

Call-ID: d2504700-3041d9ef-47e32-573020a@10.2.115.5

User-Agent: Cisco-CUCM9.1

Max-Forwards: 70

P-Asserted-Identity: "Caller" <>

CSeq: 102 BYE

Reason: Q.850;cause=16

Content-Length: 0

Feb 19 17:21:14.410: //176023/D25047000000/CCAPI/ccGenerateToneInfo:

   Stop Tone On Digit=FALSE, Tone=Null,

   Tone Direction=Sum Network, Params=0x0, Call Id=176023

Feb 19 17:21:14.410: //176022/D25047000000/CCAPI/cc_api_call_disconnected:

   Cause Value=16, Interface=0x31340418, Call Id=176022

Feb 19 17:21:14.410: //176022/D25047000000/CCAPI/cc_api_call_disconnected:

   Call Entry(Responsed=TRUE, Cause Value=16, Retry Count=0)

Feb 19 17:21:14.410: //176022/D25047000000/CCAPI/ccConferenceDestroy:

   Conference Id=0xF2EA, Tag=0x0

Feb 19 17:21:14.410: //176022/D25047000000/CCAPI/cc_api_bridge_drop_done:

   Conference Id=0xF2EA, Source Interface=0x31340418, Source Call Id=176022,

   Destination Call Id=176023, Disposition=0x0, Tag=0x0

Feb 19 17:21:14.410: //176023/D25047000000/CCAPI/cc_api_bridge_drop_done:

   Conference Id=0xF2EA, Source Interface=0x31340418, Source Call Id=176023,

   Destination Call Id=176022, Disposition=0x0, Tag=0x0

Feb 19 17:21:14.410: //176022/D25047000000/CCAPI/cc_generic_bridge_done:

   Conference Id=0xF2EA, Source Interface=0x31340418, Source Call Id=176023,

   Destination Call Id=176022, Disposition=0x0, Tag=0x0

Feb 19 17:21:14.410: //176022/D25047000000/CCAPI/ccCallDisconnect:

   Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=16)

Feb 19 17:21:14.414: //176022/D25047000000/CCAPI/ccCallDisconnect:

   Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16)

Feb 19 17:21:14.414: //176023/D25047000000/CCAPI/ccCallDisconnect:

   Cause Value=16, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)

Feb 19 17:21:14.414: //176023/D25047000000/CCAPI/ccCallDisconnect:

   Cause Value=16, Call Entry(Responsed=TRUE, Cause Value=16)

Feb 19 17:21:14.414: //176022/D25047000000/CCAPI/cc_api_call_disconnect_done:

   Disposition=0, Interface=0x31340418, Tag=0x0, Call Id=176022,

   Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry Count=0)

Feb 19 17:21:14.414: //176022/D25047000000/CCAPI/cc_api_call_disconnect_done:

   Call Disconnect Event Sent

Feb 19 17:21:14.414: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Feb 19 17:21:14.414: :cc_free_feature_vsa freeing 31B40630

Feb 19 17:21:14.414: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Feb 19 17:21:14.414:  vsacount in free is 1

Feb 19 17:21:14.414: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.2.115.5:5060;branch=z9hG4bK4cce43ae98389

From: "Caller" <>;tag=659027~d01f1c4f-fe32-4ce8-bb98-06bd76f12320-33263464

To: <0038923248XXX>;tag=B8DD5C64-7FF

Date: Wed, 19 Feb 2014 16:21:14 gmt

Call-ID: d2504700-3041d9ef-47e32-573020a@10.2.115.5

Server: Cisco-SIPGateway/IOS-12.x

CSeq: 102 BYE

Reason: Q.850;cause=16

Content-Length: 0

Feb 19 17:21:14.414: //176023/D25047000000/SIP/Msg/ccsipDisplayMsg:

Sent:

BYE sip:+38923248XXX@172.25.255.164:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.126.98.37:5060;branch=z9hG4bK31F187D0

From: sip:+38923167XXX@10.2.115.5;tag=B8DD5C04-CE

To: <0038923248XXX>;tag=SDraqe898-2700717777

Date: Wed, 19 Feb 2014 16:21:03 gmt

Call-ID: A9472160-98B811E3-897DFE89-917343ED@10.126.98.37

User-Agent: Cisco-SIPGateway/IOS-12.x

Max-Forwards: 70

Timestamp: 1392826874

CSeq: 102 BYE

Reason: Q.850;cause=16

Content-Length: 0

Feb 19 17:21:14.426: //176023/D25047000000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.126.98.37:5060;branch=z9hG4bK31F187D0

From: sip:+38923167XXX@10.2.115.5;tag=B8DD5C04-CE

To: <0038923248XXX>;tag=SDraqe898-2700717777

Call-ID: A9472160-98B811E3-897DFE89-917343ED@10.126.98.37

Timestamp: 1392826874

CSeq: 102 BYE

Server: Patton SN4940 1E30V 00A0BA097588 R6.T 2013-04-04_RFE2204 H323 RBS SIP M5T SIP Stack/4.1.12.18

Content-Length: 0

Feb 19 17:21:14.426: //176023/D25047000000/CCAPI/cc_api_call_disconnect_done:

   Disposition=0, Interface=0x31340418, Tag=0x0, Call Id=176023,

   Call Entry(Disconnect Cause=16, Voice Class Cause Code=0, Retry Count=0)

Feb 19 17:21:14.426: //176023/D25047000000/CCAPI/cc_api_call_disconnect_done:

   Call Disconnect Event Sent

Feb 19 17:21:14.426: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Feb 19 17:21:14.426: :cc_free_feature_vsa freeing 31B40710

Feb 19 17:21:14.426: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

Feb 19 17:21:14.426:  vsacount in free is 0

Feb 19 17:21:14.426: //-1/xxxxxxxxxxxx/CCAPI/ccMemPoolTDFreeHelper:

   data = 2B00079C

Feb 19 17:21:14.426: ccMemPoolTDFreeHelper:mem_mgr_mempool_free: mem_refcnt(2AFD4B64)=0 - mempool

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.02.19 17:18:31 =~=~=~=~=~=~=~=~=~=~=~=

Debug output from "debug voip rtp session named-event"

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.02.19 17:29:25 =~=~=~=~=~=~=~=~=~=~=~=

Feb 19 17:31:52.030:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x79 timestamp 0x4BA0

Feb 19 17:31:52.030:  << Pt:101    Evt:2       Pkt:0A 00 00

Feb 19 17:31:52.030:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x79 timestamp 0x4BA0

Feb 19 17:31:52.030:          Pt:101    Evt:2       Pkt:0A 00 00  >>

Feb 19 17:31:52.042:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x7B timestamp 0x4BA0

Feb 19 17:31:52.042:  << Pt:101    Evt:2       Pkt:0A 00 A0

Feb 19 17:31:52.042:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x7B timestamp 0x4BA0

Feb 19 17:31:52.042:          Pt:101    Evt:2       Pkt:0A 00 A0  >>

Feb 19 17:31:52.050:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x7C timestamp 0x4BA0

Feb 19 17:31:52.050:  << Pt:101    Evt:2       Pkt:0A 01 40

Feb 19 17:31:52.050:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x7C timestamp 0x4BA0

Feb 19 17:31:52.050:          Pt:101    Evt:2       Pkt:0A 01 40  >>

Feb 19 17:31:52.062:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x7E timestamp 0x4BA0

Feb 19 17:31:52.062:  << Pt:101    Evt:2       Pkt:0A 01 E0

Feb 19 17:31:52.062:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x7E timestamp 0x4BA0

Feb 19 17:31:52.062:          Pt:101    Evt:2       Pkt:0A 01 E0  >>

Feb 19 17:31:52.070:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x7F timestamp 0x4BA0

Feb 19 17:31:52.070:  << Pt:101    Evt:2       Pkt:0A 02 80

Feb 19 17:31:52.070:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x7F timestamp 0x4BA0

Feb 19 17:31:52.070:          Pt:101    Evt:2       Pkt:0A 02 80  >>

Feb 19 17:31:52.082:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x81 timestamp 0x4BA0

Feb 19 17:31:52.082:  << Pt:101    Evt:2       Pkt:0A 03 20

Feb 19 17:31:52.082:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x81 timestamp 0x4BA0

Feb 19 17:31:52.082:          Pt:101    Evt:2       Pkt:0A 03 20  >>

Feb 19 17:31:52.090:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x82 timestamp 0x4BA0

Feb 19 17:31:52.090:  << Pt:101    Evt:2       Pkt:0A 03 C0

Feb 19 17:31:52.090:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x82 timestamp 0x4BA0

Feb 19 17:31:52.090:          Pt:101    Evt:2       Pkt:0A 03 C0  >>

Feb 19 17:31:52.102:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x84 timestamp 0x4BA0

Feb 19 17:31:52.102:  << Pt:101    Evt:2       Pkt:0A 04 60

Feb 19 17:31:52.102:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x84 timestamp 0x4BA0

Feb 19 17:31:52.102:          Pt:101    Evt:2       Pkt:0A 04 60  >>

Feb 19 17:31:52.110:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x85 timestamp 0x4BA0

Feb 19 17:31:52.110:  << Pt:101    Evt:2       Pkt:0A 05 00

Feb 19 17:31:52.110:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x85 timestamp 0x4BA0

Feb 19 17:31:52.110:          Pt:101    Evt:2       Pkt:0A 05 00  >>

Feb 19 17:31:52.122:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x87 timestamp 0x4BA0

Feb 19 17:31:52.122:  << Pt:101    Evt:2       Pkt:0A 05 A0

Feb 19 17:31:52.122:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x87 timestamp 0x4BA0

Feb 19 17:31:52.122:          Pt:101    Evt:2       Pkt:0A 05 A0  >>

Feb 19 17:31:52.130:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x88 timestamp 0x4BA0

Feb 19 17:31:52.130:  << Pt:101    Evt:2       Pkt:0A 06 40

Feb 19 17:31:52.130:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x88 timestamp 0x4BA0

Feb 19 17:31:52.130:          Pt:101    Evt:2       Pkt:0A 06 40  >>

Feb 19 17:31:52.142:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x8A timestamp 0x4BA0

Feb 19 17:31:52.142:  << Pt:101    Evt:2       Pkt:0A 06 E0

Feb 19 17:31:52.142:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x8A timestamp 0x4BA0

Feb 19 17:31:52.142:          Pt:101    Evt:2       Pkt:0A 06 E0  >>

Feb 19 17:31:52.150:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x8B timestamp 0x4BA0

Feb 19 17:31:52.150:  << Pt:101    Evt:2       Pkt:0A 07 80

Feb 19 17:31:52.150:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x8B timestamp 0x4BA0

Feb 19 17:31:52.150:          Pt:101    Evt:2       Pkt:0A 07 80  >>

Feb 19 17:31:52.162:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x8D timestamp 0x4BA0

Feb 19 17:31:52.162:  << Pt:101    Evt:2       Pkt:0A 08 20

Feb 19 17:31:52.162:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x8D timestamp 0x4BA0

Feb 19 17:31:52.162:          Pt:101    Evt:2       Pkt:0A 08 20  >>

Feb 19 17:31:52.170:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x8E timestamp 0x4BA0

Feb 19 17:31:52.170:  << Pt:101    Evt:2       Pkt:0A 08 C0

Feb 19 17:31:52.170:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x8E timestamp 0x4BA0

Feb 19 17:31:52.170:          Pt:101    Evt:2       Pkt:0A 08 C0  >>

Feb 19 17:31:52.182:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x90 timestamp 0x4BA0

Feb 19 17:31:52.182:  << Pt:101    Evt:2       Pkt:0A 09 60

Feb 19 17:31:52.182:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x90 timestamp 0x4BA0

Feb 19 17:31:52.182:          Pt:101    Evt:2       Pkt:0A 09 60  >>

Feb 19 17:31:52.190:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x91 timestamp 0x4BA0

Feb 19 17:31:52.190:  << Pt:101    Evt:2       Pkt:0A 0A 00

Feb 19 17:31:52.190:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x91 timestamp 0x4BA0

Feb 19 17:31:52.190:          Pt:101    Evt:2       Pkt:0A 0A 00  >>

Feb 19 17:31:52.202:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x93 timestamp 0x4BA0

Feb 19 17:31:52.202:  << Pt:101    Evt:2       Pkt:8A 0A A0

Feb 19 17:31:52.202:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x93 timestamp 0x4BA0

Feb 19 17:31:52.202:          Pt:101    Evt:2       Pkt:8A 0A A0  >>

Feb 19 17:31:52.202:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x94 timestamp 0x4BA0

Feb 19 17:31:52.202:  << Pt:101    Evt:2       Pkt:8A 0A A0

Feb 19 17:31:52.202:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x94 timestamp 0x4BA0

Feb 19 17:31:52.202:          Pt:101    Evt:2       Pkt:8A 0A A0  >>

Feb 19 17:31:52.218:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0x95 timestamp 0x4BA0

Feb 19 17:31:52.218:  << Pt:101    Evt:2       Pkt:8A 0A A0

Feb 19 17:31:52.218:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0x95 timestamp 0x4BA0

Feb 19 17:31:52.218:          Pt:101    Evt:2       Pkt:8A 0A A0  >>

Feb 19 17:31:52.542:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xA6 timestamp 0x5B40

Feb 19 17:31:52.542:  << Pt:101    Evt:3       Pkt:0A 00 00

Feb 19 17:31:52.542:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xA6 timestamp 0x5B40

Feb 19 17:31:52.542:          Pt:101    Evt:3       Pkt:0A 00 00  >>

Feb 19 17:31:52.550:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xA7 timestamp 0x5B40

Feb 19 17:31:52.550:  << Pt:101    Evt:3       Pkt:0A 00 A0

Feb 19 17:31:52.550:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xA7 timestamp 0x5B40

Feb 19 17:31:52.550:          Pt:101    Evt:3       Pkt:0A 00 A0  >>

Feb 19 17:31:52.562:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xA9 timestamp 0x5B40

Feb 19 17:31:52.562:  << Pt:101    Evt:3       Pkt:0A 01 40

Feb 19 17:31:52.562:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xA9 timestamp 0x5B40

Feb 19 17:31:52.562:          Pt:101    Evt:3       Pkt:0A 01 40  >>

Feb 19 17:31:52.570:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xAA timestamp 0x5B40

Feb 19 17:31:52.570:  << Pt:101    Evt:3       Pkt:0A 01 E0

Feb 19 17:31:52.570:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xAA timestamp 0x5B40

Feb 19 17:31:52.570:          Pt:101    Evt:3       Pkt:0A 01 E0  >>

Feb 19 17:31:52.582:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xAC timestamp 0x5B40

Feb 19 17:31:52.582:  << Pt:101    Evt:3       Pkt:0A 02 80

Feb 19 17:31:52.582:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xAC timestamp 0x5B40

Feb 19 17:31:52.582:          Pt:101    Evt:3       Pkt:0A 02 80  >>

Feb 19 17:31:52.590:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xAD timestamp 0x5B40

Feb 19 17:31:52.590:  << Pt:101    Evt:3       Pkt:0A 03 20

Feb 19 17:31:52.590:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xAD timestamp 0x5B40

Feb 19 17:31:52.590:          Pt:101    Evt:3       Pkt:0A 03 20  >>

Feb 19 17:31:52.602:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xAF timestamp 0x5B40

Feb 19 17:31:52.602:  << Pt:101    Evt:3       Pkt:0A 03 C0

Feb 19 17:31:52.602:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xAF timestamp 0x5B40

Feb 19 17:31:52.602:          Pt:101    Evt:3       Pkt:0A 03 C0  >>

Feb 19 17:31:52.610:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xB0 timestamp 0x5B40

Feb 19 17:31:52.610:  << Pt:101    Evt:3       Pkt:0A 04 60

Feb 19 17:31:52.610:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xB0 timestamp 0x5B40

Feb 19 17:31:52.610:          Pt:101    Evt:3       Pkt:0A 04 60  >>

Feb 19 17:31:52.622:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xB2 timestamp 0x5B40

Feb 19 17:31:52.622:  << Pt:101    Evt:3       Pkt:0A 05 00

Feb 19 17:31:52.622:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xB2 timestamp 0x5B40

Feb 19 17:31:52.622:          Pt:101    Evt:3       Pkt:0A 05 00  >>

Feb 19 17:31:52.630:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xB3 timestamp 0x5B40

Feb 19 17:31:52.630:  << Pt:101    Evt:3       Pkt:0A 05 A0

Feb 19 17:31:52.630:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xB3 timestamp 0x5B40

Feb 19 17:31:52.630:          Pt:101    Evt:3       Pkt:0A 05 A0  >>

Feb 19 17:31:52.642:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xB5 timestamp 0x5B40

Feb 19 17:31:52.642:  << Pt:101    Evt:3       Pkt:0A 06 40

Feb 19 17:31:52.642:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xB5 timestamp 0x5B40

Feb 19 17:31:52.642:          Pt:101    Evt:3       Pkt:0A 06 40  >>

Feb 19 17:31:52.650:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xB6 timestamp 0x5B40

Feb 19 17:31:52.650:  << Pt:101    Evt:3       Pkt:0A 06 E0

Feb 19 17:31:52.650:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xB6 timestamp 0x5B40

Feb 19 17:31:52.650:          Pt:101    Evt:3       Pkt:0A 06 E0  >>

Feb 19 17:31:52.662:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xB8 timestamp 0x5B40

Feb 19 17:31:52.662:  << Pt:101    Evt:3       Pkt:8A 07 80

Feb 19 17:31:52.662:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xB8 timestamp 0x5B40

Feb 19 17:31:52.662:          Pt:101    Evt:3       Pkt:8A 07 80  >>

Feb 19 17:31:52.662:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xB9 timestamp 0x5B40

Feb 19 17:31:52.662:  << Pt:101    Evt:3       Pkt:8A 07 80

Feb 19 17:31:52.662:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xB9 timestamp 0x5B40

Feb 19 17:31:52.662:          Pt:101    Evt:3       Pkt:8A 07 80  >>

Feb 19 17:31:52.678:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xBA timestamp 0x5B40

Feb 19 17:31:52.678:  << Pt:101    Evt:3       Pkt:8A 07 80

Feb 19 17:31:52.678:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xBA timestamp 0x5B40

Feb 19 17:31:52.678:          Pt:101    Evt:3       Pkt:8A 07 80  >>

Feb 19 17:31:52.970:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xC9 timestamp 0x67C0

Feb 19 17:31:52.970:  << Pt:101    Evt:5       Pkt:0A 00 00

Feb 19 17:31:52.970:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xC9 timestamp 0x67C0

Feb 19 17:31:52.970:          Pt:101    Evt:5       Pkt:0A 00 00  >>

Feb 19 17:31:52.982:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xCA timestamp 0x67C0

Feb 19 17:31:52.982:  << Pt:101    Evt:5       Pkt:0A 00 A0

Feb 19 17:31:52.982:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xCA timestamp 0x67C0

Feb 19 17:31:52.982:          Pt:101    Evt:5       Pkt:0A 00 A0  >>

Feb 19 17:31:52.990:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xCC timestamp 0x67C0

Feb 19 17:31:52.990:  << Pt:101    Evt:5       Pkt:0A 01 40

Feb 19 17:31:52.990:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xCC timestamp 0x67C0

Feb 19 17:31:52.990:          Pt:101    Evt:5       Pkt:0A 01 40  >>

Feb 19 17:31:53.002:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xCD timestamp 0x67C0

Feb 19 17:31:53.002:  << Pt:101    Evt:5       Pkt:0A 01 E0

Feb 19 17:31:53.002:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xCD timestamp 0x67C0

Feb 19 17:31:53.002:          Pt:101    Evt:5       Pkt:0A 01 E0  >>

Feb 19 17:31:53.010:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xCF timestamp 0x67C0

Feb 19 17:31:53.010:  << Pt:101    Evt:5       Pkt:0A 02 80

Feb 19 17:31:53.010:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xCF timestamp 0x67C0

Feb 19 17:31:53.010:          Pt:101    Evt:5       Pkt:0A 02 80  >>

Feb 19 17:31:53.022:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xD0 timestamp 0x67C0

Feb 19 17:31:53.022:  << Pt:101    Evt:5       Pkt:0A 03 20

Feb 19 17:31:53.022:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xD0 timestamp 0x67C0

Feb 19 17:31:53.022:          Pt:101    Evt:5       Pkt:0A 03 20  >>

Feb 19 17:31:53.030:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xD2 timestamp 0x67C0

Feb 19 17:31:53.030:  << Pt:101    Evt:5       Pkt:0A 03 C0

Feb 19 17:31:53.030:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xD2 timestamp 0x67C0

Feb 19 17:31:53.030:          Pt:101    Evt:5       Pkt:0A 03 C0  >>

Feb 19 17:31:53.042:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xD3 timestamp 0x67C0

Feb 19 17:31:53.042:  << Pt:101    Evt:5       Pkt:0A 04 60

Feb 19 17:31:53.042:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xD3 timestamp 0x67C0

Feb 19 17:31:53.042:          Pt:101    Evt:5       Pkt:0A 04 60  >>

Feb 19 17:31:53.050:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xD5 timestamp 0x67C0

Feb 19 17:31:53.050:  << Pt:101    Evt:5       Pkt:0A 05 00

Feb 19 17:31:53.050:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xD5 timestamp 0x67C0

Feb 19 17:31:53.050:          Pt:101    Evt:5       Pkt:0A 05 00  >>

Feb 19 17:31:53.062:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xD6 timestamp 0x67C0

Feb 19 17:31:53.062:  << Pt:101    Evt:5       Pkt:0A 05 A0

Feb 19 17:31:53.062:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xD6 timestamp 0x67C0

Feb 19 17:31:53.062:          Pt:101    Evt:5       Pkt:0A 05 A0  >>

Feb 19 17:31:53.070:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xD8 timestamp 0x67C0

Feb 19 17:31:53.070:  << Pt:101    Evt:5       Pkt:0A 06 40

Feb 19 17:31:53.070:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xD8 timestamp 0x67C0

Feb 19 17:31:53.070:          Pt:101    Evt:5       Pkt:0A 06 40  >>

Feb 19 17:31:53.082:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xD9 timestamp 0x67C0

Feb 19 17:31:53.082:  << Pt:101    Evt:5       Pkt:0A 06 E0

Feb 19 17:31:53.082:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xD9 timestamp 0x67C0

Feb 19 17:31:53.082:          Pt:101    Evt:5       Pkt:0A 06 E0  >>

Feb 19 17:31:53.090:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xDB timestamp 0x67C0

Feb 19 17:31:53.090:  << Pt:101    Evt:5       Pkt:0A 07 80

Feb 19 17:31:53.090:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xDB timestamp 0x67C0

Feb 19 17:31:53.090:          Pt:101    Evt:5       Pkt:0A 07 80  >>

Feb 19 17:31:53.102:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xDC timestamp 0x67C0

Feb 19 17:31:53.102:  << Pt:101    Evt:5       Pkt:8A 08 20

Feb 19 17:31:53.102:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xDC timestamp 0x67C0

Feb 19 17:31:53.102:          Pt:101    Evt:5       Pkt:8A 08 20  >>

Feb 19 17:31:53.102:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xDD timestamp 0x67C0

Feb 19 17:31:53.102:  << Pt:101    Evt:5       Pkt:8A 08 20

Feb 19 17:31:53.102:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xDD timestamp 0x67C0

Feb 19 17:31:53.102:          Pt:101    Evt:5       Pkt:8A 08 20  >>

Feb 19 17:31:53.118:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xDE timestamp 0x67C0

Feb 19 17:31:53.118:  << Pt:101    Evt:5       Pkt:8A 08 20

Feb 19 17:31:53.118:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xDE timestamp 0x67C0

Feb 19 17:31:53.118:          Pt:101    Evt:5       Pkt:8A 08 20  >>

Feb 19 17:31:53.270:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xE7 timestamp 0x7080

Feb 19 17:31:53.270:  << Pt:101    Evt:2       Pkt:0A 00 00

Feb 19 17:31:53.270:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xE7 timestamp 0x7080

Feb 19 17:31:53.270:          Pt:101    Evt:2       Pkt:0A 00 00  >>

Feb 19 17:31:53.282:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xE8 timestamp 0x7080

Feb 19 17:31:53.282:  << Pt:101    Evt:2       Pkt:0A 00 A0

Feb 19 17:31:53.282:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xE8 timestamp 0x7080

Feb 19 17:31:53.282:          Pt:101    Evt:2       Pkt:0A 00 A0  >>

Feb 19 17:31:53.290:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xEA timestamp 0x7080

Feb 19 17:31:53.290:  << Pt:101    Evt:2       Pkt:0A 01 40

Feb 19 17:31:53.290:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xEA timestamp 0x7080

Feb 19 17:31:53.290:          Pt:101    Evt:2       Pkt:0A 01 40  >>

Feb 19 17:31:53.302:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xEB timestamp 0x7080

Feb 19 17:31:53.302:  << Pt:101    Evt:2       Pkt:0A 01 E0

Feb 19 17:31:53.302:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xEB timestamp 0x7080

Feb 19 17:31:53.302:          Pt:101    Evt:2       Pkt:0A 01 E0  >>

Feb 19 17:31:53.310:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xED timestamp 0x7080

Feb 19 17:31:53.310:  << Pt:101    Evt:2       Pkt:0A 02 80

Feb 19 17:31:53.310:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xED timestamp 0x7080

Feb 19 17:31:53.310:          Pt:101    Evt:2       Pkt:0A 02 80  >>

Feb 19 17:31:53.322:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xEE timestamp 0x7080

Feb 19 17:31:53.322:  << Pt:101    Evt:2       Pkt:0A 03 20

Feb 19 17:31:53.322:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xEE timestamp 0x7080

Feb 19 17:31:53.322:          Pt:101    Evt:2       Pkt:0A 03 20  >>

Feb 19 17:31:53.330:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xF0 timestamp 0x7080

Feb 19 17:31:53.330:  << Pt:101    Evt:2       Pkt:0A 03 C0

Feb 19 17:31:53.330:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xF0 timestamp 0x7080

Feb 19 17:31:53.330:          Pt:101    Evt:2       Pkt:0A 03 C0  >>

Feb 19 17:31:53.342:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xF1 timestamp 0x7080

Feb 19 17:31:53.342:  << Pt:101    Evt:2       Pkt:0A 04 60

Feb 19 17:31:53.342:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xF1 timestamp 0x7080

Feb 19 17:31:53.342:          Pt:101    Evt:2       Pkt:0A 04 60  >>

Feb 19 17:31:53.350:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xF3 timestamp 0x7080

Feb 19 17:31:53.350:  << Pt:101    Evt:2       Pkt:0A 05 00

Feb 19 17:31:53.350:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xF3 timestamp 0x7080

Feb 19 17:31:53.350:          Pt:101    Evt:2       Pkt:0A 05 00  >>

Feb 19 17:31:53.362:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xF4 timestamp 0x7080

Feb 19 17:31:53.362:  << Pt:101    Evt:2       Pkt:0A 05 A0

Feb 19 17:31:53.362:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xF4 timestamp 0x7080

Feb 19 17:31:53.362:          Pt:101    Evt:2       Pkt:0A 05 A0  >>

Feb 19 17:31:53.370:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xF6 timestamp 0x7080

Feb 19 17:31:53.370:  << Pt:101    Evt:2       Pkt:0A 06 40

Feb 19 17:31:53.370:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xF6 timestamp 0x7080

Feb 19 17:31:53.370:          Pt:101    Evt:2       Pkt:0A 06 40  >>

Feb 19 17:31:53.382:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xF7 timestamp 0x7080

Feb 19 17:31:53.382:  << Pt:101    Evt:2       Pkt:0A 06 E0

Feb 19 17:31:53.382:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xF7 timestamp 0x7080

Feb 19 17:31:53.382:          Pt:101    Evt:2       Pkt:0A 06 E0  >>

Feb 19 17:31:53.390:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xF9 timestamp 0x7080

Feb 19 17:31:53.390:  << Pt:101    Evt:2       Pkt:0A 07 80

Feb 19 17:31:53.390:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xF9 timestamp 0x7080

Feb 19 17:31:53.390:          Pt:101    Evt:2       Pkt:0A 07 80  >>

Feb 19 17:31:53.402:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xFA timestamp 0x7080

Feb 19 17:31:53.402:  << Pt:101    Evt:2       Pkt:0A 08 20

Feb 19 17:31:53.402:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xFA timestamp 0x7080

Feb 19 17:31:53.402:          Pt:101    Evt:2       Pkt:0A 08 20  >>

Feb 19 17:31:53.410:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xFC timestamp 0x7080

Feb 19 17:31:53.410:  << Pt:101    Evt:2       Pkt:0A 08 C0

Feb 19 17:31:53.410:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xFC timestamp 0x7080

Feb 19 17:31:53.410:          Pt:101    Evt:2       Pkt:0A 08 C0  >>

Feb 19 17:31:53.422:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xFD timestamp 0x7080

Feb 19 17:31:53.422:  << Pt:101    Evt:2       Pkt:8A 09 60

Feb 19 17:31:53.422:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xFD timestamp 0x7080

Feb 19 17:31:53.422:          Pt:101    Evt:2       Pkt:8A 09 60  >>

Feb 19 17:31:53.422:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xFE timestamp 0x7080

Feb 19 17:31:53.422:  << Pt:101    Evt:2       Pkt:8A 09 60

Feb 19 17:31:53.422:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xFE timestamp 0x7080

Feb 19 17:31:53.422:          Pt:101    Evt:2       Pkt:8A 09 60  >>

Feb 19 17:31:53.438:          s=VoIP d=DSP payload 0x65 ssrc 0x58F0F00A sequence 0xFF timestamp 0x7080

Feb 19 17:31:53.438:  << Pt:101    Evt:2       Pkt:8A 09 60

Feb 19 17:31:53.438:          s=DSP d=VoIP payload 0x65 ssrc 0x58F0F00A sequence 0xFF timestamp 0x7080

Feb 19 17:31:53.438:          Pt:101    Evt:2       Pkt:8A 09 60  >>

VIP Super Bronze

what debug for seeing DTMF tones via CUBE -SIP?

This trace shows that the DTMF negotiation is using rtp-nte. Pt=101 and you can see the dtmf events in the RTP stream using payload 101.

On your sip messaging as well you can see that your provider

This is advertised on your CUBE

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

This is advertised by the ITSP

a=rtpmap:101 telephone-event/8000

a=fmtp:18 annexb=no

a=fmtp:101 0-15

This clearly shows that they both negotiate rtp-nte...So I am at a loss as to why you say it doesnt work when you configure rtp-nte, because this is what is negotiated

Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

what debug for seeing DTMF tones via CUBE -SIP?

Nevertheless, thank You!

24207
Views
25
Helpful
26
Replies
CreatePlease login to create content