Cisco CME translation rule and dial peer help
We have a Cisco CME configured for a site and I am wanting to implement a dial shortcut to quickly call a specific number.
Essentially I am wanting to dial *88 from a Cisco phone and have that translated to 1-800-123-4567 and have that ring out to that destination number. The site is configured to dial 9 for outbound calls but I do not want to have the callers dial 9 before the *88. (we have *88 configured in our main site with full CUCM and it works fine and we want to keep the same code out at this remote office with its stand alone phone system).
What I have done so far...
voice translation-rule 2
rule 6 /^.*88/ /18001234567/
After that, if I "test voice translation-rule 2 *88" it comes back with the following:
Matched with rule 6
Original number: *88 Translated number: 18001234567
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none
Without doing anything else I got a fast busy when trying to dial the number so I assumed I wasn't getting an outside dial tone with that on its own.
Then I created a dial-peer for *88 hoping that would help...
dial-peer voice 35 pots
description **Work Alone**
translation-profile outgoing trnsprfOUTBOUND
preference 1
destination-pattern *88
progress_ind setup enable 3
port 0/0/0:23
Now I get a message indicating the call cannot be completed as dialed, which I am assuming is coming from the telco so I am assuming that now it is passing *88 out to the telco which is not what I want.
What am I missing with this?
Essentially I am wanting to dial *88 from a Cisco phone and have that translated to 1-800-123-4567 and have that ring out to that destination number. The site is configured to dial 9 for outbound calls but I do not want to have the callers dial 9 before the *88. (we have *88 configured in our main site with full CUCM and it works fine and we want to keep the same code out at this remote office with its stand alone phone system).
What I have done so far...
voice translation-rule 2
rule 6 /^.*88/ /18001234567/
After that, if I "test voice translation-rule 2 *88" it comes back with the following:
Matched with rule 6
Original number: *88 Translated number: 18001234567
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none
Without doing anything else I got a fast busy when trying to dial the number so I assumed I wasn't getting an outside dial tone with that on its own.
Then I created a dial-peer for *88 hoping that would help...
dial-peer voice 35 pots
description **Work Alone**
translation-profile outgoing trnsprfOUTBOUND
preference 1
destination-pattern *88
progress_ind setup enable 3
port 0/0/0:23
Now I get a message indicating the call cannot be completed as dialed, which I am assuming is coming from the telco so I am assuming that now it is passing *88 out to the telco which is not what I want.
What am I missing with this?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Is translation-rule 2 configured to translate the called number in the trnsprfOUTBOUND profile?
ASKER
Yes it is configured for outbound.
I will remove the dial peer as instructed and modify the translation rule and see what happens. Will report back on Monday after make the changes to let you all know if that worked.
I will remove the dial peer as instructed and modify the translation rule and see what happens. Will report back on Monday after make the changes to let you all know if that worked.
ASKER
So this morning I removed the dial peer and updated the translation rule 6 as described by Arnold and I am still getting a busy signal when calling outbound.
Kimputer, I didn't bother just deleting the dial peer and keeling the existing translation rule since I had tried that prior to implementing the dial peer.
Sr75, I believe I am putting the translation in the correct spot, but when I checked again this is what I have in the config...
voice translation-rule 1
rule 1 /^2506411700/ /1700/
rule 2 /^.*\(....\)/ /\1/
!
voice translation-rule 2
rule 3 /^2506418100$/ /2506411700/
rule 4 /^8100$/ /2506411700/
rule 5 /^8/ /2506418/
rule 6 /^[*]88$/ /918001234567/
rule 7 /.*/ /2506411700/
!
!
voice translation-profile trnsprfINBOUND
translate called 1
!
voice translation-profile trnsprfOUTBOUND
translate calling 2
Sr75 did mention CALLED in bold but mine is under CALLING...
Any other suggestions?
Kimputer, I didn't bother just deleting the dial peer and keeling the existing translation rule since I had tried that prior to implementing the dial peer.
Sr75, I believe I am putting the translation in the correct spot, but when I checked again this is what I have in the config...
voice translation-rule 1
rule 1 /^2506411700/ /1700/
rule 2 /^.*\(....\)/ /\1/
!
voice translation-rule 2
rule 3 /^2506418100$/ /2506411700/
rule 4 /^8100$/ /2506411700/
rule 5 /^8/ /2506418/
rule 6 /^[*]88$/ /918001234567/
rule 7 /.*/ /2506411700/
!
!
voice translation-profile trnsprfINBOUND
translate called 1
!
voice translation-profile trnsprfOUTBOUND
translate calling 2
Sr75 did mention CALLED in bold but mine is under CALLING...
Any other suggestions?
The CALLING number is the number being called FROM (i.e. the Caller ID). you are wanting to change the number being called TO (i.e. the Desitination). It needs to be changed to CALLED so that your users can dial *88 and get routed to 800.123.4567.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
SR75, I did as you instructed and created the new voice translation rule and applied that to the translation profile but we are still just getting a busy signal when calling *88.
I also just want to get some clarification on rule processing. We moved rule 6 to that translation-rule 3. Do the rules still get processed in the same sequence (ie 1 through 7 regardless of the translation rule set they are in)? Rule 7 picks up the *88 as well and translates it to the DID of the site so I just wanted to make sure it isn't hitting that before it tries rule 6 in the third rule set.
Any other suggestions?
I also just want to get some clarification on rule processing. We moved rule 6 to that translation-rule 3. Do the rules still get processed in the same sequence (ie 1 through 7 regardless of the translation rule set they are in)? Rule 7 picks up the *88 as well and translates it to the DID of the site so I just wanted to make sure it isn't hitting that before it tries rule 6 in the third rule set.
Any other suggestions?
Each translation-rule can have a set of 16 rules (numbered 1 - 16). Each set is different from the others. This means you can have three rule 1s. The translation profile is a top to bottom check. It will check the top most profile first for a match and then continue on.
Your dial-peer is directly assigned to a port, you do not need to dial a 9 unless your telco is asking for it (which would be odd for them to do so). So in the Translation rule 3, put what digits your telco is expecting to receive.
Your dial-peer is directly assigned to a port, you do not need to dial a 9 unless your telco is asking for it (which would be odd for them to do so). So in the Translation rule 3, put what digits your telco is expecting to receive.
ASKER
If it tries all the rules in translation-rule 2 BEFORE it tries any of the rules in translation-rule 3 then the rule 6 would get hit after rule 7 in the sequence of things and rule 7 also catching *88 and does something different with it so maybe that is why this isn't working?
With the partial information you currently posted it is hard to say where your issue is.
Your best is to debug the dial out attempt to see which rule it follows when *88 is dialed.
Your best is to debug the dial out attempt to see which rule it follows when *88 is dialed.
ASKER
I have opened a Cisco TAC case and I am hoping to get some assistance with them today. Once I figure out what is wrong I will post a solution and if it matches suggestions on here that I have incorrectly implemented then I will accept the solution(s) to distribute the points.
The issue is whether the UC auto handles *xx translations in a different rule, such that it never hits your rule, though not clear which translation rule you have.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The solutions provided were not complete and I still needed to contact the vendor to get the missing piece to make it all work. I have posted the ultimate solution that was achieved through vendor support which was very close to two submitted options.
voice translation-rule 2
rule 6 /^.*88/ /918001234567/
Remove what you did afterwards (dialpeer).