Configuring Sip Response Codes For Alternative Routing Reasons - AudioCodes Mediant 800B User Manual

Gateway & e-sbc
Hide thumbs Also See for Mediant 800B:
Table of Contents

Advertisement

User's Manual
Parameter
e]
Call Setup Rules Set ID
call-setup-rules-set-id
[IP2IPRouting_CallSetupRulesSet
Id]
Group Policy
group-policy
[IP2IPRouting_GroupPolicy]
Cost Group
cost-group
[IP2IPRouting_CostGroup]
33.4
Configuring SIP Response Codes for Alternative
Routing Reasons
The Alternative Routing Reasons table lets you configure up to 20 SIP response codes for
call release (termination) reasons. If a call (outgoing SIP dialog-initiating methods, e.g.,
INVITE, OPTIONS, and SUBSCRIBE messages) is released as a result of a configured
SIP code (e.g., SIP 406), the device searches for an alternative routing rule for the call in
the IP-to-IP Routing table (see 'Configuring SBC IP-to-IP Routing Rules' on page 666).
Typically, the device performs alternative routing when there is no response at all to an
INVITE message. This is done after a user-defined number of INVITE re-transmissions,
configured by the SIPMaxRtx parameter. In such a scenario, the device issues itself the
Version 7.2
[1] TCP
[2] TLS
Assigns a Call Setup Rule Set ID to the routing rule. The device
performs the Call Setup rules of this Set ID if the incoming call
matches the characteristics of this routing rule. The device routes
the call to the destination according to the routing rule's
configured action, only after it has performed the Call Setup
rules.
To configure Call Setup rules, see 'Configuring Call Setup Rules'
on page 387.
Defines whether the routing rule includes call forking.
[0] None = (Default) Call uses only this route (even if Forking
Group members are configured in the rows below it).
[1] Forking = Call uses this route and the routes of Forking
Group members, if configured (in the rows below it).
Note: Each Forking Group can contain up to 20 members. In
other words, up to 20 routing rules can be configured for the
same Forking Group.
Assigns a Cost Group to the routing rule for determining the cost
of the call.
By default, no value is defined.
To configure Cost Groups, see 'Configuring Cost Groups' on
page 271.
Note:
To implement LCR and its Cost Groups, you must enable
LCR for the Routing Policy assigned to the routing rule (see
'Configuring SBC Routing Policy Rules' on page 680). If LCR
is disabled, the device ignores the parameter.
The Routing Policy also determines whether matched routing
rules that are not assigned Cost Groups are considered as a
higher or lower cost route compared to matching routing rules
that are assigned Cost Groups. For example, if the 'Default
Call Cost' parameter in the Routing Policy is configured to
Lowest Cost, even if the device locates matching routing
rules that are assigned Cost Groups, the first-matched routing
rule without an assigned Cost Group is considered as the
lowest cost route and thus, chosen as the preferred route.
677
Description
Mediant 800B Gateway & E-SBC
33. Routing SBC

Advertisement

Table of Contents
loading

Table of Contents