09-19-2023 04:35 PM
I have these 4 dial peers and trying to get specific numbers to take a different peer but number keeps getting matched with wild card peers, 4002 and 5000. Instead of the more specific e164 peers 80057 & 800.
Example:
dial-peer voice 4002 voip
rtp payload-type comfort-noise 13
session protocol sipv2
incoming uri via pstn
voice-class codec 1
voice-class sip early-offer forced
voice-class sip tenant 900
dtmf-relay rtp-nte
no vad
dial-peer voice 5000 voip
description outbound to CUCM
destination-pattern +...........$
session protocol sipv2
session server-group 100
voice-class codec 1
voice-class sip early-offer forced
voice-class sip tenant 500
dtmf-relay sip-kpml rtp-nte
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711ulaw
no vad
dial-peer voice 80057 voip
no modem passthrough
session protocol sipv2
session server-group 100
destination e164-pattern-map 100
voice-class codec 2 offer-all
voice-class sip tenant 500
voice-class sip pass-thru content sdp
dtmf-relay rtp-nte
fax-relay ecm disable
fax-relay sg3-to-g3
fax protocol t38 version 0 ls-redundancy 2 hs-redundancy 0 fallback pass-through g711ulaw
no vad
dial-peer voice 800 voip
no modem passthrough
session protocol sipv2
incoming uri via pstn
incoming called e164-pattern-map 100
voice-class codec 2 offer-all
voice-class sip tenant 900
voice-class sip pass-thru content sdp
dtmf-relay rtp-nte
fax-relay ecm disable
fax-relay sg3-to-g3
fax protocol t38 version 0 ls-redundancy 2 hs-redundancy 0 fallback pass-through g711ulaw
no vad
09-19-2023 08:01 PM
The gateway moves on to the next criteria only if no match is found. Apparently destination-pattern has higher preference than e164-pattern-map.
Table 4. Outbound SIP Dial-Peer Selection Preference
Preference |
Match Criteria |
Dial-peer Commands |
1 |
Dial-Peer Group Dial-Peer |
destination dpg <dpg-tag> (DPG configured on inbound dial-peer) |
2 |
Dial-Peer Provision Policy URI |
destination uri-from <uri-tag> (DPP configured on inbound dial-peer) |
3 |
ILS Route String |
destination route-string <route-string-tag> |
4 |
URI and Carrier-ID |
destination uri <uri-tag> AND carrier-id target <string> |
5 |
Called Number and Carrier-ID |
destination-pattern <number-string> AND carrier-id target <string> |
6 |
URI |
destination uri <uri-tag> |
7 |
Called Number |
destination-pattern <DNIS-number> destination e164-pattern-map <pattern-map-number> dnis-map <dnis-map-number> |
8 |
Calling Number |
destination calling e164-pattern-map <pattern-map-number> |
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide