I have a problem breaking DTMF tone on a T1 CAS link from a carrier that has carrier side Authentication Codes in place. What this does is generate a tone after the trunk is sized and the user inputs his 5 digit code and once accepted it allows the call out. This is used for billing at the customer request. I have the below listed details.
Any assistance is appreciated.
CallManager - CM 3.2(2c)SPH and Engineering Special 46
Gateway - 3745 (MGCP) with IOS version Version 12.2(15)T
controller T1 1/1
cablelength short 133
ds0-group 1 timeslots 1-24 type e&m-wink-start
mgcp call-agent 172.20.128.10 2427 service-type mgcp version 0.1
If you have to /prepend/ the billing code to the phone number, there are a couple of solutions.
You might try a route pattern "9." with strip-predot out that channelized T1. I'm pretty sure this will result in you just seizing a trunk on that T1 and sending no digits. The audio path will be cut through to the user and they should hear dialtone, and then they enter their PIN, and then dial normally - but the digits will be collected by the PSTN switch directly instead of by CallManager. I have not actually tried this, but I think it should work with MGCP. The disadvantage is that CallManager will have no idea what you called, so you will have no meaningful CDR records, and you will be almost entirely reliant on your carrier's reporting.
If the PIN is of a consistent length (say, always 5 digits) and you don't need to pause between PIN entry and dialing the number, you can use a route pattern like "9.XXXXX@", which will collect 5 digits for the PIN and then allow you to dial anything in the NANP normally. This is just like the usual "9.@", but with a PIN. I'm not sure if you can introduce a pause when outpulsing that on the channelized T1, so you may or may not be in trouble if you have to pause between the PIN and dialing.
I really can't envision how the channelized T1 can interactively prompt you for a PIN while using E&M wink start, so I may not be correctly understanding how your carrier has this set up.
If you have to post-dial the billing code after dialing the number (which is the way I've seen it work in other environments), you shouldn't really have to do anything out of the ordinary. The call goes out normally so far as CallManager knows, the user will hear the prompt for their PIN and dial it in, and the call will proceed.
CSCdx52074 CCM Does Not Forward Access Codes To MGCP Gateway
CSCdx52074 is fixed in ES46. So you should not be seeing this one. However, to verify you can run mgcp debugs to see if the digits are received from the Call Manger.
CSCea19218 MGCP gateway does not playout DTMF during EM_WAIT_FOR_ANSWER state.
CSCea19218 is probably the culprit. Not fixed in 122-15.T. It is resolved in 122-13.T3 but this code has CSCeb10204 which is not yet resolved.
FWIW, these issues are all MGCP/T1 CAS related and do not happen with H.323.
The issue with CSCea19218 is that when the users are prompted with the Tone to enter the access code, the state of the call is not Connected but rather EM_WAIT_FOR_ANSWER and the gateway does not outpulse the DTMF tones while in this state.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...