CHAPTER 16 Services
Mediant 4000 SBC | User's Manual
Parameter
Description
■
[2]
Sticky Next
= The device initially attempts to send
traffic to the host that has the highest priority in the
group. If this host becomes unavailable (or is initially
unavailable), the device sends the traffic to the next
available host that has the highest priority and continues
sending traffic to this host even if the highest-priority host
later becomes available again.
Note:
If you have configured multiple hosts with the same
priority, their priority is determined by their order of
appearance in the HTTP Remote Hosts 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.
'Policy between Groups'
http-policy-between-
groups
[HTTPRemoteServices_
BetweenGroupsPolicy]
Defines the mode of operation between groups of hosts,
which are configured in the HTTP Remote Hosts table for
the specific remote Web service.
■
[1]
Sticky Primary
= (Default) The device always
attempts to send traffic to the group that has the highest
priority (e.g., Group 0). If none of the hosts in this group
respond, the device attempts to send traffic to a host in a
group that has the next highest priority (e.g., Group 1),
and so on. Whenever a host in the group that has the
highest priority (e.g., Group 0) becomes available again,
the device sends the traffic to the host in this group.
■
[2]
Sticky Next
= The device initially attempts to send
traffic to the group of hosts that has the highest priority
(e.g., Group 0). If none of the hosts in the group respond,
the device attempts to send traffic to a host in a group
that has the next highest priority (e.g., Group 1). Even if
the group of hosts that has the highest priority (e.g.,
Group 0) becomes available again, the device continues
sending traffic to this lower priority group (e.g., Group 1) .
'Automatic Reconnect'
http-persistent-
connection
[HTTPRemoteServices_
PersistentConnection]
Defines whether the HTTP connection with the host remains
open or is only opened per request.
■
[0]
Disable
= The HTTP connection is created per client
(user) request and remains connected until the server
closes the connection.
■
[1]
Enable
= (Default) The device creates the HTTP
connection once you have configured the service. If the
server closes the connection, the device re-opens it. If
the keep-alive timeout is configured, the device uses
HTTP keep-alive messages to keep the connection open
all the time.
Login Needed
http-login-needed
[HTTPRemoteServices_
LoginNeeded]
Enables the use of the AudioCodes proprietary REST API
Login and Logout commands for connecting to the remote
host. The commands verify specific information (e.g.,
software version) before allowing connectivity with the
device.
■
[0]
Disable
= Commands are not used.
- 250 -
Summary of Contents for Mediant 4000 SBC
Page 1: ...User s Manual AudioCodes Series of Session Border Controllers SBC Mediant 4000 SBC Version 7 2...
Page 40: ...Part I Getting Started with Initial Connectivity...
Page 48: ...Part II Management Tools...
Page 113: ...Part III General System Settings...
Page 118: ...Part IV General VoIP Configuration...
Page 525: ...Part V Session Border Controller Application...
Page 654: ...Part VI Cloud Resilience Package...
Page 663: ...Part VII High Availability System...
Page 685: ...Part VIII Maintenance...
Page 759: ...Part IX Status Performance Monitoring and Reporting...
Page 844: ...Part X Diagnostics...
Page 888: ...Part XI Appendix...