AudioCodes Mediant 4000 SBC, User Manual

Page: 280 / 1037

CHAPTER 16 Services
Mediant 4000 SBC | User's Manual
Assigning Cost Groups to Routing Rules
To use your configured Cost Groups, you need to assign them to routing rules:
■ SBC application: IP-to-IP Routing table - see Configuring SBC IP-to-IP Routing on page 545
Remote Web Services
This section describes configuration for remote Web services.
To debug remote Web services, see Debugging Web Services .
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 .
■ 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 . 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.
● Configuration Status: Status is reported when IP 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.
■ QoS: Call routing based on QoS. For more information, see Configuring QoS-Based Routing
by Routing Server .
■ General: This service type can be used for the following services:
● Generating and sending CDRs to a REST server through REST API. The REST server is
configured as an HTTP-based server (Remote Web Service). For more information, see
Configuring CDR Reporting to REST Server on page 765.
● Querying (GET) HTTP servers using Call Setup Rules. The response from the server can
be used for various functionality such as tag-based classification and routing. When
configuring the Call Setup Rule, you need to configure the 'Request Target' parameter to
the name of this Remote Web Service. For more information on Call Setup Rules, see
Configuring Call Setup Rules on page 452.
- 247 -