[cisco-voip] Area Code vs NXX Conflict

[Walt Moody]

Brian,

I'm aware of the potential for future conflicts.  Right now, the only
conflict is 623.  If at some far in the future date we have PRIs in
928, and 928 is in conflict, we'll have to deal with it.

Lelio,

Interdigit time outs could be a problem, but the more pressing problem 
is routes.  How do you tell 623[2-9]XXXXXX to go to the PSTN trunks in
Phoenix, and 623[2-9]XXX to go to Tucson's PSTN trunks?  There doesn't
seem to be a way to build a conflict table with different routing for
seven digits versus ten.

-walt

Brian Prentiss wrote:
> The thing is with the first option here, is that potentially you would 
> have a similiar situation with the other area codes at some point, as 
> the population growth forces more NXX assignments in the 520 area code.  
> Also, as people wait for that interdigit timeout, they might be thinking 
> "did it go through?" and that might be a bit of a challenge support wise.
>  
> Are you planning on doing the same with the 928 area code that is in the 
> other part of the state?
>  
> Regards,
> Brian
> 
>  
> On 5/9/07, Lelio Fulgenzi <lelio at uoguelph.ca <mailto:lelio at uoguelph.ca>> 
> wrote:
> 
>     If you can live with interdigit timeout, then you should be able to
>     program things so that you can dial either number and get through.
>     Users will have to wait 10 seconds (or whatever your parameter is
>     configured for) before 7 digit calls are placed -or- if I'm not
>     mistaken, they can press # to complete the dialing process (you
>     might need an extra route pattern with the # at the end though as
>     well).
>      
>     Other than that, if you are looking to be able to dial a 7 digit and
>     10 digit call with the same beginning three digits and not have
>     interdigit timeout at the end, I do not think you will be able to do
>     this.
>      
>      
>     --------------------------------------------------------------------------------
>     Lelio Fulgenzi, B.A.
>     Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>     (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>     ...there's no such thing as a bad timbit...
> 
>         ----- Original Message -----
>         From: Walt Moody <mailto:moody at arizona.edu>
>         To: cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>         Sent: Wednesday, May 09, 2007 2:04 PM
>         Subject: [cisco-voip] Area Code vs NXX Conflict
> 
>          
>         Here's the setup:
> 
>         The University of Arizona - in Tucson - uses seven digit dialing for
>         both on Campus and off Campus local calls.  We do not use 9+ or any
>         other PBX "outside access" codes.  NANP long distance is 1+ 10
>         digits,
>         IDDD is 011+.
> 
>         Except:  When dialing from our Tucson Campus to our Phoenix
>         Campus, we
>         dial 602827XXXX.  We do not use a "1" or any other prefix digit
>         to when
>         we dial a "free" or on-net call.
> 
>         Still with me?   OK, try this: We want to set up our dial plans
>         so that
>         we can use 10 digits to call from the Tucson Campus to anywhere
>         in the
>         Phoenix rate center, which consists of Area Codes 480, 602, and
>         623.
>         That's easy enough to do, except (there's that word again) 623
>         is both
>         an Area Code in Phoenix and an NXX in Tucson.
> 
>         I need to find a way to tell the difference between, for
>         example, the
>         dialed digits (623) 555-1212 and 623-5551 and route the 10 digit
>         "623"
>         numbers to our PRIs in Phoenix and the 7 digit "623" numbers to the
>         local Tucson PRIs.
> 
>         Prefix digits are not an option -- there are several PBXs in
>         addition
>         to the CallManagers that are part of the University's voice
>         services,
>         and no real good way to change them from their current dial plans.
> 
>         Ideas, anyone?
> 
>         Thanks,
> 
>         -walt
>         _______________________________________________
>         cisco-voip mailing list
>         cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>         https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> 
>     _______________________________________________
>     cisco-voip mailing list
>     cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>     https://puck.nether.net/mailman/listinfo/cisco-voip
> 
>