dial-peer POTS matching criteria

[carlo.russo]

Can anyone suggest a solution for this problem.

Is there any way to force a dial-peer to match more than one criteria. I have a situation where an incoming call can be destined for the same destination number, but needs to be routed to different E1 PRI ports depending on from where the call originated.

Ideally if the dial-peer POTS could match based both on dest-number and also considering the originating number, then the best fit peer would always be the desired one.

My testing seems to indicate that the peer matching is on one criteria or the other, does not look at both.

Can anyone suggest a solution, this is causing us lots of problems at the moment.

Regards,

CR.

[Chester Rieman]

Take a look at this:

http://cisco.com/en/US/partner/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml

Please re-post if this does not answer your questions.

[carlo.russo]

Thanks for the reply.

Have seen this document, but reread anyway to be sure. Doc confirms only one of the criteria is matched, not able to match on multiple conditions - "only one condition must be met for the router to select a dial peer. The router stops searching as soon as one dial peer is matched".

It would seem it's not possible to achieve what I'm tyring to do.

Any other suggestions/workarounds?

regards

CR.

[Chester Rieman]

I found one more here:

http://cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a00801c0a88.shtml

This shows using the answer-address command to route by calling number. Hope this helps....