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

Страница: 253 / 1248

Version 7.2 253 Mediant 500 MSBR
User's Manual 18. Services
Type
rest-message-type
[HTTPRemoteServices_HT
TPType]
Defines the type of service provided by the HTTP remote host:

[0] Routing (default) = Routing service (also includes Call Status
and Topology Status).

[1] Call Status = Call status service.

[2] Topology Status = Topology status service (e.g., change in
configuration).

[3] Capture = Recording of signaling and RTP packets, which can
be sent to a remote host, for example, to a Syslog server or
AudioCodes SEM.

[5] QoS = QoS-based call routing. For more information, see
Configuring QoS-Based Routing by Routing Server on page 260.
Note:

You can configure only one remote Web service for each of the
following service types:
Routing , Call Status , and Topology
Status , and QoS .

For the Topology Status option to be functional, you must enable
the functionality (see Enabling Topology Status Services on page
257).

The Routing option also includes the Call Status and Topology
Status services.

If you do no configure the parameter to QoS , the device sends
QoS reports to the Topology server.

Currently, the Capture option is not supported.
Path
rest-path
[HTTPRemoteServices_Pa
th]
Defines the path (prefix) to the REST APIs.
The valid value is a string of up to 80 characters. The default is "api".
Status
http-service-state
[HTTPRemoteServices_Se
rviceStatus]
(Read-only) Displays the status of the host associated with the Web
service.

"Connected": At least one of the hosts is connected.

"Disconnected": All hosts are disconnected.

"Not In Service": Configuration of the service is invalid.
Connection
Policy
http-policy
[HTTPRemoteServices_Po
licy]
Defines the mode of operation when you have configured multiple
remote hosts (in the HTTP Remote Hosts table) for a specific remote
Web service.

[0] Round Robin = (Default) Load balancing of traffic across all
configured hosts. Every consecutive message is sent to the next
available host.

[1] Sticky Primary = Device always attempts to send traffic to the
first (primary) host. If the host does not respond, the device sends
the traffic to the next available host. If the primary host becomes
available again, the device sends the traffic to the primary host.

[2] Sticky Next = Similar to Sticky Primary , but if the primary host
does not respond, the device sends the traffic to the next available
host and continues sending traffic to this host even if the primary
host becomes available again.