How to add a 9 for missed calls

[mgerron]

Our users want to be able to select a missed call and place a call without having to add the 9 for outgoing calls. What is the best way to do this?

[gergs00]

Yes, Yes,

We would like the same ability. Anyone have a suggestion?

[8r-schumann]

I have done this for sites and it is a little tricky. First you want to add a partiton and a new CSS for your gateways that contain translation patterns to prefix a 9 on ANI of the inbound calls.

The tricky part is if you do not have 10 digit dialing in your area or you limit who can call LD you will need to identify all local numbers so that you strip off the area code for the local number before they go to the PSTN.

[efisher]

I agree it can be tricky. Call Manager Fundamentals by John Alexander, Chris Pearce, Anne Smith, Delon Whetten have clear cut example on how to do this.

[awyle]

Hi, We done this on our router via the Incoming Dial-Peers.

See config below...

translation-rule 88

Rule 1 ^1.% 901

Rule 2 ^2.% 902

Rule 3 ^3.% 903

Rule 4 ^4.% 904

Rule 5 ^5.% 905

Rule 6 ^6.% 906

Rule 7 ^7.% 907

Rule 8 ^8.% 908

Rule 9 ^9.% 909

dial-peer voice 100 voip

tone ringback alert-no-PI

preference 1

destination-pattern 2.....

translate-outgoing calling 88

translate-outgoing called 1

voice-class codec 1

voice-class h323 1

session target ipv4:172.16.1.1

dtmf-relay h245-alphanumeric

ip qos dscp cs5 media

no vad

Hope this helps.

Thanks Gus

[oliver-jones]

Hi,

I have configured this by doing the following;

i) create a partition i.e GWtranslation_PT

ii) create 2 Calling search spaces. GW_CSS and GWtranslation_CSS. Put the GWtranslation_PT into GW_CSS and put GWtranslation_PT and your users line partition into GWtranslation_CSS

iii) create the translation pattern XXXX in CCM (assuming you are using 4 digit dialling). Set the patterns partition to be GW_translation_PT and the CSS to GWtranslation_CSS. Set Prefix digits (outgoing) to 90

iv) On your gateway, Set the inbound calls CSS to GW_CSS

You should then see that the 90 is added to the call and the users do not have to edit the string before redialing missed calls,

Hope this helps

[kvaradar]

1. Go to Route Plan>Partition>Create a Partition for translation. For example

"InboundTranslate_PT"

2- Go to Route Plan>Calling Search Space>Create a Calling Search Space

"Translate_CSS" and only include partition "InboundTranslate_PT" in that.

3- Go to gateway and find your router Gateway to PSTN.

4- Assign "Translate_CSS" to the gateway Calling Search Space.

5- Go to Route Plan>Translation pattern> Add a new translation pattern as follows

under Pattern Definition

Translation pattern 2xxx --------> this is your phones directory number range

Partition Translate_CSS

Calling Search Space Phone_CSS -------> this is the CSS where your phones are assigned.

Under Calling party Transformation -----> Prefix digits '0'

[lfulgenzi]

We wanted to do this as well, but adding a 9 is not the only thing you have to worry about. You have to add a 9 for local, a 9+1 for long distance, and a 9+011 for direct dial international (Canadian examples). After asking our SE, we were pointed to the following system parameters [in 3.3(3)sr4a]:

National Number Prefix (likely 91)

International Number Prefix (likely 9011)

Subscriber Number Prefix (likely 9)

Unknown Number Prefix

I've included the definition from the config page at the end of this post.

We have not tried this yet, but are hoping to do so soon. The problem we have is that a national number is identified when 10 digits are sent to your system. This is the case in areas that have 10 digit local dialing. However, it is also the case in areas that are 'preparing' for 10 digit local dialing. Our PSTN sends 10 digits to us even for local calls, so all our incoming calls are marked as national, so they would appear in the calls directory as 91519xxxxxxx. It will be confusing to the user, but a route patterns that take the 91519 out by using a route filter choosing our local exchanges and applying one of the following Discard Digits Instructions depending on what you need.

- 11/10D->7D

- 11/10D->7D Trailing-#

- 11D->10D

- 11D->10D Trailing-#

The other thing we noticed after doing a trace of our incoming ISDN/PRI calls, was that sometimes, the calling number has not been sent properly (either network or user supplied) such that some internationall numbers already have the international dialing prefix which can cause problems.

The short story is, you can be guarenteed that the number being sent will be formatted properly.

I'm hoping to test this sometime soon, and will try to remember to post a follow up message.

=================================================

National Number Prefix : This parameter defined the number that is prefixed to an incoming national number.

Maximum length: 8.

Allowed values: A string in the form of maximal 8 digits (0-9).

International Number Prefix : This parameter defined the number that is prefixed to an incoming international number.

Maximum length: 8.

Allowed values: A string in the form of maximal 8 digits (0-9).

Subscriber Number Prefix : This parameter defined the number that is prefixed to an incoming subscriber number.

Maximum length: 8.

Allowed values: A string in the form of maximal 8 digits (0-9).

Unknown Number Prefix : This parameter defined the number that is prefixed to an incoming unknown number.

Maximum length: 8.

Allowed values: A string in the form of maximal 8 digits (0-9).

===============================================

[abdulr]

!

voice translation-rule 1

rule 1 /\(404.......\)/ /9\1/

rule 2 /\(678.......\)/ /9\1/

rule 3 /\(770.......\)/ /9\1/

rule 4 /\(.*\)/ /91\1/

!

!

voice translation-profile ANI

translate calling 1

!

dial-peer voice 100 voip

translation-profile outgoing ANI

session target ipv4:10.1.21.33

!

404,678,770 are local numbers and 9 is added to ANI and for all other calls 91 is added, if you need international as well, you can add more specific long distance area codes and prefix 91, & for rest you can prefix 011.