AudioCodes Mediant 3000 User Manual page 286

Therefore, alternative routing can be implemented at any point in the route path.

Call status: The device can report call status to the routing server to indicate whether
a call has successfully been established and/or failed (disconnected). The device can
also report when an IP Group (Proxy Set) is unavailable, detected by the keep-alive
mechanism, or when the CAC thresholds permitted per IP Group have been crossed.
For Trunk Groups, the device reports when the trunk's physical state indicates that the
trunk is unavailable.
In addition to setting the 'Used By Routing Server' parameter to Used for configuration
entities, the following configuration is required:

An additional Security Administrator user account, configured in the Web Users table
(''Configuring Web User Accounts'' on page 82). This user account is used by the
routing server (REST client) to log in to the device's management interface.

Define the address and connection settings of the routing server (referred to as an
HTTP remote service) (referred to as remote hosts).

SBC Calls: In the IP-to-IP Routing table, the 'Destination Type' parameter must be
configured to Routing Server (see Configuring SBC IP-to-IP Routing Rules on page
603). If the incoming call matches the rule's input characteristics, the device requests
an appropriate destination from the routing server.

Gateway Calls:
•
Tel-to-IP Calls: In the Tel-to-IP Routing table, the 'Destination IP Address'
parameter must be configured to "REST" (see Configuring Tel-to-IP Routing
Rules on page 496). If the incoming call matches the rule's input characteristics,
the device requests an appropriate destination from the routing server.
•
IP-to-Tel Calls: The routing server manipulates the Request-URI header that is
sent to the device in the SIP message. The manipulation allows routing based on
the SDP 'tgrp' attribute (per RFC 4904). The 'tgrp' attribute specifies the Trunk
Group to where the device must route the call. The attribute is added to the
Request-URI in the outgoing INVITE message of the previous device in the chain.
For example, the device receives an INVITE, already manipulated by the routing
server for the previous device in the chain, indicating Trunk Group 66:
INVITE sip:+16305550100;tgrp=PBX-66;trunk-
context=example.com@10.1.0.3;user=phone SIP/2.0
User's Manual
To enable the use of the 'tgrp' attribute, use the UseSIPtgrp parameter.
286
Mediant 3000
Document #: LTRT-89730