Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

dial-peer pots matching criteria

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.

2 REPLIES
Silver

Re: dial-peer pots matching criteria

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

The link tells you how to match a voip dial-peer based on the calling number (answer-address), modify the called number using a translation-rule, and then direct the modified called-number to a particular voice-port of your choice.

New Member

Re: dial-peer pots matching criteria

I have a similar situation that this document describes but it involves an Analog E&M Wink start trunk to a Norstar key system with no local lines on the key system or the 2620. We are trying to push the external PSTN numbers to another site with a 3740 that connects to a Nortel Option 11 to go to the PSTN. Would this type of programming work?

100
Views
0
Helpful
2
Replies
CreatePlease to create content