AudioCodes Mediant 4000 SBC User Manual page 500


According to result of an ENUM query.

Hunt Group - used for call survivability of call centers (see ''Configuring Call
Survivability for Call Centers'' on page 581).

According to result of LDAP query (for more information on LDAP-based routing, see
''Routing Based on LDAP Active Directory Queries'' on page 237).

Third-party routing server, which determines the destination (next hop) of the call (IP
Group). The IP Group represents the next device in the routing path to the final
destination. For more information, see ''Centralized Third-Party Routing Server'' on
page 278.

Back to the sender of the incoming message, where the reply can be a SIP response
code or a 3xx redirect response (with an optional Contact field to where the sender
must re-send the message).
The following figure summarizes the destination types:
To configure and apply an IP-to-IP Routing rule, the rule must be associated with a Routing
Policy. The Routing Policy associates the routing rule with an SRD(s). Therefore, the
Routing Policy lets you configure routing rules for calls belonging to specific SRD(s).
However, as multiple Routing Policies are relevant only for multi-tenant deployments (if
needed), for most deployments, only a single Routing Policy is required. As the device
provides a default Routing Policy ("Default_SBCRoutingPolicy"), when only one Routing
Policy is required, the device automatically assigns the default Routing Policy to the routing
rule. If you are implementing LDAP-based routing (with or without Call Setup Rules) and/or
Least Cost Routing (LCR), you need to configure these settings for the Routing Policy
User's Manual
Figure 25-4: IP-to-IP Routing Destination Types
500
Mediant 4000 SBC
Document #: LTRT-40203