Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
3987
Views
5
Helpful
7
Replies

Having issues with DTMF tones via CUBE-SIP

dianareyes
Level 1
Level 1

‎05-23-2016 04:54 PM - edited ‎03-17-2019 07:00 AM

Good afternoon,

We are currently setting up a parking lot Gate Unit w/ a number pad which customer's press a "Call Press" button, speaks with an agent, agent presses 6 on her phone and the arm lift is triggered - granting the customer access to the parking property. The call press button is tied to a VG (VG310 -analog line), in CUCM the DN forwards the call to an external number (goes out through CUBE).  Not sure what other information may be needed....

The problem is when the agent presses #6 on her phone nothing happens - a short dial tone is received and the arm lift is not triggered.

I ran the following debugs - ccip messages, VOIP RTP ALL Named Events, and voip ccapi inout, however not exactly sure what i'm looking for. i do see the following;

Stream type : voice+dtmf
Media line : 1
State : STREAM_ADDING (2)
Stream address type : 1
Callid : 1090790
Negotiated Codec : g711ulaw, bytes :160
Nego. Codec payload : 0 (tx), 0 (rx)
Negotiated DTMF relay : rtp-nte
Negotiated NTE payload : 101 (tx), 101 (rx)
Negotiated CN payload : 0
Media Srce Addr/Port : [xx.xxx.xxx.x]:0
Media Dest Addr/Port : [xx.xxx.xxx.x]:19058

043717: May 20 18:40:17.473 EST: //1090790/33AA4C000000/SIP/Info/notify/33/sipSPIHandleInviteMedia:
Negotiated Codec : g711ulaw, bytes :160
Preferred Codec : g711ulaw, bytes :160
Preferred DTMF relay 1 : 6
Preferred DTMF relay 2 : 0
Negotiated DTMF relay : 6

Any assistance or suggestions will be greatly appreciated!

Thank you,

Diana

Labels:
0 Helpful
7 Replies 7

Murali_DS
Level 1
Level 1

‎05-23-2016 10:50 PM

Hi Diana,

U mean to say when DTMF 6 is pressed by the Agent it triggers an arm lift to grant access to the parking lot is it ???

Can u provide the Dial-peer config and also did u see any capture of dtmf press from the ccapi logs...?

 what is the DTMF relay config in the Dial-peer ??? 

 dtmf-relay sip-notify  or rtp-nte??

Thx,

M

0 Helpful

dianareyes
Level 1
Level 1
In response to Murali_DS

‎05-24-2016 10:43 PM

Hi M,

Correct, when DTMF 6 is pressed by the Agent the arm lift to supposed to lift up to grant access, however that is not occurring.

We believe the issues lays with DTMF and CUBE. We have reached out to our SIP provider and they confirmed they are not changing anything in regards to the DTMF relaying. 

dtmf-relay rtp-nte is configured under the Dial-peers, however dtmf-relay rtp-nte sip-kpml is configured on one of the dial-peers.

As requested below are the dial-peers.

dial-peer voice 10 pots
destination-pattern 911$
port 0/1/0
forward-digits all


dial-peer voice 20 pots
destination-pattern 911$
port 0/1/1
forward-digits all


dial-peer voice 102 voip
description PSTN calls intl number
huntstop
destination-pattern 011.T
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 103 voip
description Inbound Catch-All
session protocol sipv2
incoming called-number .T
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 204 voip
description Inbound Calls to Extension
destination-pattern XXXXX....
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 100 voip
description PSTN local number
huntstop
destination-pattern ..........
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 101 voip
description PSTN natl number
huntstop
destination-pattern 1..........
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 30 pots
destination-pattern XXXXXXXXXX
port 0/1/1
forward-digits all


