AudioCodes Mediant 4000 SBC, Руководство пользователя

Страница: 288 / 1037

CHAPTER 16 Services
Mediant 4000 SBC | User's Manual
Parameter Description
Note: If you have configured multiple hosts in the group with the
same priority, their priority is determined by their order of appearance
in the table. For example, if two hosts are configured in rows Index 0
and Index 1 with priority 0, the host in Index 0 is considered higher
priority.
Status
'Status' (Read-only) Displays the status of the connection with the remote
host.
■ "Connected": The host is connected.
■ "Disconnected": The host is disconnected.
Enabling Topology Status Services
The following procedure describes how to enable Topology Status for Web-based services. For
more information on Topology Status services, see
Configuring Remote Web Services .
➢
To enable Topology Status services:
1. Open the Web Service Settings page ( Setup menu > IP Network tab > Web Services folder >
Web Service Settings ).
2. From the 'Topology Status' drop-down list (RoutingServerGroupStatus), select Enable :
3. Click Apply .
Centralized Third-Party Routing Server
You can employ a remote, third- party Routing server to handle call routing decisions in
deployments consisting of multiple AudioCodes devices. The Routing server can be used to handle
SBC, Tel-to-IP, and IP-to-Tel calls. Employing a Routing server replaces the need for the device's
routing tables--IP-to-IP Routing table for SBC calls--to determine call destination.
For SBC calls, when the device receives an incoming call (SIP INVITE, NOTIFY or MESSAGE), it
searches the IP-to-IP Routing table for a matching routing rule. If the routing rule is configured to
use a Routing server ('Destination Type' parameter is configured to
Routing Server ), the device
sends a request to the Routing server for an appropriate destination.
The request is sent to the Routing server using an HTTP Get Route message. The request
contains information about the call (SIP message).
The Routing server uses its own algorithms and logic in determining the best route path. The
Routing server manages the call route between devices in "hops", which may be spread over
different geographical locations. The destination to each hop (device) can be by IP address (with
port) or IP Group. If the destination is an IP address, even though the destination type (in the IP-to-
IP Routing table) is an IP Group, the device only uses the IP Group for profiling (i.e., associated IP
Profile etc.). If multiple devices exist in the call routing path, the Routing server sends the IP
address only to the last device ("node") in the path.
- 255 -