[cisco-voip] calls using the wrong dial peer

Justin Steinberg jsteinberg at gmail.com
Thu May 7 16:17:59 EDT 2009


dont ask me why, but i'm pretty sure you can not use a voice-port for
inbound pots dial-peer matching on the as5400.  it's going to match on the
incoming called-number first, then answer-address.

what are you trying to accomplish?  perhaps there is another way to achieve
the same result.



On Thu, May 7, 2009 at 3:26 PM, Jeremy Rogers <Jeremy.Rogers at ip-soft.net>wrote:

>  I am attempting to make changes to some call routing on an AS5400.
> Currently I have a pots dial peer set for each PRI port the gateway.  The
> change I am making requires the calls coming in that port to hit that dial
> peer, however upon reviewing traces I see that the calls are hitting the
> first available POTS dial peer even though it is assigned to a different
> port.
>
> Without getting too explicit for the inbound pattern, what can I do to
> force the calls to use that dial peer?
>
>
>
> Current dial peer setup
>
> This is the dial peer for the port that the calls come in on:
>
> dial-peer voice 117 pots
>
>  answer-address .T
>
>  incoming called-number .T
>
>  direct-inward-dial
>
>  port 1/0:27:D
>
>
>
> However, this is the dial peer that all the calls are hitting and I believe
> its because it comes first in the config
>
>
>
> dial-peer voice 111 pots
>
> answer-address .T
>
>  incoming called-number .T
>
>  direct-inward-dial
>
>  port 1/0:1:D
>
>
>
> Jeremy Rogers
>
> Network Management
>
>
>
> _______________________________________________
> 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/20090507/fd5902b3/attachment.html>


More information about the cisco-voip mailing list