dial-peer outbound preference, how to define

[DenysAdams]

Hi All,

i have a case where a client wants all calls except 34xx to have clid restriced
and 34xx to be masked to 3400. its a 200  did range 34xx and 35xx

dial-peer voice 1 pots
destination-pattern 0T
fax rate disable
clid restrict
direct-inward-dial
port 0/2/0:15

dial-peer voice 7 pots
description block caller id
destination-pattern 0T
incoming called-number 434..
fax rate disable
clid network-number 0357543400
direct-inward-dial
port 0/2/0:15

this results in random calls with the mask and no caller id,

the idea was that incoming called-number 434.. in dial-peer voice 7 pots, would give all calls with 434xx priorty and would take priorty over dial-peer voice 1 pots. however that doesnt seem to be the case. i read that incoming called-number takes priorty.

however show dial-peer detail, shows that calls are matching both dial-peers and its using both dial peers.

can anyone clear up the details for me regarding what matching dial patten takes preference. or an alternative.

Regards

[Deepak Rawat]

Refer to below post for understanding the concept of dial peer matching:

http://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/14074-in-dial-peer-match.html

Regards

Deepak

[Muthurani Lavanya Paneerselvam]

Hi Denys,

When matching an outbound dial peer, the Cisco IOS router always uses the destination-pattern
command. In case of outbound dial-peer matching, the following rule applies: called
number based on DNIS matching the outbound dial-peer destination pattern and most
explicit match. Dial-peer routing for POTS is based on the port command and for VoIP is
based on the session target command. In certain cases, two or more dial peers may have
the same destination pattern—for instance, VoIP dial peers to CUCM subscribers for call
processing redundancy. In such a case, the preference command can be added to each
dial peer to set a priority, with preference 0 being the default and highest preference.
Multiple dial peers can be defined with the same destination pattern with preference 1 ,
2 , 3 , and so on.

Regards

Lavanya

[DenysAdams]

Thanks for the responces so far, i have read through the dial peer setup,

how can i have 2 dial peers with each havign the same destination patten differentiate via  the originating calling number. ??

is this possible ?

[Deepak Rawat · Accepted solution]

You have to first determine when you say "destination patten differentiate via  the originating calling" that you will be using this command to match an inbound dial peer or an outbound dial peer. Since the destination-pattern command can be used to match both the dial peers but the usage is dfferent

Dial Peer Additional Information

The dial peer attribute destination-pattern has different behavior when applied to inbound or outbound call legs:

• For inbound dial peers, the destination-pattern is matched against the calling number (ANI string).

• For outbound dial peers, the destination-pattern is matched against called number (DNIS string).

So matching an outbound dial peer using the destination-pattern agains the calling number is not possible. Simply use the preference command as suggested by Lavanya, this will be your best shot in pre deciding which outbound dial peer should be selected using the same destination pattern.

Regards

Deepak