Redial/Missed Calls Adding 9 or 91 as a prefix with a little twist

[john.almazan]

So I need to add a 9 or 91 (depending on local or long distance) to outbound calls when someone tries to return a call using missed, redial, received directory from the phone, CUPC, etc.  I was going to follow the instructions noted here:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00805b6f33.shtml

From what I understand it will append the 91 to all inbound calls so that when they appear in the directory, it'll already have that prefix. 

Prior to implementing this,  I go through my missed calls list to see what format they come in on.  I see calls from off network that come in as a 3 digit area code and then 7 digits.  So I think great, i'll just add the 91. 

Then I come across a call from Orlando, FL and notice in came in as 14072412965.  Now my solution will not work because if I add the 91 when it comes in, it will dial 911 when I attempt to redial!

Thoughts on getting around this?  I"m a bit of a newbie so please be gentle.  Thanks.

John

By the way, using the following:

Cisco Unified CM Administration
System version: 8.5.1.11900-21
VMware Installation: 2 vCPU Intel(R) Xeon(R) CPU E5506 @ 2.13GHz, disk 1: 80Gbytes, 4096Mbytes RAM

Cisco Unified Presence Administration
System Version: 8.5.1.10000-35

Cisco Unity Connection Administration
Version 8.5.1ES16.11900-16 Unrestricted

Cisco Unified Personal Communicator
Version 8.5.1.17660-6.1.34
Client Services Framework 8.5(2)-4.2.13

[iptuser55]

As you are running CUCM8.5 you can make use of the Gateway prefix method if you have different telco`s or you have links from other telephony system. If you have a stand-alone CUCM and the Telco`s do not send you different CLI then use the Global settings in Service Params under Call Managaer>Advanced- There are two of them MGCP and H323 - look for "Incoming Calling Party ....... Prefix" - It is here you add the missing prefix 91, 9 , 900 etc depending on the calling type message you see when you do a debug ISDN q931 on the GW`s

If you have different telco`s or you have links to other telephony systems then the format of the CLI coming in may be different per Telco, Link so you need to do the work per GW, E1 level - same principle

　

Identify the GW you are using for incoming calls, scroll down the bottom and you will see "Incoming Calling Party Setting"- again It is here you add the missing prefix 91, 9 , 900 and delete the number of leading digits etc depending on the calling type message you see when you do a debug ISDN q931 on the GW`s

hope it helps

[Marwan ALshawi]

ipuser55 is right you can do it differently now iwth CUCM version 7.x and later using incoming calling number section in the GW seting page

or you could use h323 digitmanipulation to do the same but you need to have difrent inbound dial-peers with answer address to prefix differnt numbers as you sated above

once you confirm version and gateway type and which way you wanna go we can help you with more details

HTH

[Dmitry Golovenkin]

The following has worked for me. Many thanks

iptuser55 wrote:
Identify the GW you are using for incoming calls, scroll down the bottom and you will see "Incoming Calling Party Setting"- again It is here you add the missing prefix 91, 9 , 900 and delete the number of leading digits etc depending on the calling type message you see when you do a debug ISDN q931 on the GW`s

[john.almazan]

So to add a little fly into the ointment, I'm in the middle of moving from one VoIP system (I3) to Cisco.  Currently our off net inbound gateways are attached to I3 and I have a trunk between Cisco and I3.  I3 delivers all offnet inbound calls bound for Cisco via this trunk.  With that said, I currently don't have any of the gateways registered directly with Cisco.  I suppose i need to do the prefix manipulation from I3's end?

John

[Marwan ALshawi]

i am not aware about how this system works

however if you can you could do it nt sure if it can prefix base don calling number for example

or you can do it in the Cisco H323 Voice gateway using translations rules and profiles

[acampbell]

Hi,

I think John means that he has an H323 trunk to old system, NO router involved

Regards

Alex

[john.almazan]

All

I think there is a little bit of a misunderstanding.  I do have Cisco H323 servers but they are "registered" with I3 and not with CUCM.  Despite that, I decided to try configuring some translation rules at the gateway level as per marwanshawi.  This is what I came up with:

voice translation-rule 1

rule 1 /^916\(.......\)/ /9\1/

rule 2 /^1916\(.......\)/ /9\1/

rule 3 /1........../ /9\0/

rule 4 /........../ /91\0/

!

!

voice translation-profile format_outbound_calls

translate calling 1

voice-port 0/0/0:23

translation-profile incoming format_outbound_calls

We are in the 916 area code so:

If I see 916xxxxxxx, I strip the 916 and prepend a 9. (Rule 1)

If I see 1916xxxxxxx, I strip the 1916 and prependend a 9. (Rule 2)

For other long distance:

If I see 1xxxxxxxxxx, I prepend a 9. (Rule 3)

If I see xxxxxxxxxx, I prepend a 91. (Rule 4)

I figure toll free numbers will apply to rule 3 and 4 and as well.  I have not yet addressed international calls.  I think with the rules above, I avoid dialing 911 or 9911 by accident.

I have tested using test voice translation-rule 1 command.  Seems to work properly.

Comments?  Concerns?  Any issues with these rules?  Thanks!

John