[cisco-voip] Num expands

Wed Nov 30 09:10:46 EST 2011

I'll have to read up on the limit of translation rules in v15. Last I checked it was 15, which was not scalable by any means. I'll post the limit and link to the documentation if I find it. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 

----- Original Message -----
From: "Nick Matthews" <matthnick at gmail.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "Dennis Heim" <Dennis.Heim at cdw.com>, "Cisco VoIPoE List" <cisco-voip at puck.nether.net>, "Chris Martin" <clm.ccie at gmail.com> 
Sent: Wednesday, November 30, 2011 8:40:17 AM 
Subject: Re: [cisco-voip] Num expands 

When you type bad characters into the command line, the error prompt 
says you can. I wasn't able to get ^ to work but I didn't try too 
terribly hard. 

In the latest IOS (I'm thinking 15(2)T) they greatly increased the 
amount of translation rules you can have, so that ban has been lifted 
after 10 something years. There's a limit on num-exp too, but I think 
it's in the realm of 512 entries. 

-nick 

On Tue, Nov 29, 2011 at 10:26 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote: 
> This is an interesting thread. I used numexp for the simple reason that 
> translation rules, etc have a limited number of entries available. I was 
> aware that they were captured both on the in/out but not midstream. I only 
> use them during SRST so I don't think we're too exposed. Will have to 
> re-evaluate when I have a bit more time. 
> 
> Can numexp use both ^ and $ so it doesn't capture midstream? 
> 
> --- 
> Lelio Fulgenzi, B.A. 
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
> (519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
> Cooking with unix is easy. You just sed it and forget it. 
> - LFJ (with apologies to Mr. Popeil) 
> 
> 
> ________________________________ 
> From: "Dennis Heim" <Dennis.Heim at cdw.com> 
> To: "Nick Matthews" <matthnick at gmail.com>, "Chris Martin" 
> <clm.ccie at gmail.com> 
> Cc: "Cisco VoIPoE List" <cisco-voip at puck.nether.net> 
> Sent: Tuesday, November 29, 2011 12:55:48 AM 
> Subject: Re: [cisco-voip] Num expands 
> 
> Num-exp will eventually bite you in the arse. Any time saved now will be 
> insanely painful down the road or if you are lucky you will be employed 
> somewhere else when it comes time to payback the Cisco gods. 
> 
> Dennis Heim 
> Senior Engineer (Unified Communications) 
> CDW Advanced Technology Services 
> 10610 9th Place 
> Bellevue, WA 98004 
> 
> 425.310.5299 Single Number Reach (WA) 
> 317.569.4255 Single Number Reach (IN) 
> 317.569.4201 Fax 
> dennis.heim at cdw.com 
> cdw.com/content/solutions/unified-communications/ 
> 
> 
> -----Original Message----- 
> From: cisco-voip-bounces at puck.nether.net 
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nick Matthews 
> Sent: Monday, November 28, 2011 7:27 PM 
> To: Chris Martin 
> Cc: Cisco VoIPoE List 
> Subject: Re: [cisco-voip] Num expands 
> 
> Agree. Num-exp is one of the easiest ways to create a totally messy dial 
> plan. You can use the $ terminator in the num-exp string if you find no 
> other way around it. 
> 
> -nick 
> 
> On Tue, Nov 22, 2011 at 3:04 PM, Chris Martin <clm.ccie at gmail.com> wrote: 
>> Num expansion is bi-directorial and will replace digits mid stream if 
>> it has a match, just like you are reporting. I would create a voice 
>> translation rule and apply to either an incoming dial-peer or on your 
>> voice-port. 
>> 
>> IE: 
>> 
>> voice translation-rule 9000 
>> rule 1 /^9...$/ /55\0/ 
>> ! 
>> voice translation-profile 9000 
>> translate called 9000 
>> ! 
>> voice-port 0/0/0:23 
>> translation-profile incoming 9000 
>> 
>> This matches on anything incoming on an incoming called number with 9 
>> and 3 extra digits then prefixes 55. ie: 9001 = 559001. 
>> 
>> HTH, 
>> Chris 
>> 
>> On Tue, Nov 22, 2011 at 1:30 PM, Mike King <me at mpking.com> wrote: 
>>> 
>>> I have a site that has been given the number block ending in 9XXX. 
>>> Trypically we've only been taking in 4 digits from telco. 
>>> I set a num expand like this: 
>>> 9... 559... 
>>> we have extensions in the 5591XX thru 5599XX. 
>>> However, I have issues with outbound calls completing. My Maintenance 
>>> provider is saying that it was catching anyting (outbound calls as 
>>> well) and appending 559 to it. 
>>> example 
>>> 919781234567 becomes 95599781234567 
>>> 
>>> Suggestions? 
>>> I guess I could contact telco and change it up to 5 digits, but I'm 
>>> wondering if there is a different way to setup the num expands so it 
>>> does more what I want. 
>>> Mike 
>>> _______________________________________________ 
>>> cisco-voip mailing list 
>>> 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 
>> 
>> 
> 
> _______________________________________________ 
> cisco-voip mailing list 
> 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 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111130/46ab9737/attachment.html>