[cisco-voip] PSTN E.164 call routing

Tue Jul 15 15:07:26 EDT 2008

"Cleaner would be to ship a fully qualified number out and let the telco
figure it out."

I would think telco won't figure it out, but instead play back a message
about you need to not dial a area code or number is not valid, etc.

I agree overall more digits is better, you can also translate to less to
PSTN, etc.  I have a customer with this issue now a CRM box that
outdials everything based upon 10-digit which doesn't work for some
locals calls as we still have 7-digit dialing here....

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan O'Connell
Sent: Tuesday, July 15, 2008 10:23 AM
To: Tim Smith
Cc: cisco voip
Subject: Re: [cisco-voip] PSTN E.164 call routing

That is exactly what I'm trying to achieve is less route plan entries,
and a much cleaner design overall. Back to the Calgary example, area
code 403 is shared between Local calls and Long distance calls, and that
is just one of 2 area codes for this region. If I want to designate
which NNX is local vs LD based on the gateway it is leaving the network
from then I would need to write patterns for each, not only that I would
have to keep them current ass NNX's are added into the NANP. No Thanks.
Cleaner would be to ship a fully qualified number out and let the telco
figure it out. So back to my question do you know if this is possible to
achieve? I'm pretty sure this can be done using SIP trunks to the
service provider but not so sure on the traditional side as in PRI
circuits.

I am not sure I am following what you are saying where I could achieve
this by creatively selecting which GW certain area codes exit the
network from, essentially making all calls long distance? Is this what
you are suggesting?

Thoughts

Ryan

________________________________

From: smithsonianwa at gmail.com [mailto:smithsonianwa at gmail.com] On Behalf
Of Tim Smith
Sent: Tuesday, July 15, 2008 1:54 AM
To: Ryan O'Connell
Cc: cisco voip
Subject: Re: [cisco-voip] PSTN E.164 call routing

Hi Ryan,

Are you able to dial the full E164 number by using the international
access code? I would have thought this would work?

This would usually come down to your dialplan design.. i.e. route a call
out a certain circuit, and make sure that you are sending the digits
required on that circuit so the call can be completed.. this can be
different for providers, or could be different if you throw the call out
a remote gateway or something for example...

What are you really trying to achieve? Are you just trying to use less
route plan entries :)

Cheers,

Tim

On 7/14/08, Ryan O'Connell <Roconnell at unislumin.com> wrote: 

Does anyone know if service providers have any present day capabilities
or future plans to pass full e.164 numbers. For example we want to pass
full numbers to the PSTN whether they are local or long distance and let
the carrier figure it out very similar to how it works on the Mobil
networks. So today if we are in Calgary and we want to dial another
Calgary number we must dial 4031234567, if we dial the same number with
a leading 1 then the call gets rejected. Is there any means to make it
like it is on the mobile network where if the same number is dialed with
the 1 so 14031234567, while in Calgary, and the call gets passed? I know
with the introduction to SIP trunking services they would have to take
both the 10 digit local number and the 11 digit equivalent and route it
accordingly because the point of entry into the PSTN cloud may not
necessarily be local. If this is the case I wonder if it's possible with
TDM circuits as well?

Thoughts?

Ryan

_______________________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080715/eb9446af/attachment-0001.html>