CHAPTER 18 Core Entities
Mediant 4000 SBC | User's Manual
Parameter
Description
Note:
■
You must configure both priority and weight (or none of them).
In other words, if you configure this parameter, you must also
configure the 'Proxy Random Weight' parameter. If you don't
configure this parameter, you must also not configure the
'Proxy Random Weight' parameter.
■
If weight and priority are not configured for any of the proxy
servers of the Proxy Set, the order in which the addresses (IP
addresses and FQDNs) are listed in the table determine their
priority (i.e., top-listed address has the highest priority).
■
For FQDNs, weight and priority of DNS-resolved IP addresses
are determined by the DNS. However, this parameter's value
overrides the priority received from the DNS.
■
If you have configured at least one of the proxy servers of the
Proxy Set with weight and priority, the device prioritizes all the
configured proxy servers according to weight and priority. In
this case, proxy servers that are not configured with priority
(i.e., 0) are considered as proxy servers with the highest
priority.
■
The parameter is applicable to load balancing (see the 'Proxy
Load Balancing Method' parameter), and homing and parking
redundancy (see the 'Redundancy Mode' parameter).
'Proxy Random Weight'
weight
[ProxyIp_Weight]
Defines the weight of the proxy.
The valid value is 0 to 65535, where 0 is the highest weight and
65535 the lowest. The default is 0.
Note:
■
The parameter is applicable only if you have configured the
'Proxy Load Balancing Method' parameter to
Random
Weights
. For more information on weights, see this parameter.
■
You must configure both priority and weight (or none of them).
In other words, if you configure this parameter, you must also
configure the 'Proxy Priority' parameter. If you don't configure
this parameter, you must also not configure the 'Proxy Priority'
parameter.
■
For proxy servers configured with FQDNs, this parameter's
value overrides the weight received for DNS-resolved IP
addresses from the DNS server.
Building and Viewing SIP Entities in Topology View
The Topology view lets you easily build and view your main SIP entities, including IP Groups, SIP
Interfaces, and Media Realms. The Topology view graphically displays these entities and the
associations between them, giving you a better understanding of your SIP topology and
configuration. The Topology view also lets you configure additional SIP settings that are important
to your deployment such as routing and manipulation. You can use the Topology view as an
alternative to configuring the entities in their respective Web pages or you can use it in combination.
To access the Topology view, do one of the following:
- 378 -
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...