/mcpPreference Match Criteria Dial-peer Commands 1 URI incoming uri called <uri-tag> incoming uri calling <uri-tag> 2 Called Number incoming called-number <number-string> incoming called e164-pattern-map <pattern-map-number> 3 Calling Number incoming calling e164-pattern-map <pattern-map-number> answer-address <number-string> 4 Destination-pattern (ANI) destination-pattern <number-string> 5 Carrier-ID carrier-id source <string>
Table 3. Inbound Enbloc POTS Dial-Peer Selection Preference Preference Match Criteria Dial-peer Commands 1 Called Number incoming called-number <number-string> 2 Calling Number answer-address <number-string> 3 Destination-pattern (ANI) destination-pattern <number-string> 4 Voice-port port <voice-port-number>
When No Matches Exist / Default Dial-Peer 0 peer_tag=0, pid:0 When there are no eligible matches for an inbound dial-peer for either POTS or VoIP calls, the gateway allocates dial-peer 0. This is not ideal as dial-peer 0 has limited capabilities and can cause issues with calls. The outlier to this is SCCP and MGCP protocols which do not use dial-peers for routing calls. See the MGCP and SCCP section for further details. dial-peer 0 capabilities No dtmf-relay mechanisms. • Advertised all voice codecs for VoIP calls. •