User's Manual 378 Document #: LTRT-10532
Mediant 500L Gateway & E-SBC
Parameter Description
When the parameter is set to [2], the XferPrefix parameter can be used
to define different routing rules for redirected calls.
The parameter is ignored if the parameter AlwaysSendToProxy is set to
1.
Always Use Route
Table
always-use-route-table
[IPGroup_AlwaysUseR
outeTable]
Defines the Request-URI host name in outgoing INVITE messages.
[0] No (default).
[1] Yes = The device uses the IP address (or domain name) defined in
the Tel-to-IP Routing table (see Configuring Tel-to-IP Routing Rules on
page 509) as the Request-URI host name in outgoing INVITE
messages, instead of the value configured in the 'SIP Group Name'
field.
Note: The parameter is applicable only to Server-type IP Groups.
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).
17.5 Configuring Proxy Sets
The Proxy Sets table lets you configure up to 102 Proxy Sets. A Proxy Set defines the
address 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 (address) of the IP Group
configuration entity. Each Proxy Set can be configured with up to 10 addresses configured
as an IP address and/or DNS host name (FQDN), enabling you to implement load
balancing and redundancy (Proxy Hot-Swap feature) between multiple servers. Each Proxy
Set can be assigned a specific SSL/TLS certificate the (TLS Context), enabling you to use
different TLS certificates per SIP entity (IP Group). In addition, each Proxy Set must be
assigned a SIP Interface (and SRD), which determines, amongst others, the device's local
network interface through which communication with the Proxy Set is done.
You can enable the device's keep-alive feature per Proxy Set, which determines whether
proxies (addresses) configured for the Proxy Set are online or offline. If offline, the device
will not route the call to the specific proxy. You can configure the device to send either SIP
OPTIONS or REGISTER messages for the keep-alive. The keep-alive feature is required
when using the proxy load-balancing or redundancy feature. For load-balancing, the device
performs keep-alive on all proxies. For Parking-type redundancy, the device performs
keep-alive only on the currently active proxy. For Homing-type redundancy, the device
performs keep-alive on the current proxy as well as the "main" proxy. When using SIP
OPTIONS, you can configure the device to consider the proxy as offline if specific SIP
response codes are received from the keep-alive messages. To ensure that a previously
offline proxy is now online, you can configure the number of required consecutive
successful keep-alive messages (SIP OPTIONS only) before the device considers the
proxy as being 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. To
view the connectivity status of Proxy Sets, see Viewing Proxy Set Status on page 56.3.
To Next Page
Loading...