dial-peer voice 210 voip
description Inbound Calls to Extension
destination-pattern xxxxxxx..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 211 voip
description Inbound Calls to Extension
preference 1
destination-pattern XXX3XXX..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 220 voip
description Inbound Calls to Extension
destination-pattern XXXXXXXX..
session protocol sipv2
session target ipv4:XX.xxx.xxx.x
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 221 voip
description Inbound Calls to Extension
preference 1
destination-pattern XXXXXXX..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 230 voip
description Inbound Calls to Extension
destination-pattern XXXXXXXX..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 231 voip
description Inbound Calls to Extension
preference 1
destination-pattern XXXXXXXX..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 240 voip
description Inbound Calls to Extension
destination-pattern XXXXXXXX..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 241 voip
description Inbound Calls to Extension
preference 1
destination-pattern XXXXXXXX..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 250 voip
description Inbound Calls to Extension
destination-pattern XXXXXXXX..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 251 voip
description Inbound Calls to Extension
preference 1
destination-pattern XXXXXXXX..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 260 voip
description Inbound Calls to Extension
destination-pattern XXXXXXXX..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 261 voip
description Inbound Calls to Extension
preference 1
destination-pattern XXXXXXXX..
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 300 pots
description ACCESS
destination-pattern XX....
clid network-number XXXX
port 0/2/0:23
forward-digits 5


dial-peer voice 350 voip
destination-pattern XXXXXXXXXX
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte sip-kpml
codec g711ulaw


dial-peer voice 270 voip
description Contracts FAX
destination-pattern XXXXXXXXXX
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 271 voip
description Contracts FAX
preference 1
destination-pattern XXXXXXXXXX
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
dtmf-relay rtp-nte
codec g711ulaw


dial-peer voice 205 voip
description Inbound Calls to Unity
preference 1
destination-pattern XXXXXXXXXX
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
codec g711ulaw


dial-peer voice 206 voip
description Inbound Calls to Unity
destination-pattern XXXXXXXXXX
session protocol sipv2
session target ipv4:XX.XXX.XXX.X
codec g711ulaw

Voice Service Voip configuration

sip

  min-se 180 session-expires 180

  header-passing

  early-offer forced

  midcall-signaling passthru

  sip-profiles 101

 

0 Helpful

Murali_DS
Level 1
Level 1
In response to dianareyes

‎05-30-2016 12:26 AM

Hi Diana,

sry for the late reply, since you are using SIP dial-peers you can add SIP-Notify to process the sip messages.

I assume this is the DP tag u are using to signal the other end  :dial-peer voice 350 voip, you can include sip-notify/sip-kmpl and chk this out, from my experience I haven't came across this scenario so we could try it out.

dial-peer voice 350 voip

dtmf-relay rtp-nte sip-notify

or dtmf-relay rtp-nte sip-info

The below link would give you more idea abt this 

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/dtmf-relay.html

Regards,

M

0 Helpful

dianareyes
Level 1
Level 1
In response to Murali_DS

‎06-01-2016 01:51 PM

Hi All,

Thank you for your suggestions and feedback!

Unfortunately, none of the DTMF relays methods worked and I ended up opening up a Cisco TAC case.  

It was confirmed we were hitting a Cisco ISR4 defect in which DTMF doesn't work properly when MTP is CoLocated with ASR/ISR4K.  We changed MTP and used CallManager instead, once changed DTMF started working properly.

In case you're interested or helps anyone else coming across this issue - Cisco Bug #CSCtw50974 - ASR/ISR4K DTMF 2833 to 2833 Not Working with MTP CoLocated and OOB+2833.

Best Regards,

D

Deepak Mehta
VIP Alumni
VIP Alumni
In response to dianareyes

‎06-01-2016 01:59 PM

Great info, thank you for sharing this.

0 Helpful

Deepak Mehta
VIP Alumni
VIP Alumni

‎05-24-2016 10:33 AM

Thanks .

It looks RTP NTE with PT 101 is your preference however it is not clear what service provider is negotiating .

Also early offer is forced on CUBE so the called party decides the negotiation of what DTMF and codec has to be used.

Can you send full debug ccsip messages for a non working call.thanks

0 Helpful

dianareyes
Level 1
Level 1
In response to Deepak Mehta

‎05-24-2016 10:50 PM

Hi Deepak,

As requested attached is a debug ccsip messges on a non working calls.  I believe there was 2-non working calls in the debug output.

Let me know your thoughts!

Thank you,

D

Preview file
520 KB
0 Helpful
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:

Customers Also Viewed These Support Documents