CHAPTER 18 Core Entities
Mediant 4000 SBC | User's Manual
Parameter
Description
Note:
If you configure the 'Authentication Mode'
parameter to
SBC as Server
, you can specify the SIP
request (method) types (e.g., INVITE) that must be
challenged by the device, using the IP Group's
'Authentication Method List' parameter.
GW Group Status
'GW Group Registered IP Address'
(Read-only field) Displays the IP address of the IP
Group entity (gateway) if registered with the device;
otherwise, the field is blank.
Note:
The field is applicable only to Gateway-type IP
Groups (i.e., the 'Type' parameter is configured to
Gateway).
'GW Group Registered Status'
(Read-only field) Displays whether the IP Group entity
(gateway) is registered with the device ("Registered" or
"Not Registered").
Note: The field is applicable only to Gateway-type IP
Groups (i.e., the 'Type' parameter is configured to
Gateway).
Configuring Proxy Sets
The Proxy Sets table lets you configure up to 625 Proxy Sets. A Proxy Set defines the address (IP
address or FQDN) and transport type (e.g., UDP or TCP) of a SIP server (e.g., SIP proxy and SIP
registrar server). The Proxy Set represents the destination of the IP Group configuration entity.
●
You can configure each Proxy Set with up to 10 proxy servers (rows) in the Proxy
Address table (a "child" of the Proxy Sets table), configured as IP addresses (in
dotted-decimal notation) and/or DNS hostnames (FQDN).
●
Each Proxy Set supports up to 15 DNS-resolved IP addresses.
●
Each Proxy Set supports up to 15 IP addresses, regardless of how the IP address
is obtained--DNS resolved or manually configured (dotted-decimal notation).
●
For all Proxy Sets together, the device supports up to 4,500 DNS-resolved IP
addresses. If the DNS resolution provides more than this number, it ignores the
extra addresses.
●
An SRV query sent by the device can return up to 50 hostnames. For each
hostname, the subsequent DNS A-record query sent by the device can resolve into
up to 50 IP addresses.
Multiple proxy servers enables you to implement proxy load balancing and redundancy. These
features are supported by the device's proxy keep-alive feature, which when enabled, sends keep-
alive messages (SIP OPTIONS) to all configured proxy servers to determine their connectivity
status (offline or online). You can also configure the device to consider the proxy as offline if
specific SIP response codes are received in response to the keep-alive messages. You can
configure the number of required consecutive successful keep-alive messages before the device
considers a previously offline proxy as online. This mechanism avoids the scenario in which the
device falsely detects a proxy as being online when it is actually offline, resulting in call routing
failure.
- 367 -
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...