CCM 4.1(3) - DialPlan 7-digit dialing Configuration

Hi. Currently I have a CallManager cluster providing services on different cities. Now we are moving a new office to the IPT cluster and the city dials 7-digit local calls dialing within the location and 10-digit local calls and 11-digit LD, etc..
What is the best approach for adding the 7-digit and 10-digit routes.. currently I'm not using the @ anywhere in the CallManager and I don't want to use it. Also adding unique route-patterns for all the 7-digit dialing is not the best approach as there are lots of routes.. Gateway is using MGCP.
Thanks in advanced,
-Jose

Instead of using 9.[2-9]XX[2-9]XXXXXX use the area code as your 2nd through 5th digits. For example:
9.[2-9]XXXXXX - for 7 digit local
9.212[2-9]XXXXXX - 10 digit local
9.315[3-9]XXXXXX - 10 digit local
9.1[2-9]XX[2-9]XXXXXX - Long distance
replacing the 212 and the 315 examples with area codes that are local to your area.

Similar Messages

Pap2t for 7 digit dialing

Hi there,
how can I configure my pap2t to handle 7 digit dialing so it can make local calls without having to enter 1-NPA?
Cheers

This page appears to have some handy examples for implementing a North American dialplan
http://www.cisco.com/en/US/products/ps10033/products_qanda_item09186a0080a35a44.shtml

7 digit dialing on FXO lines for UC320W

Located in the Jacksonville, FL USA area, cannot seem to create a dial plan for 7 digit dialing. Area code is (904) and I don't see an option where to change from 10 digit to 7 digit outbound dialing.
Am I missing something?

Hi lance-ten,
Please go to Region page, change the dial plan from 10-digit to 7-digit and provide the default area code which is 904 for your case. Then you need to apply the configuration to make it effect.
Regards,
Wendy

Random 'Duplicate Digit Dialing' on SPA-2102

I have a Linksys VOIPAdapter SPA-2102 which worked fine for two years but started ‘duplicate digitdialing' from mid-October this year. While it is still working perfectly for callsto and from any US/Canada number, now it always dials "double digits"randomly AFTER getting connected to an international access number(403-260-3325) and then dialing 011 to connect overseas . For example, aftergetting connected if I dial 92-51-2256684 it instead dials 922512256684or 925512256684 or 992512256684 etc. Thus the problem startsafter dialing 13 digits, while the same settings worked fine earlier for twoyears.
I have talked extensively both to my VOIP phone service provider and theInternational Dialing service provider, but both have failed to solve theproblem. The problem is not faced if I use a softphone from my computer,confirming the problem to be in the VOIP Adapter settings. I changed my phonebut that has not solved the problem. I reset the VOIP Adapter to defaultfactory settings by dialing the 73738# code from the handset and then feedingin the settings provided by my service provider (Adminlogin-Advanced-Voice-Line 1) but problem was not solved. Tried the same with877778# code but problem stayed. Downloaded the firmware from Linksys(Cisco)website and upgraded to version 5.2.10 from 3.3.5(a) but problem still there.
Can someone help, as I amunable to dial overseas since last six weeks!

If you tried the different combinations of DTMF Transmit Method and Codec settings you tried the obvious fixes.
To persue further changes, I would download the latest firmware for the SPA2102, install it and re-enter your configuration. If you are currently running the latest firmware, I would reset the firmware to factory specifications with the IVR and re-enter your configuration. You can download the latest firmware here:
http://www.cisco.com/cisco/web/solutions/small_business/products/firmware.html
When you send dtmf digits using the rfc2833 protocol, for each digit the protocol sends a start digit packet, then multiple packets for the digit depending on how long you hold down the key, then an end packet. If the packets get out of sequence or lost that's when the receiving end can get an error in decoding the digit. The packets are sent along with the voice stream packet (rtp packets). If you made the call with XLite using the same voip provider to call the pstn number and experienced no problems whereas you consistently experienced problems with the SPA2102 then it would seem that the firmware in the SPA2102 has some difference with the XLite computer code. As I said, by default it appears to me the XLite is using rfc2833 as a dtmf transmission method and G711u as the codec.
Several of the Betamax companies have competitive promotional rates to Pakistan. VoipBuster is 3.0c/min, Rynga is 3.0c/min, Jumblo is 3.0c, 12voip is 3.5c/min, budgetsip is 3.3c/min, and actionvoip is 4.0c/min. These are euro cent prices. You could try one of these companies with your 2d line on the SPA2102. The disadvantage here, though, is it costs 10 euros to get started which is close to $16 Canadian, they can change the rates without warning, and they offer zero customer support.
You could also try a different voip provider to call the pstn number as a test to see if that made any difference. You can get a pay-as-you-go account with CallCentric for a $5 (US) deposit. With CallCentric, calls to a Canadian PSTN number are 0.0198 (US) per minute.

Route 10 digit dialed numbers to 4 digit VoIP extensions

If a branch office phone dials a 10 digit TN of a VoIP phone, instead of simply dialing the internal extension, is there any way to route that call over the WAN instead of sending the call off to the PSTN? We have 30+ locations for which we'd like to apply this concept to.
We are using a mixture of PSTN's and SIP trunks, MGCP gateways, and CUCM 7.1
Thanks,

Absolutely although the answer will differ depending on the intracies of your particular dial plan design. Here are two common approaches:
(Adapt) Create translation patterns for your DID ranges within the same partition that the off-net route patterns exist. The more-specific translation pattern will be matched, preventing the call from going off-net. In your example as you've described it:
Route Pattern: [2-9]XX[2-9]XXXXXX or 9.[2-9]XX[2-9]XXXXXX
Translation Pattern:
FROM: 608[2-9]XX.XXXX or 9.608[2-9]XX.XXXX (Take note of the period and the fact that the pattern is more explicit than your route pattern!)
TO: Digit Discard: PreDot; Use a CSS that has the internal DNs.
(Start Over) This, along with a long list of other dial plan shortcomings has been designed in the E.164-based dial plan introduced with CUCM 7.0; however, this essentially requires you to start over. There is no easy way to convert from the legacy model. The E.164 "act local, think global" mentality would inherently catch this.
Full disclosure: I am a big proponent of the E.164-based design and am unlikely to be entirely impartial here.

