[cisco-voip] calls using the wrong dial peer

[Jeremy Rogers]

Thanks Nick,
Putting it on the voice port itself would probably do the trick.

Jeremy Rogers
Network Management
IPsoft, Inc.
Jeremy.Rogers at ip-soft.net
Phone: 888.IPSOFT8
http://www.ipsoft.com



-----Original Message-----
From: matthn at gmail.com [mailto:matthn at gmail.com] On Behalf Of Nick Matthews
Sent: Thursday, May 07, 2009 5:11 PM
To: Justin Steinberg
Cc: Jeremy Rogers; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] calls using the wrong dial peer

This is basic dial peer matching.

incoming pots:
incoming called number
answer address
destination pattern on ANI
port

If you have incoming called number ., it's going to match on that no
matter what else is applied to the dial peer.  If you have something
like an FXS this can be avoided by putting a station-id on the voice
port and matching that on the answer address, and not using an
incoming called number. To match on the port you can't have any of the
other 3 match.

For a situation with multiple PRIs, where you don't necessarily want
to put a station-id on them, you would have to do any translation on
the voice port itself rather than the dial peers.  Or creatively
leverage some difference in the numbers you dial in or out of the
different PRIs, but this requires more knowledge of what's going on
with the circuits.


-nick




On Thu, May 7, 2009 at 4:17 PM, Justin Steinberg <jsteinberg at gmail.com> wrote:
> 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
>>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>