User's Manual 294 Document #: LTRT-10632
Mediant 800B Gateway & E-SBC
Parameter Description
addresses has not changed. If a change is detected, the
device updates its' list of IP addresses and re-establishes
connections accordingly.
In addition to multiple HTTP sessions, the device
establishes multiple (TCP) connections per session, thereby
enhancing data exchange capabilities with the host.
Port
rest-port
[HTTPRemoteHosts_Port]
Defines the port of the host.
The valid value is 0 to 65535. The default is 80.
Interface
rest-interface
[HTTPRemoteHosts_Interface]
Assigns one of the device's IP network interfaces through
which communication with the remote host is done.
By default, no value is defined and the OAMP interface is used.
Transport Type
rest-transport-type
[HTTPRemoteHosts_HTTPTransportType]
Defines the protocol for communicating with the remote host:
[0] HTTP (default)
[1] HTTPS
Status
http-host-state
(Read-only) Displays the status of the connection with the
remote host.
"Connected": The hosts is connected.
"Disconnected": The host is disconnected.
"Not In Service": Configuration of the host is invalid.
15.6.2 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' on page
288.
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:
Figure 15-45: Enabling Topology Status Web-based Service
3. Click Apply.
15.6.3 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, and Tel-to-IP Routing table and IP-
to-Tel Routing table for Tel-to-IP and IP-to-Tel calls respectively) 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 that is also configured to use a
Routing server. If found, the device requests the Routing server for an appropriate destination.
For Gateway calls: When the device receives an incoming call (SIP INVITE, NOTIFY or
MESSAGE), it disregards the routing tables and instead immediately requests the Routing server
To Next Page
Loading...
