E.164 International Numbering Format

[mschuh]

Hi there,

what happens at CCM when a user dials (e.g with TSP from Outlook Address Book) +3312345678?

supports the CCM special characters like the +?

thanks

Manfred

[b.hsu]

the North American Numbering Plan (NANP) is used, which consists of an area code, an office code, and a station code. Area codes are assigned geographically, office codes are assigned to specific switches, and station codes identify a specific port on that switch. The format in North America is 1Nxx-Nxx-xxxx, with N = digits 2 through 9 and x = digits 0 through 9. Internationally, each country is assigned a one- to three-digit country code; the country's dialing plan follows the country code. In Cisco's voice implementations, numbering schemes are configured using the destination-pattern command.

http://www.cisco.com/en/US/products/hw/routers/ps221/products_configuration_guide_chapter09186a008007c9a1.html

[oliliac]

Hi Manfred,

CCM simply ignore character + found at the beging of the string. I have a client that use AD integration and all numbers was defined in E.164 format even if the CCM use only 4 digits. It was a company politic. So I simply define a translation rule.

So in AD all numbers are in format: +4021302xxxx. I define a translation pattern with pattern 4021302xxxx and called transformation mask xxxx and all works ok.

You must create translation pattern based on your needs.

Hope that this will help you

regards

ovidiu

[paul.harrison · Accepted solution]

Manfred,

you need to make sure that the number in the address book are consitant first. So make sure all the numbers are stored as Full E.164 as per your example.

Then make sure you area settings are correct in control panel >phones and modems so that it knows that it should dial your access code for an outside line.

The only other thing to do is make sure that if you have to insert a digit to call a number (e.g. 0) that it's in brackets, so you example would be +33 (0)12345678. Then the Microsoft rules will dial the number as 0 .

If you are importing the numbers from a mobile this is a problem for calls in your own country because the mobile will not store the (0) part. so then you need to not use the access code you would use for normal long distance calls (9) you would use 90 instead. This then put the 0 back into the call. This works fine because you've already told the microsoft dialer what country you're in so it knows what the country code part of the number is.

Of course anyone in the USA can ignore this because you don't make calls like the rest of the world.

Paul

[mschuh]

Hi Paul,

thanks for assistance. You're right with your statement about the settings in control panel. I've used netmon to trace what happens with different settings.