/mcpMMOIP Multimedia Mail Over IP dial-peers are utilized to send emails to exchange servers. These are mostly utilized for t37 on-ramp / off-ramp faxing. These dial-peer types are not within the scope of this document.
Note: The maximum number of dial-peers that can be configured on a Cisco gateway depends on the available memory (DRAM). Each dial-peer consumes approximately 6KB of memory, so ensure that the gateway has at least 20% of the total memory reserved for other CPU processes. A large number of configured dial-peers can add to the delay to route a call. This can be significant as the Cisco voice application looks through dial-peers from the top down, similar to an Access Control List (ACL). This is usually not a problem on newer Cisco Gateways. Sample Error:
May 26 12:59:46.406: %DIALPEER_DB-3-ADDPEER_MEM_THRESHOLD: Addition of dial-peers limited by available m
Inbound Dial-Peer Matching When a Cisco Gateway receives a call setup request, the gateway begins searching for an applicable incoming dial-peer for this call. This is not a digit-by-digit analysis; rather, the full message is utilized to determine which inbound dial-peer is selected. The order of items in the message checked is largely dependent on the protocol for the call as indicated by the preference lists defined in Table 1, Table 2, and Table 3. A dial-peer only needs to satisfy one of the conditions for matching. It is not necessary for all the attributes to be configured in the dial-peer or that every attribute match the call setup information. All dial-peers are searched based on the first match criteria. The gateway moves on to the next criteria only if no match is found. Table 1. Inbound SIP Dial-Peer Selection Preference Preference Match Criteria Dial-peer Commands 1 URI incoming uri via <uri-tag> 2 URI incoming uri request <uri-tag> 3 URI incoming uri to <uri-tag> 4 URI incoming uri from <uri-tag> incoming called-number <number-string> 5 Called Number