AudioCodes Mediant 500L - Remote Web Services; Configuring Remote Web Services

User's Manual 282 Document #: LTRT-10532
Mediant 500L Gateway & E-SBC
15.6 Remote Web Services
This section describes configuration for remote Web services.
Note: To debug remote Web services, see Debugging Web Services on page 975.
15.6.1 Configuring Remote Web Services
The Remote Web Services table lets you configure up to seven Web-based (HTTP/S)
services provided by third-party, remote HTTP/S hosts. The following types of services can
be offered by the remote host:
 Routing: Call routing service, whereby the remote host (e.g., routing server)
determines the next hop of an incoming call on the path to the final destination. For
more information on employing a third-party, remote routing server, see ''Centralized
Third-Party Routing Server'' on page
289.
 Call Status: Call status of calls processed by the device. The call status is provided to
the remote host through CDRs sent by the device.
 Topology Status: Status of device configuration (add, edit and delete). The device
sends topology status to the HTTP host, using the REST TopologyStatus API
command. To enable the functionality, see ''Enabling Topology Status Services'' on
page
289.
Topology status includes the following:
• IP Group Connectivity: Status is reported when the keep-alive mechanism,
enabled for the associated Proxy Set, detects that the IP Group is unavailable, or
when CAC thresholds (configured in the Admission Control table) associated with
the IP Group are crossed.
• Trunk Group Availability: Status is reported when the trunk's physical state
indicates that the trunk is unavailable.
• Configuration Status: Status is reported when IP Groups, Trunk Groups or SIP
Interfaces that are configured to be used by remote Web-based services (i.e., the
UsedByRoutingServer parameter is set to 1 - Used) are created or deleted. If you
subsequently change the settings of the UsedByRoutingServer parameter or the
'Name' parameter, the device reports the change as a creation or deletion of the
corresponding configuration entity.
 Capture: Recording of signaling and RTP packets, and Syslog. The remote host can
be, for example, a Syslog server or AudioCodes OVOC.
 QoS: Call routing based on QoS. For more information, see Configuring QoS-Based
Routing by Routing Server on page
292.