AudioCodes Mediant 3000 User Manual page 285

User's Manual
The device also allows the routing server to manipulate call data such as calling name, if
required. The routing server may also create new IP Groups and associated configuration
entities if it deems necessary for routing.
Multiple routing servers can also be employed, whereby each device in the chain path can
use a specific routing server. Alternatively, a single routing server can be employed and
used for all devices ("stateful" routing server).
Communication between the device and the routing server is through the device's
embedded Representational State Transfer (RESTful) API. The RESTful API is used to
manage the routing-related information that is exchanged between the routing server
(RESTful server) and the device (RESTful client). When the connection settings of the
routing sever is configured on the device and the device starts-up, it connects to the routing
server and activates the RESTful API, which triggers the routing-related API commands.
The following figure provides an example of information exchange between devices and a
routing server for routing calls:
Figure 16-29: Example of Call Routing Information Exchange between Devices and Routing
The device automatically updates (sends) the routing server of its' configuration topology
regarding SIP routing-related entities (such as SRDs, SIP Interfaces, and IP Groups) that
have been configured for use by the routing server. To enable their use by the routing
server, you must configure the 'Used By Routing Server' parameter to Used for each
configuration entity. For example, if you add a new SRD and enable it for use by the
routing server, the device sends this information to the routing server. Routing of calls
pertaining to routing-related entities that are disabled for use by the routing server (default)
are handled only by the device (not the routing server).
In addition to regular routing, the routing server functionality also supports the following:

Alternative Routing: If a call fails to be established, the device "closest" to the failure
and configured to send "additional" routing requests (through the REST API) to the
routing server, sends a new routing request to the routing server. The routing server
may respond with a new route destination, thereby implementing alternative routing.
Alternatively, it may enable the device to return a failure response to the previous
device in the route path chain and respond with an alternative route to this device.
Version 7.0
Server
285
16. Services
Mediant 3000