matthnick at gmail
May 18, 2012, 9:26 AM
Post #4 of 4
(408 views)
Permalink
|
|
Re: Matich dial-peers on trunk group or caller id
[In reply to]
|
|
A few notes:
-If you want to use answer address make sure you're not using incoming
called-number or you'll never match it. 'incoming called-number .' is
generally the format used, which would block the algorithm from ever
checking caller-id.
-Another approach is corlists. Configure the corlists so the only
outbound dial peer that can be used is the chosen trunk. Little
complicated, not my favorite.
-What easier is matching based on port or caller-id, depending on
existing configuration complexity, and then applying a inbound
translation to add a tag, and then outbound dial peers that strip the
tag to the desired trunks.
-nick
On Fri, May 18, 2012 at 10:16 AM, Ted Nugent <tednugent73 [at] gmail> wrote:
> You could also match on incoming called-number on the inbound pots dialpeer,
> then use translation profiles to prefix something that will match your
> outbound dialpeers for the outbound trunkgroup.
>
> dial-peer voice 200 pots
> incoming called-number 91955512..
> direct-inward-dial
> translation-profile incoming AddInboundPrefix
> trunkgroup PRI1
>
>
>
> On Thu, May 17, 2012 at 3:35 PM, Joseph Mays <mays [at] win> wrote:
>>
>> I want to route all incoming calls from a particular trunk to be outgoing
>> calls on another specific trunk group. Is there any way, in a dial-peer
>> entry, to match on caller ID or incoming trunk group, rather than
>> destination-pattern?
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip [at] puck
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip
|
