<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br>Just a guess but how about:<br><br>Translation-rule 1<br>rule 1 ..../..../ /..../<br><br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: "cisco-voip-request@puck.nether.net" <cisco-voip-request@puck.nether.net><br>To: cisco-voip@puck.nether.net<br>Sent: Wednesday, May 9, 2007 7:56:06 PM<br>Subject: cisco-voip Digest, Vol 51, Issue 59<br><br><div>Send cisco-voip mailing list submissions to<br> cisco-voip@puck.nether.net<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a target="_blank"
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>or, via email, send a message with subject or body 'help' to<br> cisco-voip-request@puck.nether.net<br><br>You can reach the person managing the list at<br> cisco-voip-owner@puck.nether.net<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of cisco-voip digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Area Code vs NXX Conflict (Jason Aarons (US))<br> 2. VGW + throughput (Voll, Scott)<br> 3. IOS strip digits from 8 to 4 (Jason Aarons (US))<br> 4. Re: Area Code vs NXX Conflict (Lelio Fulgenzi)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 9 May 2007 17:42:41 -0400<br>From: "Jason Aarons \(US\)" <jason.aarons@us.didata.com><br>Subject: Re:
[cisco-voip] Area Code vs NXX Conflict<br>To: "Walt Moody" <moody@arizona.edu>, <cisco-voip@puck.nether.net><br>Message-ID:<br> <C1FE15183DA37645BC0633BC604E44F00586BDF8@USNAEXCH.na.didata.local><br>Content-Type: text/plain; charset="us-ascii"<br><br>You would have to get a list of NPA-XXXs for that CO and expand the<br>route pattern. I've done this for TEHO (Tail End Hop Off) routing,<br>Atlanta had hundreds of NPA-XXXs...headache to keep up with..<br><br>-----Original Message-----<br>From: cisco-voip-bounces@puck.nether.net<br>[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Walt Moody<br>Sent: Wednesday, May 09, 2007 4:19 PM<br>To: cisco-voip@puck.nether.net<br>Subject: Re: [cisco-voip] Area Code vs NXX Conflict<br><br>Brian,<br><br>I'm aware of the potential for future conflicts. Right now, the only<br>conflict is 623. If at some far in the future date we have PRIs in<br>928,
and 928 is in conflict, we'll have to deal with it.<br><br>Lelio,<br><br>Interdigit time outs could be a problem, but the more pressing problem <br>is routes. How do you tell 623[2-9]XXXXXX to go to the PSTN trunks in<br>Phoenix, and 623[2-9]XXX to go to Tucson's PSTN trunks? There doesn't<br>seem to be a way to build a conflict table with different routing for<br>seven digits versus ten.<br><br>-walt<br><br>Brian Prentiss wrote:<br>> The thing is with the first option here, is that potentially you would<br><br>> have a similiar situation with the other area codes at some point, as <br>> the population growth forces more NXX assignments in the 520 area<br>code. <br>> Also, as people wait for that interdigit timeout, they might be<br>thinking <br>> "did it go through?" and that might be a bit of a challenge support<br>wise.<br>> <br>> Are you planning on doing the same with the 928 area code that is in<br>the
<br>> other part of the state?<br>> <br>> Regards,<br>> Brian<br>> <br>> <br>> On 5/9/07, Lelio Fulgenzi <lelio@uoguelph.ca<br><mailto:lelio@uoguelph.ca>> <br>> wrote:<br>> <br>> If you can live with interdigit timeout, then you should be able<br>to<br>> program things so that you can dial either number and get through.<br>> Users will have to wait 10 seconds (or whatever your parameter is<br>> configured for) before 7 digit calls are placed -or- if I'm not<br>> mistaken, they can press # to complete the dialing process (you<br>> might need an extra route pattern with the # at the end though as<br>> well).<br>> <br>> Other than that, if you are looking to be able
to dial a 7 digit<br>and<br>> 10 digit call with the same beginning three digits and not have<br>> interdigit timeout at the end, I do not think you will be able to<br>do<br>> this.<br>> <br>> <br>><br>------------------------------------------------------------------------<br>--------<br>> Lelio Fulgenzi, B.A.<br>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G<br>2W1<br>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>><br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>> ...there's no such thing as a bad timbit...<br>> <br>> ----- Original Message
-----<br>> From: Walt Moody <mailto:moody@arizona.edu><br>> To: cisco-voip@puck.nether.net<br><mailto:cisco-voip@puck.nether.net><br>> Sent: Wednesday, May 09, 2007 2:04 PM<br>> Subject: [cisco-voip] Area Code vs NXX Conflict<br>> <br>> <br>> Here's the setup:<br>> <br>> The University of Arizona - in Tucson - uses seven digit<br>dialing for<br>> both on Campus and off Campus local calls. We do not use 9+<br>or any<br>> other PBX "outside access" codes. NANP long distance
is 1+ 10<br>> digits,<br>> IDDD is 011+.<br>> <br>> Except: When dialing from our Tucson Campus to our Phoenix<br>> Campus, we<br>> dial 602827XXXX. We do not use a "1" or any other prefix<br>digit<br>> to when<br>> we dial a "free" or on-net call.<br>> <br>> Still with me? OK, try this: We want to set up our dial<br>plans<br>> so that<br>> we can use 10 digits to call from the Tucson Campus
to<br>anywhere<br>> in the<br>> Phoenix rate center, which consists of Area Codes 480, 602,<br>and<br>> 623.<br>> That's easy enough to do, except (there's that word again) 623<br>> is both<br>> an Area Code in Phoenix and an NXX in Tucson.<br>> <br>> I need to find a way to tell the difference between, for<br>> example, the<br>> dialed digits (623) 555-1212 and 623-5551 and route the 10<br>digit<br>> "623"<br>> numbers
to our PRIs in Phoenix and the 7 digit "623" numbers<br>to the<br>> local Tucson PRIs.<br>> <br>> Prefix digits are not an option -- there are several PBXs in<br>> addition<br>> to the CallManagers that are part of the University's voice<br>> services,<br>> and no real good way to change them from their current dial<br>plans.<br>> <br>> Ideas, anyone?<br>> <br>> Thanks,<br>> <br>> -walt<br>>
_______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net><br>> <a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> <br>> <br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net><br>> <a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>> <br>> <br>_______________________________________________<br>cisco-voip mailing
list<br>cisco-voip@puck.nether.net<br><a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>-----------------------------------------<br>Disclaimer:<br><br>This e-mail communication and any attachments may contain<br>confidential and privileged information and is for use by the<br>designated addressee(s) named above only. If you are not the<br>intended addressee, you are hereby notified that you have received<br>this communication in error and that any use or reproduction of<br>this email or its contents is strictly prohibited and may be<br>unlawful. If you have received this communication in error, please<br>notify us immediately by replying to this message and deleting it<br>from your computer. Thank you.<br><br><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 9 May 2007 15:42:08 -0700<br>From: "Voll, Scott"
<Scott.Voll@wesd.org><br>Subject: [cisco-voip] VGW + throughput<br>To: <cisco-voip@puck.nether.net><br>Message-ID: <407055A92CECCB499C922A2D35FC19A608DEE742@Apollo.wesd.org><br>Content-Type: text/plain; charset="us-ascii"<br><br>What should I expect for Throughput on a ISR VGW. <br><br> <br><br>2801 = ?mb<br><br>2811 = ?mb<br><br>2821 =<br><br>2851 =<br><br>3825 =<br><br> <br><br>Plus they will be doing a couple pots lines and ~8 FXS/FXO ports, and<br>QoS . No T1's, ATM, Frame, etc. just Ethernet IP.<br><br> <br><br>Thanks<br><br> <br><br>Scott<br><br> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a target="_blank" href="https://puck.nether.net/pipermail/cisco-voip/attachments/20070509/ecdfe868/attachment-0001.html">https://puck.nether.net/pipermail/cisco-voip/attachments/20070509/ecdfe868/attachment-0001.html</a>
<br><br>------------------------------<br><br>Message: 3<br>Date: Wed, 9 May 2007 19:44:32 -0400<br>From: "Jason Aarons \(US\)" <jason.aarons@us.didata.com><br>Subject: [cisco-voip] IOS strip digits from 8 to 4<br>To: <cisco-voip@puck.nether.net><br>Message-ID:<br> <C1FE15183DA37645BC0633BC604E44F00586BF11@USNAEXCH.na.didata.local><br>Content-Type: text/plain; charset="us-ascii"<br><br>Telco is delivering 8 digits in Malaysia, I only need 4 digits<br>significant. I don't want to ask them to change from 8 digits to 4.<br><br> <br><br>This is all h323 dial-peers, some DIDs go to CallManager, some DIDs go<br>to CVP, etc. I can't use MGCP or do a translation-pattern in CCM.<br><br> <br><br>How best should I reduce the 8 digits received to 4 via IOS Gateway?<br><br> <br><br>DID Range 8808-87XX<br><br> <br><br>num-exp 880887.. ....<br><br> <br><br> <br><br>Jason Aarons<br><br>Consultant<br><br><a target="_blank"
href="http://www.dimensiondata.com/na">http://www.dimensiondata.com/na</a> <<a target="_blank" href="http://www.dimensiondata.com/na">http://www.dimensiondata.com/na</a>> <br><br>904-338-3245 cell<br><br> <br><br>For urgent issues notify your Project Manager, for 24x7 support contact<br>the Dimension Data NOC at 800-974-6584.<br><br> <br><br><br><br>-----------------------------------------<br>Disclaimer:<br><br>This e-mail communication and any attachments may contain<br>confidential and privileged information and is for use by the<br>designated addressee(s) named above only. If you are not the<br>intended addressee, you are hereby notified that you have received<br>this communication in error and that any use or reproduction of<br>this email or its contents is strictly prohibited and may be<br>unlawful. If you have received this communication in error, please<br>notify us immediately by replying to this message and deleting it<br>from your
computer. Thank you.<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a target="_blank" href="https://puck.nether.net/pipermail/cisco-voip/attachments/20070509/3f9dcfd7/attachment-0001.html">https://puck.nether.net/pipermail/cisco-voip/attachments/20070509/3f9dcfd7/attachment-0001.html</a> <br><br>------------------------------<br><br>Message: 4<br>Date: Wed, 9 May 2007 19:55:39 -0400<br>From: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Subject: Re: [cisco-voip] Area Code vs NXX Conflict<br>To: "Jason Aarons \(US\)" <jason.aarons@us.didata.com>, "Walt Moody"<br> <moody@arizona.edu>, <cisco-voip@puck.nether.net><br>Message-ID: <002a01c79295$8d9d7f00$47196883@cfs.uoguelph.ca><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>I use this for this sort of stuff....<br><br><a target="_blank"
href="http://www.localcallingguide.com/">http://www.localcallingguide.com/</a><br><br>--------------------------------------------------------------------------------<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <br>...there's no such thing as a bad timbit...<br><br> ----- Original Message ----- <br> From: Jason Aarons (US) <br> To: Walt Moody ; cisco-voip@puck.nether.net <br> Sent: Wednesday, May 09, 2007 5:42 PM<br> Subject: Re: [cisco-voip] Area Code vs NXX Conflict<br><br><br> You would have to get a list of NPA-XXXs for that CO and expand the<br> route pattern. I've done this for TEHO (Tail End Hop Off) routing,<br> Atlanta had hundreds of NPA-XXXs...headache to keep up
with..<br><br> -----Original Message-----<br> From: cisco-voip-bounces@puck.nether.net<br> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Walt Moody<br> Sent: Wednesday, May 09, 2007 4:19 PM<br> To: cisco-voip@puck.nether.net<br> Subject: Re: [cisco-voip] Area Code vs NXX Conflict<br><br> Brian,<br><br> I'm aware of the potential for future conflicts. Right now, the only<br> conflict is 623. If at some far in the future date we have PRIs in<br> 928, and 928 is in conflict, we'll have to deal with it.<br><br> Lelio,<br><br> Interdigit time outs could be a problem, but the more pressing problem <br> is routes. How do you tell 623[2-9]XXXXXX to go to the PSTN trunks in<br> Phoenix, and 623[2-9]XXX to go to Tucson's PSTN trunks? There doesn't<br> seem to be a
way to build a conflict table with different routing for<br> seven digits versus ten.<br><br> -walt<br><br> Brian Prentiss wrote:<br> > The thing is with the first option here, is that potentially you would<br><br> > have a similiar situation with the other area codes at some point, as <br> > the population growth forces more NXX assignments in the 520 area<br> code. <br> > Also, as people wait for that interdigit timeout, they might be<br> thinking <br> > "did it go through?" and that might be a bit of a challenge support<br> wise.<br> > <br> > Are you planning on doing the same with the 928 area code that is in<br> the <br> > other part of the state?<br> > <br> > Regards,<br> > Brian<br> >
<br> > <br> > On 5/9/07, Lelio Fulgenzi <lelio@uoguelph.ca<br> <mailto:lelio@uoguelph.ca>> <br> > wrote:<br> > <br> > If you can live with interdigit timeout, then you should be able<br> to<br> > program things so that you can dial either number and get through.<br> > Users will have to wait 10 seconds (or whatever your parameter is<br> > configured for) before 7 digit calls are placed -or- if I'm not<br> > mistaken, they can press # to complete the dialing process (you<br> > might need an extra route pattern with the # at the end though as<br> >
well).<br> > <br> > Other than that, if you are looking to be able to dial a 7 digit<br> and<br> > 10 digit call with the same beginning three digits and not have<br> > interdigit timeout at the end, I do not think you will be able to<br> do<br> > this.<br> > <br> > <br> ><br> ------------------------------------------------------------------------<br> --------<br> > Lelio Fulgenzi, B.A.<br> > Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G<br> 2W1<br> > (519) 824-4120 x56354 (519)
767-1060 FAX (JNHN)<br> ><br> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br> > ...there's no such thing as a bad timbit...<br> > <br> > ----- Original Message -----<br> > From: Walt Moody <mailto:moody@arizona.edu><br> > To: cisco-voip@puck.nether.net<br> <mailto:cisco-voip@puck.nether.net><br> > Sent: Wednesday, May 09, 2007 2:04 PM<br> > Subject: [cisco-voip] Area Code vs NXX Conflict<br> >
<br> > <br> > Here's the setup:<br> > <br> > The University of Arizona - in Tucson - uses seven digit<br> dialing for<br> > both on Campus and off Campus local calls. We do not use 9+<br> or any<br> > other PBX "outside access" codes. NANP long distance is 1+ 10<br> > digits,<br> > IDDD is 011+.<br> > <br> > Except: When dialing from our Tucson Campus to our
Phoenix<br> > Campus, we<br> > dial 602827XXXX. We do not use a "1" or any other prefix<br> digit<br> > to when<br> > we dial a "free" or on-net call.<br> > <br> > Still with me? OK, try this: We want to set up our dial<br> plans<br> > so that<br> > we can use 10 digits to call from the Tucson Campus to<br> anywhere<br> > in the<br> > Phoenix rate center,
which consists of Area Codes 480, 602,<br> and<br> > 623.<br> > That's easy enough to do, except (there's that word again) 623<br> > is both<br> > an Area Code in Phoenix and an NXX in Tucson.<br> > <br> > I need to find a way to tell the difference between, for<br> > example, the<br> > dialed digits (623) 555-1212 and 623-5551 and route the 10<br> digit<br> > "623"<br> > numbers to our
PRIs in Phoenix and the 7 digit "623" numbers<br> to the<br> > local Tucson PRIs.<br> > <br> > Prefix digits are not an option -- there are several PBXs in<br> > addition<br> > to the CallManagers that are part of the University's voice<br> > services,<br> > and no real good way to change them from their current dial<br> plans.<br> > <br> > Ideas, anyone?<br> > <br> > Thanks,<br> >
<br> > -walt<br> > _______________________________________________<br> > cisco-voip mailing list<br> > cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net><br> > <a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br> > <br> > <br> > _______________________________________________<br> > cisco-voip mailing list<br> > cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net><br> > <a
target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br> > <br> > <br> _______________________________________________<br> cisco-voip mailing list<br> cisco-voip@puck.nether.net<br> <a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br> -----------------------------------------<br> Disclaimer:<br><br> This e-mail communication and any attachments may contain<br> confidential and privileged information and is for use by the<br> designated addressee(s) named above only. If you are not the<br> intended addressee, you are hereby notified that you have received<br> this communication in error and that any use or reproduction of<br> this email or its
contents is strictly prohibited and may be<br> unlawful. If you have received this communication in error, please<br> notify us immediately by replying to this message and deleting it<br> from your computer. Thank you.<br><br> _______________________________________________<br> cisco-voip mailing list<br> cisco-voip@puck.nether.net<br> <a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a target="_blank" href="https://puck.nether.net/pipermail/cisco-voip/attachments/20070509/b44f2aa7/attachment.html">https://puck.nether.net/pipermail/cisco-voip/attachments/20070509/b44f2aa7/attachment.html</a> <br><br>------------------------------<br><br>_______________________________________________<br>cisco-voip mailing
list<br>cisco-voip@puck.nether.net<br><a target="_blank" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br><br>End of cisco-voip Digest, Vol 51, Issue 59<br>******************************************<br></div></div><br></div></div></body></html>