cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1944
Views
0
Helpful
8
Replies

DTMF Outbound Issues on UC520 and XO SIP since upgrade to 15.0.1.XA

johnconrick
Level 1
Level 1

We were on 12.24YB and had this issue sporadically, and on 12.20T and never had this occur but what is happening is when you call WebEx for example and have to enter your meeting number, the tones (although you hear them locally) do not carry over and the remote system does not respond.  We just upgraded to 15.0.1XA on Sunday and this issue is now repeatable on all outbound DTMF - inbound works fine.  Attached is a copy of current running config and debug logs.  There were other calls in the system while I was running debug - my test was from Ext 760 (Extra Desk) to 4721724 (also a cisco uc520 system) and trying to dial 2003 (direct extension) and it was not registering the tones.

8 Replies 8

johnconrick
Level 1
Level 1

we have 2 polycom soundstation 2w phones in user mode and DTMF tones are working on them.  All our other phones are 7975 and DTMF is not working there.

johnconrick
Level 1
Level 1

Question in case the powers that be lose patience with this outbound DTMF issue:

if i change:

boot system flash uc500-advipservicesk9-mz.150-1.XA

to

boot system flash uc500-advipservicesk9-mz.124-20.T2.bin

after uploading the T2 fimware to flash and reset the UC520 that will rollback to T2 firmware right?  Will the newer versions of CUE, CME etc still work with the T2 firmware?



johnconrick
Level 1
Level 1

Here is the invite (our UC520) and ringing (XO) from the Debug , it does look like the remote end is a Sonus gateway:

INVITE



sip:4721724@207.155.153.33:5060

SIP/2.0

Via: SIP/2.0/UDP 65.44.247.10:5060;branch=z9hG4bK24BB199C

Remote-Party-ID: "Extra Desk" <



sip:6153454700@65.44.247.10

>;party=calling;screen=no;privacy=off

From: "Extra Desk" <



sip:6153454700@207.155.153.33

>;tag=A7D905C-1984

To: <



sip:4721724@207.155.153.33

>

Date: Mon, 11 Jan 2010 16:15:11 GMT

Call-ID: 53F07687-FE0311DE-85ED91C9-B9005EF3@65.44.247.10

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

Min-SE:  1800

Cisco-Guid: 1388947808-4261614046-2246611401-3103809267

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

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

CSeq: 101 INVITE

Max-Forwards: 70

Timestamp: 1263226511

Contact: <



sip:6153454700@65.44.247.10:5060

>

Expires: 180

Allow-Events: telephone-event

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 246

v=0

o=CiscoSystemsSIP-GW-UserAgent 7027 876 IN IP4 65.44.247.10

s=SIP Call

c=IN IP4 65.44.247.10

t=0 0

m=audio 18888 RTP/AVP 0 101

c=IN IP4 65.44.247.10

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

000901: Jan 11 16:15:11.483: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 65.44.247.10:5060;branch=z9hG4bK24BB199C

From: "Extra Desk" <



sip:6153454700@207.155.153.33

>;tag=A7D905C-1984

To: <



sip:4721724@207.155.153.33

>;tag=gK02b57704

Call-ID: 53F07687-FE0311DE-85ED91C9-B9005EF3@65.44.247.10

CSeq: 101 INVITE

Content-Length: 0

 

000902: Jan 11 16:15:12.547: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 65.44.247.10:5060;branch=z9hG4bK24BB199C

From: "Extra Desk" <



sip:6153454700@207.155.153.33

>;tag=A7D905C-1984

To: <



sip:4721724@207.155.153.33

>;tag=gK02b57704

Call-ID: 53F07687-FE0311DE-85ED91C9-B9005EF3@65.44.247.10

CSeq: 101 INVITE

Contact: <



sip:4721724@207.155.153.33:5060

>

A lot of us are experiencing the same issues with this software release using SIP providers who have Sonus gateways.

There is a popular thread here:

https://www.myciscocommunity.com/thread/4945

And the Cisco Bug ID here:

http://ww.cisco.com/cgi-bin/Support/Bugtool/home.pl

CSCtd68173

Cisco says they are working on a fix for this issue, so we are hopeful there will be a fix soon.

Checking on this now.

Yes, we have seen this bug and are working on a fix.  It will be included in the 8.0.1 software pack.  This bug wasn't as straight forward as most from a coding side.  There will be an announcement here for when it is fixed.

I know it's hard to speculate on the release timeframe, but do you think we will see 8.0.1 released at some point this quarter?

Yes, we are just days away from releasing this version.


Marcos

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: