[cisco-nas] 7 / 10 digit matching

Darryl Sladden (dsladden) dsladden at cisco.com
Thu Mar 7 05:57:46 EST 2013


T at end of destination patterns 

Regards,
Darryl Sladden

Sent from my iPhone

On Mar 7, 2013, at 11:00 AM, "Michael Tague" <tague at win.net> wrote:

> Hi,
> 
> We are in the US and are trying to make outbound 7 & 10 digit dialing work
> correctly on a Cisco 2400 IAD.   For a while we have been using outbound
> dial-peers with the following destination patterns:
> 
> #11    destination-pattern [2-9]11        (911, 411, etc)
> #12    destination-pattern [2-9]......    (7 digit dialing)
> #13   destination-pattern 1..........    (1+ long distance dialing)
> #14   destination-pattern 011T        (011 International calling)
> 
> They work well.   Specifically, if you dial a local 7 digit number, it will
> immediately match and make the call, or, if you dial 1+10 digits (for Long
> Distance), it too will match as soon as the last digit (the 11th) is dialed.
> 
> However, in our area, some are used to dialing a ten digit number, area-code
> + 7 digit number.   We would like to make that work.   At first I added two
> dial-peers with these destination patterns (note: 502 and 812 are local area
> codes):
> 
> #15    destination-pattern 502[2-9]......
> #16   destination-pattern 812[2-9]......
> 
> thinking that the explicit 502 and 812 prefixes would favor dial-peers #15
> and #16 over #12, but that didn't happen.  Instead, as soon as the dialer
> hits the 7th digit, dial-peer #12 kicks in and a bad number is dialed.
> 
> I looked at Reg-Ex on the destination-pattern string, but couldn't see an
> how to exclude 502 or 812.
> 
> Anyone on the list have some wisdom on this?
> 
> We wound up using these patterns:
> 
> #102  destination-pattern [^0158]......
> #104  destination-pattern 502[2-9]......
> #106  destination-pattern 50[^2]....
> #108  destination-pattern 5[^0].....
> #110  destination-pattern 812[2-9]......
> #112  destination-pattern 81[^2]....
> #114  destination-pattern 8[^1].....
> 
> which work but make what we are doing rather obscure.   Any suggestions?
> 
> Thanks,
> Michael
> tague at win.net
> 
> _______________________________________________
> cisco-nas mailing list
> cisco-nas at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas



More information about the cisco-nas mailing list