Hot Dial configuration on 7821

How to configure hot dial on 7821? i have created partition as hot-dial-pt and css as hot-dial-css. and created blank translation pattern.
Please let me know the process to configure hot dial on 7821 phone.

With a SIP phone, you need to do a SIP pattern. Refer to the following previous forum
https://supportforums.cisco.com/discussion/11136061/hot-dial-cisco-9951-sip-phone

Who changed Address Book SMS and Dial configuration settings ??

Address Book suddenly stopped allowing me to SMS from my K610i mobile phone... Furtunately someone posted a fix where you can add the phone id string to the AddressBook application settings.
Anyone know if there was there a recent update from Apple that changed some of the AddressBook application settings to disable this feature ?

With Bluetooth on, if you look at Address Book's window you should see a bluetooth icon on the top bar, to the right of the drop-down menu icon that looks like a wee gear wheel. This bluetooth icon needs to be blue for SMS messaging. If it is grey, click it and see if anything interesting happens.
AK

SPA3000 F/W 3.1.20(GW) last digit repetition within the dial plan is not working for gateway 0-4

H/W: SPA3000
F/W: 3.1.20(GW)
Problem: The last digit repetition within the dial plan is not working for gateway 0-4.
Line 1 Dial Plan: (****|<#,xx.<:@gw1>|1747xxxxxxxx.<:@gw1>)
Dial "17474743246#" which works for gw1.
Dial "#17474743246" which also works for gw1.
Dial "17474743246" which doesn't work and actually goes through VoIP 1 but not gw1.
It results in I have to specify a fixed number of digits for gw0-gw4 in the dial plan or it won't works. This could be very difficult for international calls.
Is there any way to specify Interdigit Short Timer with <:@gw0>?
BTW, it's strange that I have to include (****) in the dial plan to enter IVR. Without it I can't even hear any sound coming from gw1 (SIPphone). Maybe the SPA needs a factory reset. The test dial plan might look like,
S:4,(****|*xxx.|[2-9]|xxxxx|*0<:@gw1>|1747xxxxxxx<:@gw1>|1408xxxxxxx<:@gw0>|xxxxxxxxxxxxxxxxxxxx.!)
The last barring sequence "xxxxxxxxxxxxxxxxxxxx!" is to make sure the Interdigit Short Timer works after the last digit dialed otherwise the number will be transmitted immediately which is not preferred.

IMHO , if there's a need for you to include *** on the dial plan to enter the IVR menu there might be a need to reset the unit.
I believe that you can set the interdigit timer by including that on the dial plan ie: xxxxS0 just like on a hotline, i just never had a chance to try including that syntax when invoking gw0 on the dial plan , but i guess you may give it a try.

CUCM Dialled Number Analyser for Digit by Digit Analysis?

Hi,
I'm wondering if anyone can help.
I work in a diagnostic team that often has to solve issues with problems on dial plans and customers not being able to call particular numbers. We often use Dialled Number Analyser to help us with this, but this only helps when the number is dialled en bloc. Often, a customer will say they try to dial a number and it will stop at a specific point, indicating there's an overlapping pattern somewhere. This can be very difficult to find. We use route plan report to help us but often the offending pattern will have wild cards in it and therefore merely searching for the number or the first few digits of the number will not help.
Is there another Cisco tool that will show the matches that Call Manager is making as each digit is dialled? Dialled number analyser does NOT help with this. It can be very time consuming trying to locate a route pattern otherwise (because there may be several partitions to look through and various patterns with wildcards in them).
Many thanks,
Neil

You should be able to pull the CCM SDI traces and see the digit analysis which will show you the pattern matched. You will need to know the calling DN and time of the call to find this.
Here's an example that I pulled from a CUCM 8.5(1) system. Older versions may be more/less information and the formatting may change slightly. The DialingPartition and DialingPattern lines are the actual route pattern matched in the database. Note that I replaced the real calling DID with 16085550100 here for privacy reasons.
16:28:14.410 |Digit analysis: analysis results|5,100,50,1.934924^10.245.58.160^SEP00270DBD4BA916:28:14.410 ||PretransformCallingPartyNumber=+16085550100|CallingPartyNumber=+16085550100|DialingPartition=Sec1_Route_PT|DialingPattern=\+1XXXXXXXXXX|FullyQualifiedCalledPartyNumber=+18005532447|DialingPatternRegularExpression=(+1[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9])|DialingWhere=|PatternType=Enterprise|PotentialMatches=NoPotentialMatchesExist|DialingSdlProcessId=(0,0,0)|PretransformDigitString=+18005532447|PretransformTagsList=SUBSCRIBER|PretransformPositionalMatchList=+18005532447|CollectedDigits=+18005532447|UnconsumedDigits=|TagsList=SUBSCRIBER|PositionalMatchList=+18005532447|VoiceMailbox=|VoiceMailCallingSearchSpace=|VoiceMailPilotNumber=|RouteBlockFlag=RouteThisPattern|RouteBlockCause=0|AlertingName=|UnicodeDisplayName=|DisplayNameLocale=1|OverlapSendingFlagEnabled=0|WithTags=|WithValues=|CallingPartyNumberPi=NotSelected|ConnectedPartyNumberPi=NotSelected|CallingPartyNamePi=NotSelected|ConnectedPartyNamePi=NotSelected|CallManagerDeviceType=NoDeviceType|PatternPrecedenceLevel=Routine|CallableEndPointName=[67bee3e6-a58e-13dc-88c8-731e76915835]|PatternNodeId=[ffe93d92-a48a-5b00-c450-2b0a9097b6e2]|AARNeighborhood=[]|AARDestinationMask=[]|AARKeepCallHistory=true|AARVoiceMailEnabled=false|NetworkLocation=OffNet|Calling Party Number Type=Cisco Unified CallManager|Calling Party Numbering Plan=Cisco Unified CallManager|Called Party Number Type=Cisco Unified CallManager|Called Party Numbering Plan=Cisco Unified CallManager|ProvideOutsideDialtone=true|AllowDeviceOverride=false|AlternateMatches= Information Not Available|TranslationPatternDetails= Information Not Available|ResourcePriorityNamespace=|PatternRouteClass=RouteClassDefault|5,100,50,1.934924^10.245.58.160^SEP00270DBD4BA9

Issue on urgent priority short dialing intra cluster

Hello All,
I have an issue with short daling within the cluster, It seems CUCM takes 6 seconds to make the second phone ring even when a TP with urgent priority is hit. As fas as my observation appropriate translation pattern hit and it actions as soon as the user presses the digits, but cucm takes time in searching the called number and it finds the number only after 6 seconds and the phone rings. There is no issues with enblock dialling.
Configuration: CUCM 8.5.1
ANI : 3573257
DNIS : 3573258
* Cisco 7942 (3573257 in partition2 dialls 3 2 5 8) --> 3XXX TP with urgent priority, prefix 357 in partiotion1 --> Cisco 7942 (3573258 in partition2 phone rings after 6 seconds)
* Both the phone are under the same subscriber.
* If I do enblock dialling I dont see any issues.
Changes happened:
The issue happened after the site has been undegone some phones, partiotion, CSS and gateway changes with regard to implementing logical partitioning.
Kindly help me on this issue, earlier called phone rings as soon as the user do 4 digit short dial but now it has 6 seconds delay. I can post if you need the CCM traces here.

I checked your traces.
in Enbloc dialing there is no potential match exist during digit analysis.
21:59:35.734 |StationInit: (0146365) EnblocCall calledParty=3257.|8,100,50,1.933363045^19.237.142.74^SEP001E13E61F14
21:59:35.735 |Digit analysis: match(pi="2", fqcn="66553077", cn="3573077",plv="5", pss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", TodFilteredPss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", dd="3257",dac="0")|8,100,50,1.933363045^19.237.142.74^SEP001E13E61F14
21:59:35.735 |Digit analysis: analysis results|8,100,50,1.933363045^19.237.142.74^SEP001E13E61F14
21:59:35.735 ||PretransformCallingPartyNumber=3077
|CallingPartyNumber=3077
|DialingPartition=SG2-ICR-PhoneDN-PT
|DialingPattern=3573257
|FullyQualifiedCalledPartyNumber=66553257
|DialingPatternRegularExpression=(3573257)
|DialingWhere=
|PatternType=Enterprise
|PotentialMatches=NoPotentialMatchesExist
but for the digit by digit dialing, it says, potential matches exist.
21:59:50.906 |Digit analysis: match(pi="2", fqcn="66553077", cn="3573077",plv="5", pss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", TodFilteredPss="SG2-ICR-BSpecial-PT:SG2-ICR-Emergency-PT:SG2-ICR-DNTrans-PT:SG2-ICR-PSTN-FAC-PT:SG2-ICR-CMService-PT:SG2-TCM-InTrans-PT:SG2-TCM-PT:SG2-VM-PT", dd="3257",dac="0")|8,100,50,1.933364937^19.237.142.74^SEP001E13E61F14
21:59:50.906 |Digit analysis: analysis results|8,100,50,1.933364937^19.237.142.74^SEP001E13E61F14
21:59:50.906 ||PretransformCallingPartyNumber=3077
|CallingPartyNumber=3077
|DialingPartition=SG2-ICR-PhoneDN-PT
|DialingPattern=3573257
|FullyQualifiedCalledPartyNumber=66553257
|DialingPatternRegularExpression=(3573257)
|DialingWhere=
|PatternType=Enterprise
|PotentialMatches=PotentialMatchesExist
|DialingSdlProcessId=(0,0,0)
|PretransformDigitString=3573257
|PretransformTagsList=SUBSCRIBER
|PretransformPositionalMatchList=3573257
|CollectedDigits=3573257
|UnconsumedDigits=
not sure why this difference is? could you please crosscheck the routeplan report once again please?

755p Voice Dial with BlueTooth

I've searched all over the place for help with my quest to make my Treo 755p "Smart" phone have bluetooth voice dial capabilities. What seems to be out-of-the-box functionality for many normal phones (no "smart" in their name) is apparently difficult to achieve with the Treo 755p, and apparently with all Treos from what I've seen so far. Here's the conclusion that I'm coming to, but I just can't believe it, so I'm posting this here in the hopes the experts (that's you guys) will either correct my misunderstanding, or (hopefully not) confirm that I'm on the right track.
APPARENTLY:
Voice dial capability is not part of the Treo 755p; one has to install a 3rd party program or service to gain this functionality. There are a few good options out there, but they do cost additional money.
Voice dial programs apparently work pretty good with the wired headsets that come with the Treo package. Apparently (although I have not tested it yet) pressing the button on the side of the treo or one the wired headset can be configured to activate the voice dial software, and the user can speak into the wired headset microphone to dial by voice.
Extra digit dialing is apparently not supported by most (if any) of the software I've seen that works on the Palm platform. (This is hard to tell exactly, because some software works only for the windows platform, which I don't have.)
Bluetooth headsets configured in hands-free mode will launch the voice-dial software, but I've found that the treo does not connect the voice dial software to the bluetooth headset, so instructions are not heard through the headset and the headset microphone is ignored for voice dialing. Others have apparently had the same issue, from what I've seen posted in this forum and on other fora as well.
The only method I've heard of anyone successfully using a bluetooth headset for voice dialing with a Treo is to bypass the Treo Bluetooth Handsfree mode, purchase an extra bluetooth adapter meant to add bluetooth capabilities to non-bluetooth phones, and then pair the headset with that adapter. This adapter typically costs $10-20, but is sort of big and must clip to your phone or to your belt. This adapter plugs itself into the treo's headset jack and simulates a wired headset. Apparently this mode works well, for yet more cost and additional bulk with makes it difficult to fit the phone into standard casings and/or take the phone out to work with the PDS without unplugging it.
One such adapter is the Cardo "Node" (http://www.cardowireless.com/node/434), but you can't buy it from their website anymore so I'm looking for other options.
I've heard that Jabra also has one, but I'm not sure of the model number, price, or form-factor.
Am I on track with this? This just doesn't sound right to me. I've seen postings that users have had this issue from the earliest Treo models, so I would have thought that Palm would have addressed it by now. I've always thought of Palm as a reputable and responsive company, so I'm hoping I've missed the "silver bullet" solution. Can someone point me in the right direction?
Many thanks.
Bob Smiley
Post relates to: Treo 755p (Sprint)

I hope Palm is listening.
It was good to see others as frustrated as I am about the Treo’s glaring deficiency – kind of a support group. I kept thinking I must be wrong because I traded up from a dumb phone and couldn’t believe my new palm is incapable of Bluetooth voice dialing.
The voice dialing companies all say it’s a problem with the Treos. I have asked the people at Palm and, though they are very nice, they haven't been able to help. The people I spoke with didn’t seem to understand what I wanted and then spent a great deal of time trying to find the answer. In the end, they confirmed: you can get Bluetooth with a Treo, and you can get voice dialing with a Treo, but you can't get voice dialing over Bluetooth. They didn't know if a solution was in the works.
I am really puzzled about this problem. How hard can this be? As Bob Smiley said, you can get a Bluetooth adapter to simulate a wired headset, and any one of us could superglue it to the Treo, but why?
It seems to me that this is such a basic function that, especially with all the upgrades, they should be able to fix it easily. My impression is that no one at Palm is working on this and that no one is scheduled to work on this, but I hope I’m wrong.
Post relates to: Treo 755p (Verizon)
Post relates to: Treo 755p (Verizon)

Dial-Peer matches but fails to call out

Hello,
Am trying to get my CME configured for Callcentric. I have both an inbound and an outbound plan.
With my dial-peers configured for standard 11-digit and 10-digit dialing, calls go to fast busy after all digits except the last two are dialed. Debug shows a dial-peer match initially, then states no match and the call fails. If I change the destination pattern to match my cell phone number exactly, I can dial all the digits but the call still fails. Anyone have a suggestion?
Here are my dial peers:
dial-peer voice 700 voip
description SIP Trunk - Incoming
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target dns:callcentric.com
incoming called-number .%
dial-peer voice 701 voip
description SIP Trunk - Outgoing 3-Digit Calls
translation-profile outgoing SIP_1
preference 1
destination-pattern 9[2-8]11
voice-class codec 1
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target sip-server
dtmf-relay rtp-nte
dial-peer voice 702 voip
description SIP Trunk - Outgoing 11-Digit Calls
translation-profile outgoing SIP_1
preference 1
destination-pattern 91[2-9].......
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target sip-server
dtmf-relay rtp-nte
dial-peer voice 703 voip
description SIP Trunk - Outgoing 10-Digit Calls
translation-profile outgoing SIP_1
preference 1
destination-pattern 9[2-9].......
voice-class codec 1
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target sip-server
no vad
And here is the debug associated with a call:
*Dec 26 22:26:27.854: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=7018, Called Number=, Voice-Interface=0x4A4AE7B0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:27.854: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20009
GMIT-VOICEROUTER01#
*Dec 26 22:26:29.526: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:29.526: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9
*Dec 26 22:26:29.526: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
*Dec 26 22:26:29.526: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
*Dec 26 22:26:29.914: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=91, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:29.914: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=91
*Dec 26 22:26:29.914: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
*Dec 26 22:26:29.914: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
*Dec 26 22:26:30.174: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Numbe
GMIT-VOICEROUTr=, Called Number=912, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:30.174: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=912
*Dec 26 22:26:30.174: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
*Dec 26 22:26:30.174: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
*Dec 26 22:26:30.514: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9120, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:30.514: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9120
*Dec 26 22:26:30.514: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
*Dec 26 22:26:30.514: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
*Dec 26 22:26:30.822: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=91207, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:30.822: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=91207
*Dec 26 22:26:30.826: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
*Dec 26 22:26:30.826: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
*Dec 26 22:26:31.342: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=912072, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:31.342: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=912072
*Dec 26 22:26:31.346: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
*Dec 26 22:26:31.346: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
*Dec 26 22:26:31.542: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9120722, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:31.546: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9120722
*Dec 26 22:26:31.546: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
*Dec 26 22:26:31.546: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
*Dec 26 22:26:31.934: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=91207227, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:31.934: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=91207227
*Dec 26 22:26:31.934: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
*Dec 26 22:26:31.934: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
*Dec 26 22:26:32.602: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=912072277, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:32.602: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=912072277
*Dec 26 22:26:32.602: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Partial Matches(1) after DP_MATCH_DEST
*Dec 26 22:26:32.606: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=MORE_DIGITS_NEEDED(1)
*Dec 26 22:26:33.382: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9120722776, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:33.382: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9120722776
*Dec 26 22:26:33.382: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Dec 26 22:26:33.386: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=702
*Dec 26 22:26:33.386: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9120722776, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:33.386: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9120722776
*Dec 26 22:26:33.386: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Dec 26 22:26:33.386: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=702
*Dec 26 22:26:33.386: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9120722776, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:33.386: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9120722776
*Dec 26 22:26:33.386: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Dec 26 22:26:33.386: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=702
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=9120722776, Called Number=9120722776, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9120722776
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=702
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules Attempt
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=9120722776, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=702
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9120722776, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9120722776
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Dec 26 22:26:33.390: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=702
*Dec 26 22:26:33.394: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=9120722776, Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:33.394: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=9120722776
*Dec 26 22:26:33.394: //-1/98A189FD81D3/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Dec 26 22:26:33.394: //-1/98A189FD81D3/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=702
*Dec 26 22:26:33.574: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=91[2-9]......., Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:33.578: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules Attempt
*Dec 26 22:26:36.374: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=7018$, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Dec 26 22:26:36.378: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules AttemptER01#

Translation profile:
voice translation-rule 3
rule 1 /^7../ /2072267262/
voice translation-rule 4
rule 1 /^9$1....$/ /\1/
rule 2 /^9207$...$/ /\1/
rule 3 /^9$011.*$/ /\1/
rule 4 /^9$[2-9]11$/ /\1/
voice translation-profile SIP_1
translate calling 3
translate called 4
Here is debug ccsip messages:
*Dec 27 14:10:16.598: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:[email protected]:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 207.5.178.214:5060;branch=z9hG4bKd77b793048igqgkfd0g1.1
Allow-Events: message-summary, refer, dialog, line-seize, presence, call-info, as-feature-event
Max-Forwards: 69
Call-ID: SDp6vve01-196593d11e4bf68c71f8a4085d7de7d0-c54gcb0
From: ;tag=SDp6vve01-callagent.gwi.net+1+8bfe3a+d3cf6d84
CSeq: 938331054 OPTIONS
Organization: MetaSwitch
Supported: resource-priority, 100rel
Content-Length: 0
Contact:
To:
*Dec 27 14:10:16.606: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 207.5.178.214:5060;branch=z9hG4bKd77b793048igqgkfd0g1.1
From: ;tag=SDp6vve01-callagent.gwi.net+1+8bfe3a+d3cf6d84
To:
GMIT-VOICEROUT166>;tag=F1B5120-18BD
Date: Fri, 27 Dec 2013 14:10:16 GMT
Call-ID: SDp6vve01-196593d11e4bf68c71f8a4085d7de7d0-c54gcb0
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 938331054 OPTIONS
Supported: 100rel,resource-priority,replaces,sdp-anat
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Content-Type: application/sdp
Content-Length: 172
v=0
o=CiscoSystemsSIP-GW-UserAgent 4484 7548 IN IP4 66.55.220.166
s=SIP Call
c=IN IP4 66.55.220.166
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3
c=IN IP4 66.55.220.166
ER01#
GMIT-VOICEROUTER01#
*Dec 27 14:10:34.834: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5080 SIP/2.0
Via: SIP/2.0/UDP 66.55.220.166:5060;branch=z9hG4bK5795232C
From: "Server Room" [email protected]>;tag=F1B9854-8A5
To: [email protected]>
Date: Fri, 27 Dec 2013 14:10:34 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2066961728-1849102819-2185007278-567139419
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, B
GMIT-VOICEROUTER01#YE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1388153434
Contact:
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 297
v=0
o=CiscoSystemsSIP-GW-UserAgent 3022 9963 IN IP4 66.55.220.166
s=SIP Call
c=IN IP4 66.55.220.166
t=0 0
m=audio 19258 RTP/AVP 18 101 19
c=IN IP4 66.55.220.166
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=rtpmap:19 CN/8000
a=ptime:20
*Dec 27 14:10:34.906: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 407 Proxy Authentication Required
v: SIP/2.0/UDP 66.55.220.166:5060;branch=z9hG4bK5795232C
f: "Server Room" [email protected]>;tag=F1B9854-8A5
t: [email protected]>
i: [email protected]
CSeq: 1
GMIT-VOICEROUT01 INVITE
Proxy-Authenticate: Digest realm="callcentric.com", domain="sip:callcentric.com", nonce="3755ae79fd668c2035ebb90cdc12d030", opaque="", stale=TRUE, algorithm=MD5
l: 0
*Dec 27 14:10:34.914: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:[email protected]:5080 SIP/2.0
Via: SIP/2.0/UDP 66.55.220.166:5060;branch=z9hG4bK5795232C
From: "Server Room" [email protected]>;tag=F1B9854-8A5
To: [email protected]>
Date: Fri, 27 Dec 2013 14:10:34 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0
*Dec 27 14:10:34.914: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:[email protected]:5080 SIP/2.0
Via: SIP/2.0/UDP 66.55.220.166:5060;branch=z9hG4bK579619F9
From: "Server Room" [email protected]>;tag=F1B9854-8A5
To: [email protected]>
Date: Fri, 27 Dec 2013 14:10:34 GMT
Call-ID: [email protected]
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2066961728-1849102819-2185007278-567139419
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Max-Forwards: 70
Timestamp: 1388153434
Contact:
Expires: 180
Allow-Events: telephone-event
Proxy-Authorization: Digest username="17772882353",realm="callcentric.com",uri="sip:[email protected]:5080",response="cbac03a76a23b6a35ebbee966c00a577",nonce="3755ae79fd668c2035ebb90cdc12d030",opaque="",algorithm=MD5
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 297
v=0
o=CiscoSystemsSIP-GW-UserAgent 3022 9963 IN IP4 66.55.220.166
s=SIP Call
c=IN IP4 66.55.220.166
t=0 0
m=audio 19258 RTP/AVP 18 101 19
c=IN IP4 66.55.220.166
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=rtpmap:19 CN/8000
a=ptime:20
*Dec 27 14:10:34.990: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 403 Incorrect Authentication
v: SIP/2.0/UDP 66.55.220.166:5060;branch=z9hG4bK579619F9
f: "Server Room" [email protected]>;tag=F1B9854-8A5
t: [email protected]>
i: [email protected]
CSeq: 102 INVITE
l: 0
*Dec 27 14:10:35.002: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:[email protected]:5080 SIP/2.0
Via: SIP/2.0/UDP 66.55.220.166:5060;branch=z9hG4bK579619F9
From: "Server Room" [email protected]>;tag=F1B9854-8A5
To: [email protected]>
Date: Fri, 27 Dec 2013 14:10:34 GMT
Call-ID: [email protected]
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: telephone-event
Content-Length: 0
Here is debug voip ccapi inout:
GMIT-VOICEROUTER01#debug voip ccapi inout
voip ccapi inout debugging is on
GMIT-VOICEROUTER01#
*Dec 27 14:10:55.326: //-1/8912F77B8243/CCAPI/cc_api_display_ie_subfields:
   cc_api_call_setup_ind_common:
   cisco-username=
   ----- ccCallInfo IE subfields -----
   cisco-ani=7018
   cisco-anitype=0
   cisco-aniplan=0
   cisco-anipi=0
   cisco-anisi=0
   dest=
   cisco-desttype=0
   cisco-destplan=0
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-lastrdn=
   cisco-rdntype=0
   cisco-rdnplan=0
   cisco-rdnpi=0
   cisco-rdnsi=0
   cisco-redirectreason=0   fwd_final_type =0
   final_redirectNumber =
   hunt_group_timeout =0
*Dec 27 14:10:55.326: //-1/8912F77B8243/CCAPI/cc_api_call_setup_ind_common:
   Interface=0x4A4AE7B0, Call Info(
   Calling Number=7018,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=(TON=Unknown, NPI=Unknown),
   Calling Translated=FALSE, Subscriber Type Str=RegularLine, FinalDestinationFlag=FALSE,
   Incoming Dial-peer=20009, Progress Indication=ORIGINATING SIDE IS NON ISDN(3)
GMIT-VOICEROUT, Calling IE Present=TRUE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=-1
*Dec 27 14:10:55.326: //-1/8912F77B8243/CCAPI/ccCheckClipClir:
   In: Calling Number=7018(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
*Dec 27 14:10:55.326: //-1/8912F77B8243/CCAPI/ccCheckClipClir:
   Out: Calling Number=7018(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
*Dec 27 14:10:55.326: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
*Dec 27 14:10:55.326: :cc_get_feature_vsa malloc success
*Dec 27 14:10:55.326: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
*Dec 27 14:10:55.326: cc_get_feature_vsa count is 1
*Dec 27 14:10:55.326: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
*Dec 27 14:10:55.326: :FEATURE_VSA attributes are: feature_name:0,feature_time:1282234808,feature_id:151
*Dec 27 14:10:55.330: //12898/8912F77B8243/CCAPI/cc_api_call_setup_ind_common:
   Set Up Event Sent;
   Call Info(Calling Number=7018(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=(TON=Unknown, NPI=Unknown))
*Dec 27 14:10:55.330: //12898/8912F77B8243/CCAPI/cc_process_call_setup_ind:
   Event=0x49A103B8
*Dec 27 14:10:55.330: //12898/8912F77B8243/CCAPI/ccCallSetContext:
   Context=0x4C5A319C
*Dec 27 14:10:55.334: //12898/8912F77B8243/CCAPI/cc_process_call_setup_ind:
   >>>>CCAPI handed cid 12898 with tag 20009 to app "_ManagedAppProcess_Default"
*Dec 27 14:10:55.334: //12898/8912F77B8243/CCAPI/ccCallSetupAck:
   Call Id=12898
*Dec 27 14:10:55.334: //12898/8912F77B8243/CCAPI/cc_api_set_transfer_info:
   Transfer Number=, Transfer Reason=0x0
*Dec 27 14:10:55.334: //12898/8912F77B8243/CCAPI/ccGenerateToneInfo:
   Stop Tone On Digit=TRUE, Tone=Dial Tone,
   Tone Direction=Network, Params=0x0, Call Id=12898
*Dec 27 14:10:55.334: //12898/8912F77B8243/CCAPI/ccSetDigitTimeouts:
   Initial Digit Timeout=-1000(ms), Inter Digit Timeout=-1000(ms)
*Dec 27 14:10:55.338: //12898/8912F77B8243/CCAPI/ccSetDigitTimeouts:
   Call Entry(Inter Digit Timeout=10000(ms), Initial Digit Timeout=10000(ms))
*Dec 27 14:10:55.338: //12898/xxxxxxxxxxxx/CCAPI/ccCallReportDigits:
   (callID=0x3262, digit_event=0x1, enable=TRUE, consume=FALSE)
*Dec 27 14:10:55.338: //12898/8912F77B8243/CCAPI/ccCallReportDigits:
   Enabled=TRUE, Call Id=12898
*Dec 27 14:10:55.338: //12898/xxxxxxxxxxxx/CCAPI/cc_api_call_report_digits_done:
   (vdbPtr=0x4A4AE7B0, callID=0x3262, disp=0, digit_event=0x1, enable=TRUE, consume=FALSE)
*Dec 27 14:10:55.338: //12898/8912F77B8243/CCAPI/cc_api_call_report_digits_done:
   Enabled=TRUE, Disposition=0x0, Interface=0x4A4AE7B0, Call Id=12898
*Dec 27 14:10:55.338: //12898/8912F77B8243/CCAPI/cc_api_call_report_digits_done:
   Call Entry(Initial Digit Timeout=15000(ms), Inter Digit Timeout=10000(ms))
*Dec 27 14:10:56.650: //12898/8912F77B8243/CCAPI/cc_api_call_digit_begin:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=9, DigitBeginFlags=0x0,
   Rtp Timestamp=0x9D41D0, Rtp Expiration=0x0
*Dec 27 14:10:56.654: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=9, Duration=100,
   Xrule Calling Tag=0, Xrule Called Tag=0, Digit Tone Mode=DTMF
*Dec 27 14:10:56.654: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Call Entry(Handoff Depth=0)
*Dec 27 14:10:56.970: //12898/8912F77B8243/CCAPI/cc_api_call_digit_begin:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=1, DigitBeginFlags=0x0,
   Rtp Timestamp=0x9DBED0, Rtp Expiration=0x0
*Dec 27 14:10:56.974: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=1, Duration=100,
   Xrule Calling Tag=0, Xrule Called Tag=0, Digit Tone Mode=DTMF
*Dec 27 14:10:56.974: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Call Entry(Handoff Depth=0)
*Dec 27 14:10:57.290: //12898/8912F77B8243/CCAPI/cc_api_call_digit_begin:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=2, DigitBeginFlags=0x0,
   Rtp Timestamp=0x9E3BD0, Rtp Expiration=0x0
*Dec 27 14:10:57.294: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=2, Duration=100,
   Xrule Calling Tag=0, Xrule Called Tag=0, Digit Tone Mode=DTMF
*Dec 27 14:10:57.294: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Call Entry(Handoff Depth=0)
*Dec 27 14:10:57.610: //12898/8912F77B8243/CCAPI/cc_api_call_digit_begin:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=0, DigitBeginFlags=0x0,
   Rtp Timestamp=0x9EB8D0, Rtp Expiration=0x0
*Dec 27 14:10:57.614: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=0, Duration=100,
   Xrule Calling Tag=0, Xrule Called Tag=0, Digit Tone Mode=DTMF
*Dec 27 14:10:57.614: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Call Entry(Handoff Depth=0)
*Dec 27 14:10:57.890: //12898/8912F77B8243/CCAPI/cc_api_call_digit_begin:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=7, DigitBeginFlags=0x0,
   Rtp Timestamp=0x9F35D0, Rtp Expiration=0x0
*Dec 27 14:10:57.894: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=7, Duration=100,
   Xrule Calling Tag=0, Xrule Called Tag=0, Digit Tone Mode=DTMF
*Dec 27 14:10:57.894: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Call Entry(Handoff Depth=0)
*Dec 27 14:10:58.162: //12898/8912F77B8243/CCAPI/cc_api_call_digit_begin:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=2, DigitBeginFlags=0x0,
   Rtp Timestamp=0x9FB2D0, Rtp Expiration=0x0
*Dec 27 14:10:58.162: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=2, Duration=100,
   Xrule Calling Tag=0, Xrule Called Tag=0, Digit Tone Mode=DTMF
*Dec 27 14:10:58.162: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Call Entry(Handoff Depth=0)
*Dec 27 14:10:58.314: //12898/8912F77B8243/CCAPI/cc_api_call_digit_begin:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=2, DigitBeginFlags=0x0,
   Rtp Timestamp=0xA02FD0, Rtp Expiration=0x0
*Dec 27 14:10:58.314: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=2, Duration=100,
   Xrule Calling Tag=0, Xrule Called Tag=0, Digit Tone Mode=DTMF
*Dec 27 14:10:58.314: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Call Entry(Handoff Depth=0)
*Dec 27 14:10:58.582: //12898/8912F77B8243/CCAPI/cc_api_call_digit_begin:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=7, DigitBeginFlags=0x0,
   Rtp Timestamp=0xA0ACD0, Rtp Expiration=0x0
*Dec 27 14:10:58.582: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=7, Duration=100,
   Xrule Calling Tag=0, Xrule Called Tag=0, Digit Tone Mode=DTMF
*Dec 27 14:10:58.582: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Call Entry(Handoff Depth=0)
*Dec 27 14:10:58.754: //12898/8912F77B8243/CCAPI/cc_api_call_digit_begin:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=7, DigitBeginFlags=0x0,
   Rtp Timestamp=0xA129D0, Rtp Expiration=0x0
*Dec 27 14:10:58.754: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=7, Duration=100,
   Xrule Calling Tag=0, Xrule Called Tag=0, Digit Tone Mode=DTMF
*Dec 27 14:10:58.754: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Call Entry(Handoff Depth=0)
*Dec 27 14:10:59.022: //12898/8912F77B8243/CCAPI/cc_api_call_digit_begin:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=6, DigitBeginFlags=0x0,
   Rtp Timestamp=0xA1A6D0, Rtp Expiration=0x0
*Dec 27 14:10:59.022: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Destination Interface=0x0, Destination Mask=0x3, Destination Call Id=-1,
   Source Call Id=12898, Digit=6, Duration=100,
   Xrule Calling Tag=0, Xrule Called Tag=0, Digit Tone Mode=DTMF
*Dec 27 14:10:59.022: //12898/8912F77B8243/CCAPI/cc_api_call_digit_end:
   Call Entry(Handoff Depth=0)
*Dec 27 14:10:59.026: //12898/xxxxxxxxxxxx/CCAPI/ccCallReportDigits:
   (callID=0x3262, digit_event=0x0, enable=FALSE, consume=FALSE)
*Dec 27 14:10:59.026: //12898/8912F77B8243/CCAPI/ccCallReportDigits:
   Enabled=TRUE, Call Id=12898
*Dec 27 14:10:59.026: //12898/xxxxxxxxxxxx/CCAPI/cc_api_call_report_digits_done:
   (vdbPtr=0x4A4AE7B0, callID=0x3262, disp=0, digit_event=0x0, enable=FALSE, consume=FALSE)
*Dec 27 14:10:59.026: //12898/8912F77B8243/CCAPI/cc_api_call_report_digits_done:
   Enabled=TRUE, Disposition=0x0, Interface=0x4A4AE7B0, Call Id=12898
*Dec 27 14:10:59.026: //12898/8912F77B8243/CCAPI/cc_api_call_report_digits_done:
   Call Entry(Initial Digit Timeout=15000(ms), Inter Digit Timeout=10000(ms))
*Dec 27 14:10:59.026: //12898/8912F77B8243/CCAPI/ccCallProceeding:
   Progress Indication=NULL(0)
*Dec 27 14:10:59.030: //12898/8912F77B8243/CCAPI/ccCallSetupRequest:
   Destination=, Calling IE Present=TRUE, Mode=0,
   Outgoing Dial-peer=702, Params=0x4C5A0BDC, Progress Indication=ORIGINATING SIDE IS NON ISDN(3)
*Dec 27 14:10:59.030: //12898/8912F77B8243/CCAPI/ccCheckClipClir:
   In: Calling Number=20722672628(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
*Dec 27 14:10:59.030: //12898/8912F77B8243/CCAPI/ccCheckClipClir:
   Out: Calling Number=20722672628(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
*Dec 27 14:10:59.030: //12898/8912F77B8243/CCAPI/ccCallSetupRequest:
   Destination Pattern=91[2-9]......., Called Number=120722776, Digit Strip=FALSE
*Dec 27 14:10:59.030: //12898/8912F77B8243/CCAPI/ccCallSetupRequest:
   Calling Number=20722672628(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=120722776(TON=Unknown, NPI=Unknown),
   Redirect Number=, Display Info=Server Room
   Account Number=, Final Destination Flag=FALSE,
   Guid=8912F77B-6E37-11E3-8243-90AE21CDDC5B, Outgoing Dial-peer=702
*Dec 27 14:10:59.030: //12898/8912F77B8243/CCAPI/cc_api_display_ie_subfields:
   ccCallSetupRequest:
   cisco-username=
   ----- ccCallInfo IE subfields -----
   cisco-ani=20722672628
   cisco-anitype=0
   cisco-aniplan=0
   cisco-anipi=0
   cisco-anisi=0
   dest=120722776
   cisco-desttype=0
   cisco-destplan=0
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-lastrdn=
   cisco-rdntype=0
   cisco-rdnplan=0
   cisco-rdnpi=0
   cisco-rdnsi=0
   cisco-redirectreason=0   fwd_final_type =0
   final_redirectNumber =
   hunt_group_timeout =0
*Dec 27 14:10:59.034: //12898/8912F77B8243/CCAPI/ccIFCallSetupRequestPrivate:
   Interface=0x48C27BD0, Interface Type=3, Destination=, Mode=0x0,
   Call Params(Calling Number=20722672628,(Calling Name=Server Room)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=120722776(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=RegularLine, FinalDestinationFlag=FALSE, Outgoing Dial-peer=702, Call Count On=FALSE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
*Dec 27 14:10:59.034: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
*Dec 27 14:10:59.034: :cc_get_feature_vsa malloc success
*Dec 27 14:10:59.034: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
*Dec 27 14:10:59.034: cc_get_feature_vsa count is 2
*Dec 27 14:10:59.034: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
*Dec 27 14:10:59.034: :FEATURE_VSA attributes are: feature_name:0,feature_time:1282234584,feature_id:152
*Dec 27 14:10:59.034: //12899/8912F77B8243/CCAPI/ccIFCallSetupRequestPrivate:
   SPI Call Setup Request Is Success; Interface Type=3, FlowMode=1
*Dec 27 14:10:59.034: //12899/8912F77B8243/CCAPI/ccCallSetContext:
   Context=0x4C5A0B8C
*Dec 27 14:10:59.034: //12898/8912F77B8243/CCAPI/ccSaveDialpeerTag:
   Outgoing Dial-peer=702
*Dec 27 14:10:59.038: //12899/8912F77B8243/CCAPI/cc_api_call_proceeding:
   Interface=0x48C27BD0, Progress Indication=NULL(0)
*Dec 27 14:10:59.270: //12899/8912F77B8243/CCAPI/cc_api_call_disconnected:
   Cause Value=57, Interface=0x48C27BD0, Call Id=12899
*Dec 27 14:10:59.270: //12899/8912F77B8243/CCAPI/cc_api_call_disconnected:
   Call Entry(Responsed=TRUE, Cause Value=57, Retry Count=0)
*Dec 27 14:10:59.270: //12898/xxxxxxxxxxxx/CCAPI/ccCallReleaseResources:
   release reserved xcoding resource.
*Dec 27 14:10:59.270: //12899/8912F77B8243/CCAPI/ccCallSetAAA_Accounting:
   Accounting=0, Call Id=12899
*Dec 27 14:10:59.270: //12899/8912F77B8243/CCAPI/ccCallDisconnect:
   Cause Value=57, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=57)
*Dec 27 14:10:59.270: //12899/8912F77B8243/CCAPI/ccCallDisconnect:
   Cause Value=57, Call Entry(Responsed=TRUE, Cause Value=57)
*Dec 27 14:10:59.274: //12899/8912F77B8243/CCAPI/cc_api_call_disconnect_done:
   Disposition=0, Interface=0x48C27BD0, Tag=0x0, Call Id=12899,
   Call Entry(Disconnect Cause=57, Voice Class Cause Code=0, Retry Count=0)
*Dec 27 14:10:59.274: //12899/8912F77B8243/CCAPI/cc_api_call_disconnect_done:
   Call Disconnect Event Sent
*Dec 27 14:10:59.274: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
*Dec 27 14:10:59.274: :cc_free_feature_vsa freeing 4C6D58D0
*Dec 27 14:10:59.274: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
*Dec 27 14:10:59.274: vsacount in free is 1
*Dec 27 14:10:59.278: //12898/8912F77B8243/CCAPI/ccCallDisconnect:
   Cause Value=57, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)
*Dec 27 14:10:59.278: //12898/8912F77B8243/CCAPI/ccCallDisconnect:
   Cause Value=57, Call Entry(Responsed=TRUE, Cause Value=57)
*Dec 27 14:10:59.278: //12898/8912F77B8243/CCAPI/cc_api_get_transfer_info:
   Transfer Number Is Null
*Dec 27 14:11:02.250: //12898/8912F77B8243/CCAPI/cc_api_call_disconnect_done:
   Disposition=0, Interface=0x4A4AE7B0, Tag=0x0, Call Id=12898,
   Call Entry(Disconnect Cause=57, Voice Class Cause Code=0, Retry Count=0)
*Dec 27 14:11:02.250: //12898/8912F77B8243/CCAPI/cc_api_call_disconnect_done:
   Call Disconnect Event Sent
*Dec 27 14:11:02.250: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
*Dec 27 14:11:02.250: :cc_free_feature_vsa freeing 4C6D59B0
*Dec 27 14:11:02.250: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
*Dec 27 14:11:02.250: vsacount in free is 0ER01#

Call on PRI Line are not transfered to IP-AA on CCM

Greetings,
Having an issue with H.323 Voice gateway. Incoming calls are not transferred to Auto-Attendant. This happens randomly but I have noticed that the frequency is higher when there are no incoming call no PRI lines.
(Check the attachments for debugs)
The calls seems to be answered by gateway but ISDN-Connect message is never displayed. I tried to call from my IP Phone to but no ISDN-Connect message for this call, however, the call is landed on gateway. Running CCM 4.2(3), IPCC Express 4.0(4),IOS version 12.4(8) Advance IP Services, tried IOS 12.4(5a) Advance Enterprise Services as well but in vain.
Another questions is that: we can run both MGCP and H.323 on voice gateway but how will it register with CallManager. I guess we can use some loopback technique for this purpose. Need suggestions/comments!!!
Please find the attachments of Q921 and Q931 debugs. Took debugs for 2-scenarios
1- Called from and outside number to PRI line
2- Called from IP-phone to PRI line
Regards,
Syed Khalid Ali

You can refer this guide for more information on configuring loopback for PRI interface:
http://www.cisco.com/en/US/docs/ios/12_2/dial/configuration/guide/dafchant.html#wp1002838

Smart dialing not working for me

I have Alltel, which requires 10 digit dialing. I turned on the smart dialing feature, and entered my area code. But every time I dial a 7 digit number, I just get an error message from Alltel that I must use 10 digits. Is there a trick to getting smart dial working?

Odd, I don't have the "use 1 for National Dialing" setting.
Perhaps you should turn that to Yes.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Agent desktop changing dial number as entered

In the agent desktop there is a checkbox, "dial number as entered" that I want to be checked when the application is started. How do I do this?

3 years later I'm running UCCX 8.5(1)SU2 with CAD 8.5.1.214 and have the same issue. Did you ever get a solution or workaround?
Without putting a checkmark in "Dial Number as Entered" I enter a 5-digit extension I get in bottom left corner "Call Failed: Invalid Destination", if I put the checkmark in I can 5 digit dial.

CCM 4.1(3) - DialPlan 7-digit dialing Configuration

Similar Messages

Maybe you are looking for