CHAPTER18 Core Entities
Mediant 1000 Gateway & E-SBC | User's Manual
Parameter Description
✔ No response is received from the proxy each time the
device re-sends it. The number of retransmissions is
configured by the [HotSwapRtx] parameter. In such a
scenario, the device issues itself the SIP response code
408 (Request Timeout).
✔ The proxy rejects the message with a SIP response code
that you have configured in the Alternative Routing
Reasons table (see Configuring SIP Response Codes for
Alternative Routing Reasons) for SBC the application, or in
the Reasons for Tel-to-IP Alternative Routing table (see
Alternative Routing Based on SIP Responses) for the
Gateway application.
For the SBC application: You can employ alternative routing
with this option. If no response is received from any of the
redundant (online) proxies or the proxies reject the message
with a SIP response code that you have configured in the Altern-
ative Routing Reasons table, the device searches the IP-to-IP
Routing table for an alternative routing rule and if found, sends
the message to the rule's destination.
'Proxy Load Balancing
Method'
proxy-load-
balancing-method
[ProxySet_
ProxyLoadBalancingMe
thod]
Enables load balancing between proxy servers of the Proxy Set.
â– [0] Disable = (Default) Disables proxy load balancing.
â– [1] Round Robin = The device sends outgoing SIP messages
to the online proxy servers of the Proxy Set in a round-robin
fashion. The order of the round-robin is determined by the listed
order of the IP addresses in the Proxy Address table and their
priority. You can configure priority of each IP address using the
'Proxy Priority' parameter (see below). For DNS-resolved IP
addresses for proxy servers configured with an FQDN
(including NAPTR and SRV, if configured), the priority is
received from the DNS. For the Gateway application,
REGISTER messages are also distributed ina round-robin
fashion, unless you have configured a specific IP address of a
registrar server (using the RegistrarIP parameter). The IP
address list is refreshed every user-defined interval (see the
ProxyIPListRefreshTime parameter). If a change in the order of
the IP address entries in the list occurs, all load statistics are
erased and balancing starts over again.
â– [2] Random Weights = The outgoing requests are not
distributed equally among the proxy servers. The distribution is
determined by the weight of the proxy servers. You can
configure the weight per proxy server, using the 'Proxy Random
Weight' parameter in the Proxy Address table (see below). For
proxy servers configured with an FQDN, the weight of each
DNS-resolved IP address is received from the DNS server
(using SRV records). However, if you have configured the
weight for the FQDN in the 'Proxy Random Weight' parameter,
this parameter's value overrides the weight from the DNS
server. The device sends the requests in such a fashion that
each proxy receives a percentage of the requests according to
its' weight.
- 373 -
To Next Page
Loading...
Need help?
General
