[cisco-voip] Cisco Dialplans China to the US

[Todd Simons]

All-
I'll figure out the dialplans and share.

Question to those of you doing least cost routing... when you pass calls
around, do you just pass the US 10 digit number, then add 1 as necessary
at the last VoIP PBX before PSTN?

Our setup:

PSTN--PBX1--Router1--/----\
                     |VoIP|--Router3--PBX3--PSTN
PSTN--PBX2--Router3--\----/                    

  
Example: 
	China User Dials 9-1-732-111-1111
	VoIP Option 1: strip 91, send 732111111, add 9 and 1 as
necessary based on target PBX that will hand off to the PSTN
	VoIP Option 2: keep 91, send 91732111111, hand off call

I'm leaning towards just 10 digits, PBX1 & PBX2 are on the east coast
and can easily be backups for each other.  PBX3 is in China.

~Todd

-----Original Message-----
From: Matthew Saskin [mailto:matt at saskin.net] 
Sent: Monday, March 03, 2008 11:15 AM
To: Todd Simons
Cc: Joel P; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Cisco Dialplans China to the US

Sorry, don't happen to have any.  The extent of TEHO that i've worked 
with lately is within callmanager and is just to intercept calls from 
the US to specific foreign countries.

Speaking for the NYC/northern NJ area, the major NPA's include 201, 551,

212, 347, 718, 978, 646, and 917

Not sure off the top of my head about the boston area.

Todd Simons wrote:
> Matt-
> Thanks
> 
> Most of the call volume will be to our project managers and support
> personel cell phones, local to our NJ or MA office, so I expect to
> create specific dialpeers for those area codes, and have secondary
> dialpeer that covers all numbers.
> 
> Do you have any sample Cisco config for the dial-peers for the US
NPAs?
> And/or China NPAs?
> 
> ~Todd
> 
> -----Original Message-----
> From: Matthew Saskin [mailto:matt at saskin.net] 
> Sent: Friday, February 29, 2008 9:38 AM
> To: Todd Simons
> Cc: Joel P; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Cisco Dialplans China to the US
> 
> What you're looking to accomplish is called tail-end hop-off.  What
I'm 
> guessing you're looking for is the list of all possible NPA's for 
> Massachusetts and New Jersey?
> 
> For what it's worth, if you're going to haul the traffic across the 
> sites anyhow, it may just be easiest to do tail-end hop-off for *all*
us
> 
> calls originating from China and send them out one of the US gateways
- 
> also makes the patterns much simpler (just match the 1 and the and 10 
> digit fixed length phone number, plus whatever the international dial 
> prefix is in China)
> 
> -matt
> 
> Todd Simons wrote:
>> Joel-
>>
>> I'm new to all this, so please bear with me.  I'm not sure what the 
>> difference between MGCP and H323 is.
>>
>>  
>>
>> Our internet routers have additional T1 cards for voice configured
> with 
>> PRI connections to our PBXs.  From there, we setup dial-peer 
>> definitions, pots to the T1 (and in some cases FXS cards) and VoIP 
>> between the routers.   The PBXs have the connectivity to the PSTN 
>> through PRI, E&M T1 and CoT (based on call needs, local/long
distance)
> 
>> and will route the calls accordingly.
>>
>>  
>>
>> I expect the call path from our China Office to a 732 area code to
be:
>>
>>
>
Phone->ChinaPBX=E1/PRI=>ChinaRouter**VOIPCloud**>NJRouter=T1/PRI=>NJPBX=
> T1/PRI=>PSTNCloud->Phone
>>  
>>
>> We can handle the routing into/out of the PBXs, I'm looking for the 
>> dialpeer and translation rules for the Cisco router configs.
>>
>>  
>>
>> What are ICTs?
>>
>>  
>>
>> ~Todd
>>
>>  
>>
>> *From:* Joel P [mailto:tman701 at gmail.com]
>> *Sent:* Friday, February 29, 2008 12:02 AM
>> *To:* Todd Simons; cisco-voip at puck.nether.net
>> *Subject:* RE: [cisco-voip] Cisco Dialplans China to the US
>>
>>  
>>
>> If im understanding your request correctly you could just build some 
>> route patterns pointing to the far-end gateways.
>>
>> Then at each GW pass the call out your PSTN.
>>
>> Not sure if youre using MGCP or H323 GW's, but it can be accomplished

>> either way.
>>
>> Do you have ICT's for the calling between sites in your Cloud?
>>
>>  
>>
>> Joel P
>>
>>  
>>
>>
>
------------------------------------------------------------------------
>> *From:* cisco-voip-bounces at puck.nether.net 
>> [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf Of *Todd
Simons
>> *Sent:* Thursday, February 28, 2008 9:25 PM
>> *To:* Todd Simons; cisco-voip at puck.nether.net
>> *Subject:* Re: [cisco-voip] Cisco Dialplans China to the US
>>
>>  
>>
>> All-
>>
>> Clarification... we already have an established VoIP cloud for
4-digit
> 
>> dialing.   We want to send public calling through the VoIP cloud too.
> 
>> ...for example, in our NJ office, if we dial a China telephone call,
> we 
>> want it to go through OUR VoIP Cloud to china, then out to the PSTN
> from 
>> our Shanghai PBX, or in our Shanghai office if they call a NJ phone 
>> number, the calls get routed through the VoIP cloud to our NJ PBX,
> which 
>> will put the call out to the PSTN.
>>
>>  
>>
>> ~Todd
>>
>>  
>>
>> *From:* cisco-voip-bounces at puck.nether.net 
>> [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf Of *Todd
Simons
>> *Sent:* Thursday, February 28, 2008 9:07 PM
>> *To:* cisco-voip at puck.nether.net
>> *Subject:* [cisco-voip] Cisco Dialplans China to the US
>>
>>  
>>
>> Hello all
>>
>> I'm starting a project to implement least cost routing between our 
>> Shanghai, Boston, and NJ offices.  Just wondering if anyone has a 
>> dialplan (dial-peers, translations, etc) that they can share for the 
>> PSTN call routing, or if anyone has seen any good resources on the
Web
> 
>> for this.
>>
>>  
>>
>> Many Thanks!
>>
>> ~Todd
>>
>>
>> ## Scanned by Delphi Technology, Inc. ##
>>
>>
>> ## Scanned by Delphi Technology, Inc. ##
>>
>>
>> ## Scanned by Delphi Technology, Inc. ##
>>
>>
>>
>
------------------------------------------------------------------------
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> 
> ## Scanned by Delphi Technology, Inc. ##


## Scanned by Delphi Technology, Inc. ##