Accepted Solutions
The preference has not the highest value when selecting the dial peer. In your specific case as you have overlap between the two dial peers, which in itself is a seriously bad idea to have, you would need to use additional information to define what dial peer to use for what.
For your calls to PSTN don’t you use a breakout code, for example 0 or 9, to have CM send the call to the voice gateway? If so I would recommend you to keep that intact as the call traverse to the gateway from CM and use it in the dial peer and then remove it before sent to the service provider. You could also possibly prefix digits in front of the called number for the calls to the PBX extension, making them not overlap with the dial string used for PSTN calls. This prefix would then be dropped in the dial peer before the call is sent to the PBX.
There are many ways to achieve this, it’s in the end a matter of preference. Again in general it is a very bad idea to have overlaps as it brings so many challenges to the table.
Variable-Length Matching
When matching dial peers, the router defaults to variable-length matching, which means that as long as the left-justified digits in the dial string match the configured pattern in the dial peer, any digits beyond the configured pattern are ignored for the purposes of matching. For example, dial string 5551212 would match both of the following dial peers:
dial-peer voice 1 voip destination-pattern 555 session target ipv4:10.10.1.1 dial-peer voice 2 voip destination-pattern 5551212 session target ipv4:10.10.1.2
To disable variable-length matching for a dial peer, add the dollar sign ($) to the end of the destination pattern, as shown:
dial-peer voice 1 voip destination-pattern 555$ session target ipv4:10.10.1.1
The $ character in the configuration prevents this dial peer from being matched for dial string 5551212 because the extra digits beyond 555 are considered in the matching.
The preference has not the highest value when selecting the dial peer. In your specific case as you have overlap between the two dial peers, which in itself is a seriously bad idea to have, you would need to use additional information to define what dial peer to use for what.
For your calls to PSTN don’t you use a breakout code, for example 0 or 9, to have CM send the call to the voice gateway? If so I would recommend you to keep that intact as the call traverse to the gateway from CM and use it in the dial peer and then remove it before sent to the service provider. You could also possibly prefix digits in front of the called number for the calls to the PBX extension, making them not overlap with the dial string used for PSTN calls. This prefix would then be dropped in the dial peer before the call is sent to the PBX.
There are many ways to achieve this, it’s in the end a matter of preference. Again in general it is a very bad idea to have overlaps as it brings so many challenges to the table.
As @roger mentioned use a specific pattern instead of .T in pots dial-peer or use a prefix to differentiate the calls. Its not a best practice to use such overlapping dial-peer.
For additional details on what I referenced with preference not being the highest value for selection please have a look at this document. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/dialpeer/configuration/15-mt/vd-15-mt-book/vd-dp-feat-cfg.html
