Re: Block using the less mached dial-peer in case the more

I think adding 'huntstop' to dial-peer 100 may prevent this. It will
match 9059 first for longer match (provided the digits come en-bloc),
and if that fails for whatever reason it won't fall back to dial-peer
1.

If you're dialing digit-by-digit from a FXS port with an analog phone
you would need to employ corlists.

-nick

On Thu, Aug 20, 2009 at 9:11 AM, Nathan Richie<nathanr_at_boice.net> wrote:
> I would look at creating a translation for 9059......... into something different such as 8059......... and creating a dial peer just for it......
>
> ________________________________________
> From: nobody_at_groupstudy.com [nobody_at_groupstudy.com] On Behalf Of CCIE [ccie_at_axizo.com]
> Sent: Thursday, August 20, 2009 5:16 AM
> To: ccielab_at_groupstudy.com
> Subject: Block using the less mached dial-peer in case the more matched dial-peer is busy
>
> Hi Experts,
>
>
>
> I have the following dial-peers, I don't want to us dial-peer 1 to call
> 9059....... if dial-peer 100 in use, i.e. block 9059... from using dial-peer
> 1.
>
>
>
> dial-peer voice 1 pots
>
> destination-pattern 9.T
>
> port 0/3/0
>
>
>
> dial-peer voice 100 pots
>
> destination-pattern 9059.......
>
> port 0/3/2
>
>
> Regards,
>
> Amin
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Thu Aug 20 2009 - 18:46:34 ART