[cisco-voip] no DTMF to a specific number

[Eric Pedersen]

CUCM 8.6 <- SIP-> GW(IOS 15.1)  <- PRI -> PSTN

I'm having a strange DTMF relay problem with a specific destination: when we call this number, their IVR answers but DTMF doesn't work.  I ran an ISDN debug, and I see that their IVR audio starts after we receive an ISDN PROGRESS message without ever receiving an ISDN CONNECT message. At this point the gateway has only sent a SIP 183 Session Progress message to CUCM, not a SIP 200.  I have the gateway configured to use KPML for DTMF relay, but the gateway doesn't subscribe to kpml until after sending SIP 200.

I set up a specific incoming dial-peer for this number with dtmf-relay sip-notify and that works fine, but I'd rather not do a one-off configuration for this, and kpml seems to work fine with every other call.

Has anyone seen anything like this? It seems to me like this is a configuration problem on their end, but it works calling from my cell phone.

FYI, this is what the ISDN message sequence looks like for the problematic call:
715102: Oct 23 13:34:51.065 MDT: ISDN Se0/0/1:23 Q931: Sending SETUP  callref = 0x5559 callID = 0xD360 switch = primary-dms100 interface = User
715103: Oct 23 13:34:51.065 MDT: ISDN Se0/0/1:23 Q931: TX -> SETUP pd = 8  callref = 0x5559
715104: Oct 23 13:34:51.193 MDT: ISDN Se0/0/1:23 Q931: RX <- CALL_PROC pd = 8  callref = 0xD559
715105: Oct 23 13:34:52.541 MDT: ISDN Se0/0/1:23 Q931: RX <- PROGRESS pd = 8  callref = 0xD559
<-- IVR STARTS -->
715133: Oct 23 13:35:26.633 MDT: ISDN Se0/0/1:23 Q931: TX -> DISCONNECT pd = 8  callref = 0x5559
715134: Oct 23 13:35:26.693 MDT: ISDN Se0/0/1:23 Q931: RX <- RELEASE pd = 8  callref = 0xD559
715135: Oct 23 13:35:26.693 MDT: ISDN Se0/0/1:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x5559

A call to a working IVR looks like:
714989: Oct 23 13:33:07.677 MDT: ISDN Se0/0/1:23 Q931: Sending SETUP  callref = 0x554F callID = 0xD356 switch = primary-dms100 interface = User
714990: Oct 23 13:33:07.677 MDT: ISDN Se0/0/1:23 Q931: TX -> SETUP pd = 8  callref = 0x554F
714991: Oct 23 13:33:07.793 MDT: ISDN Se0/0/1:23 Q931: RX <- CALL_PROC pd = 8  callref = 0xD54F
714995: Oct 23 13:33:10.341 MDT: ISDN Se0/0/1:23 Q931: RX <- ALERTING pd = 8  callref = 0xD54F
714996: Oct 23 13:33:10.541 MDT: ISDN Se0/0/1:23 Q931: RX <- CONNECT pd = 8  callref = 0xD54F
714998: Oct 23 13:33:10.541 MDT: ISDN Se0/0/1:23 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x554F
<-- IVR STARTS -->
715007: Oct 23 13:33:15.629 MDT: ISDN Se0/0/1:23 Q931: TX -> DISCONNECT pd = 8  callref = 0x554F
715008: Oct 23 13:33:15.689 MDT: ISDN Se0/0/1:23 Q931: RX <- RELEASE pd = 8  callref = 0xD54F
715009: Oct 23 13:33:15.693 MDT: ISDN Se0/0/1:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x554F

Regards,
Eric

The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121023/86a2f103/attachment.html>