CHAPTER25 Routing
Mediant 1000 Gateway & E-SBC | User's Manual
■ 806 Media Limits Exceeded: The device generates Release Cause Code 806 when the call
is terminated due to crossed thresholds of QoE metrics such as MOS, packet delay, and
packet loss (configured in the Quality of Experience Profile table - see Configuring Quality of
Experience Profiles on page302) and/or media bandwidth (configured in the Bandwidth profile
table - see Configuring Bandwidth Profiles on page307). When this occurs, the device sends a
SIP 480 (Temporarily Unavailable) response to the SIP entity. When the threshold is crossed,
the device maintains the existing call and applies alternative routing only to subsequent calls.
To configure alternative routing based on Release Cause 806, do the following :
a. Assign an IP Group with a QoE and/or Bandwidth profile that rejects calls if the threshold
is crossed.
b. Configure Release Cause Code 806 in the Reasons for Tel-to-IP Alternative Routing table.
c. Configure an alternative routing rule.
The device always routes at least two calls to the destination that has crossed the threshold,
so that it can continue measuring QoE / bandwidth. When the threshold drops below the con-
figured QoE / bandwidth threshold (i.e., good QoE), the device stops using the alternative rout-
ing rule and starts routing the calls using the initial routing rule.
● You can also enable the Busy Out feature, whereby the device can take specified
actions if all Proxy Sets of associated destination IP Groups of matching routing
rules in the Tel-to-IP Routing table do not respond to connectivity checks. For more
information, see the EnableBusyOut parameter.
● If the AltRoutingTel2IPEnable parameter is enabled for the IP Connectivity feature
(see Alternative Routing Based on IP Connectivity), the Busy Out feature does not
function with the Proxy Set keep-alive mechanism (see below). To use the Busy
Out feature with the Proxy Set keep-alive mechanism (for IP Groups), disable the
AltRoutingTel2IPEnable parameter.
● The device also plays a tone to the endpoint whenever an alternative route is used.
This tone is played for a user-defined time, configured by the
AltRoutingToneDuration parameter
Depending on configuration, alternative routing is done using one of the following configuration
entities:
■ Tel-to-IP Routing Rules: Alternative routing rules can be configured for a specific routing rule
in the Tel-to-IP Routing table. If the destination of the "main" routing rule is unavailable, the
device searches the table for the next matching rule (e.g., destination phone number), and if
available attempts to re-route the call to the IP destination configured for this alternative routing
rule. For more information on configuring alternative Tel-to-IP routing rules, see Configuring
Tel-to-IP Routing Rules. The table below shows an example of alternative routing where the
device uses the first available alternative routing rule to re-route the initial, unsuccessful Tel-to-
IP call destination.
Table 25-7: Alternative Routing based on SIP Response Code Example
Destination Phone
Prefix
IP
Destination
SIP Response
Rule
Used?
Main Route 40 10.33.45.68 408 Request
Timeout
No
Alternative
Route #1
40 10.33.45.70 486 Busy Here No
Alternative
Route #2
40 10.33.45.72 200 OK Yes
- 604 -
To Next Page
Loading...
Need help?
General
