[cisco-voip] IOS strip digits from 8 to 4
Mike Lydick
mikelydick at yahoo.com
Wed May 9 21:14:16 EDT 2007
Just a guess but how about:
Translation-rule 1
rule 1 ..../..../ /..../
----- Original Message ----
From: "cisco-voip-request at puck.nether.net" <cisco-voip-request at puck.nether.net>
To: cisco-voip at puck.nether.net
Sent: Wednesday, May 9, 2007 7:56:06 PM
Subject: cisco-voip Digest, Vol 51, Issue 59
Send cisco-voip mailing list submissions to
cisco-voip at puck.nether.net
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
cisco-voip-request at puck.nether.net
You can reach the person managing the list at
cisco-voip-owner at puck.nether.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. Re: Area Code vs NXX Conflict (Jason Aarons (US))
2. VGW + throughput (Voll, Scott)
3. IOS strip digits from 8 to 4 (Jason Aarons (US))
4. Re: Area Code vs NXX Conflict (Lelio Fulgenzi)
----------------------------------------------------------------------
Message: 1
Date: Wed, 9 May 2007 17:42:41 -0400
From: "Jason Aarons \(US\)" <jason.aarons at us.didata.com>
Subject: Re: [cisco-voip] Area Code vs NXX Conflict
To: "Walt Moody" <moody at arizona.edu>, <cisco-voip at puck.nether.net>
Message-ID:
<C1FE15183DA37645BC0633BC604E44F00586BDF8 at USNAEXCH.na.didata.local>
Content-Type: text/plain; charset="us-ascii"
You would have to get a list of NPA-XXXs for that CO and expand the
route pattern. I've done this for TEHO (Tail End Hop Off) routing,
Atlanta had hundreds of NPA-XXXs...headache to keep up with..
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Walt Moody
Sent: Wednesday, May 09, 2007 4:19 PM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Area Code vs NXX Conflict
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
>
>
_______________________________________________
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.
------------------------------
Message: 2
Date: Wed, 9 May 2007 15:42:08 -0700
From: "Voll, Scott" <Scott.Voll at wesd.org>
Subject: [cisco-voip] VGW + throughput
To: <cisco-voip at puck.nether.net>
Message-ID: <407055A92CECCB499C922A2D35FC19A608DEE742 at Apollo.wesd.org>
Content-Type: text/plain; charset="us-ascii"
What should I expect for Throughput on a ISR VGW.
2801 = ?mb
2811 = ?mb
2821 =
2851 =
3825 =
Plus they will be doing a couple pots lines and ~8 FXS/FXO ports, and
QoS . No T1's, ATM, Frame, etc. just Ethernet IP.
Thanks
Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070509/ecdfe868/attachment-0001.html
------------------------------
Message: 3
Date: Wed, 9 May 2007 19:44:32 -0400
From: "Jason Aarons \(US\)" <jason.aarons at us.didata.com>
Subject: [cisco-voip] IOS strip digits from 8 to 4
To: <cisco-voip at puck.nether.net>
Message-ID:
<C1FE15183DA37645BC0633BC604E44F00586BF11 at USNAEXCH.na.didata.local>
Content-Type: text/plain; charset="us-ascii"
Telco is delivering 8 digits in Malaysia, I only need 4 digits
significant. I don't want to ask them to change from 8 digits to 4.
This is all h323 dial-peers, some DIDs go to CallManager, some DIDs go
to CVP, etc. I can't use MGCP or do a translation-pattern in CCM.
How best should I reduce the 8 digits received to 4 via IOS Gateway?
DID Range 8808-87XX
num-exp 880887.. ....
Jason Aarons
Consultant
http://www.dimensiondata.com/na <http://www.dimensiondata.com/na>
904-338-3245 cell
For urgent issues notify your Project Manager, for 24x7 support contact
the Dimension Data NOC at 800-974-6584.
-----------------------------------------
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/20070509/3f9dcfd7/attachment-0001.html
------------------------------
Message: 4
Date: Wed, 9 May 2007 19:55:39 -0400
From: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Subject: Re: [cisco-voip] Area Code vs NXX Conflict
To: "Jason Aarons \(US\)" <jason.aarons at us.didata.com>, "Walt Moody"
<moody at arizona.edu>, <cisco-voip at puck.nether.net>
Message-ID: <002a01c79295$8d9d7f00$47196883 at cfs.uoguelph.ca>
Content-Type: text/plain; charset="iso-8859-1"
I use this for this sort of stuff....
http://www.localcallingguide.com/
--------------------------------------------------------------------------------
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: Jason Aarons (US)
To: Walt Moody ; cisco-voip at puck.nether.net
Sent: Wednesday, May 09, 2007 5:42 PM
Subject: Re: [cisco-voip] Area Code vs NXX Conflict
You would have to get a list of NPA-XXXs for that CO and expand the
route pattern. I've done this for TEHO (Tail End Hop Off) routing,
Atlanta had hundreds of NPA-XXXs...headache to keep up with..
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Walt Moody
Sent: Wednesday, May 09, 2007 4:19 PM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Area Code vs NXX Conflict
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
>
>
_______________________________________________
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.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070509/b44f2aa7/attachment.html
------------------------------
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
End of cisco-voip Digest, Vol 51, Issue 59
******************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070509/f3683514/attachment-0001.html
More information about the cisco-voip
mailing list