[cisco-voip] E.164 dialing

[Ryan O'Connell]

That's what I'm saying is that I shouldn't need the "+" if the number is a fully qualified E.164 number.

Thoughts?


-----Original Message-----
From: Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
Sent: Monday, July 14, 2008 6:33 AM
To: Ryan O'Connell; cisco-voip at puck-nether.net
Subject: RE: [cisco-voip] E.164 dialing

Unfortunately, you are going to have to wait for UCM 7.0 to have full
E164 support.  Currently UCM throws up when it gets a '+'.

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan O'Connell
Sent: Friday, July 11, 2008 3:54 PM
To: cisco-voip at puck-nether.net
Subject: [cisco-voip] E.164 dialing



Hello,

I am working on a Dialplan that is based on E.164 numbers. Essentially
all internal DN's will be the fully qualified E.164 number without the
"+" so for NANP that will be 11 digits and in Europe it will consist of
country-code followed by local exchange. Using partitions and CSS's to
maintain interal 4 digit dialing intra-site and full E.164 inter-site.
For DID's the above plan is pretty straight forward but for non-DID's I
can't seem to find any ranges within the NANP that are designated as
private addresses. So if I want to assign 100 DN's to be voicemail ports
or lobby phones or whatever I was wondering what I should make these
numbers so that it doesn't overlap with any PSTN numbers.

If anyone can share thoughts or their experiences in this area that
would be helpful thanks


Ryno
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.