AudioCodes Mediant 4000 SBC, User Manual

Page: 602 / 1037

CHAPTER 25 Routing SBC
Mediant 4000 SBC | User's Manual
■ Enables Least Cost Routing (LCR), and configures default call cost (highest or lowest) and
average call duration for routing rules that are not assigned LCR Cost Groups. The default call
cost determines whether matched routing rules that are not assigned Cost Groups are
considered as a higher or lower cost route compared to other matching routing rules that are
assigned Cost Groups. If you disable LCR, the device ignores the Cost Groups assigned to the
routing rules in the IP-to-IP Routing table.
■ Assigns LDAP servers (LDAP Server Group) for LDAP-based routing. IP-to-IP routing rules
configured for LDAP or CSR (Call Setup Rules) queries use the LDAP server(s) that is
assigned to the routing rule's associated Routing Policy. You can configure a Routing Policy
per SRD or alternatively, configure a single Routing Policy that is shared between all SRDs.
The implementation of Routing Policies is intended for the following deployments only :
■ Deployments requiring LCR and/or LDAP-based routing.
■ Multi-tenant deployments that require multiple, logical routing tables where each tenant has its
own dedicated ("separated") routing (and manipulation) table. In such scenarios, each SRD
(tenant) is configured as an Isolated SRD and assigned its own unique Routing Policy,
implementing an almost isolated, non-bleeding routing configuration topology.
For all other deployment scenarios, the Routing Policy is irrelevant and the handling of the
configuration entity is not required as a default Routing Policy ("Default_SBCRoutingPolicy" at
Index 0) is provided. When only one Routing Policy is required, the device automatically associates
the default Routing Policy with newly added configuration entities that can be associated with the
Routing Policy (as mentioned later in this section, except for Classification rules). This facilitates
configuration, eliminating the need to handle the Routing Policy configuration entity (except if you
need to enable LCR and/or assign an LDAP server to the Routing Policy). In such a setup, where
only one Routing Policy is used, single routing and manipulation tables are employed for all SRDs.
If possible, it is recommended to use only one Routing Policy for all SRDs (tenants),
unless deployment requires otherwise (i.e., a dedicated Routing Policy per SRD).
Once configured, you need to associate the Routing Policy with an SRD(s) in the SRDs table. To
determine the routing and manipulation rules for the SRD, you need to assign the Routing Policy to
routing and manipulation rules. The figure below shows the configuration entities to which Routing
Policies can be assigned:
Typically, assigning a Routing Policy to a Classification rule is not required, as when an incoming
call is classified it uses the Routing Policy associated with the SRD to which it belongs. However,
if a Routing Policy is assigned to a Classification rule, it overrides the Routing Policy assigned to
the SRD. The option to assign Routing Policies to Classification rules is useful in deployments
requiring different routing and manipulation rules for specific calls pertaining to the
same SRD. In
such scenarios, you need to configure multiple Classification rules for the same SRD, where for
some rules no Routing Policy is assigned (i.e., the SRD's assigned Routing Policy is used) while
for others a different Routing Policy is specified to override the SRD's assigned Routing Policy.
In multi-tenant environments employing multiple SRDs and Routing Policies, the IP Groups that
can be used in routing rules (in the IP-to-IP Routing table) are as follows:
- 569 -