
_________________________________________________________________________________
_________________________________________________________________________________
64 TAU-72.IP/TAU-36.IP Universal Network Terminal
Gateway may operate with a single main SIP-proxy and up to four redundant SIP-proxies. For exclusive
operations with the main SIP-proxy, 'Parking' and 'Homing' modes are identical. In this case, if the main SIP-
proxy fails, it will take time to restore its operational status.
For operations with redundant SIP-proxies, 'Parking' and 'Homing' modes will work as follows: the
gateway sends INVITE message to the main SIP-proxy address when performing outgoing call, and REGISTER
message when performing registration attempt. If on expiration of 'Invite total timeout' there is no response
from the main SIP-proxy or response 408 (when 'changeover by timeout' option is enabled), 503, or 505 is
received, the gateway sends INVITE (or REGISTER) message to the first redundant SIP-proxy address, and if it is
not available, the request is forwarded to the next redundant SIP-proxy and so forth. When available redundant
SIP-proxy if found, registration will be renewed on that SIP-proxy.
Next, the following actions will be available depending on the selected redundancy mode:
In the 'parking' mode, the main SIP-proxy management is absent, and the gateway will
continue operation with the redundant SIP-proxy even when the main proxy operation is
restored. If the connection to the current SIP-proxy is lost, querying of the subsequent
SIP-proxies will be continued using the algorithm described above. If the last redundant
SIP-proxy is not available, the querying will continue in a cycle, beginning from the main
SIP-proxy:
In the 'homing' mode, three types of the main SIP-proxy management are available:
periodic transmission of OPTIONS messages to its address, periodic transmission of
REGISTER messages to its address, or transmission of INVITE request when performing
outgoing call. First of all, INVITE request is sent to the main SIP-proxy, and if it is
unavailable, then to the next redundant one, etc. Regardless of the management type,
when the main SIP-proxy operation is restored, gateway will renew its registration and
begin operation with the main SIP-proxy.
SIP configuration:
–
Proxy mode
—select SIP server (SIP-proxy) operation mode form the drop-down list:
–
Off
—
disabled.
–
Parking
—
SIP-proxy redundancy mode without main SIP-proxy management.
–
Homing
—
SIP-proxy redundancy mode with main SIP-proxy management.
–
Proxy/ Registrar address 1..5
—
SIP-proxy/registration server network address; you may define the port
after the colon; if it is not specified, 5060 will be taken as the default port value.
–
Use registration 1.
.5—when checked, register on server, otherwise registration server will not be used.
Home server test
—depending on the selected configuration, test the main proxy using OPTIONS,
REGISTER, or INVITE messages in 'homing' redundancy mode.
–
Change-over
—this setting defines the request transmission error that will be used for redundant proxy
changeover: INVITE and REGISTER, INVITE only or REGISTER only.
–
Changeover by timeout
—when enabled, redundant proxy changeover will be performed when response
408 is received, in addition to standard responses 503 and 505.
–
Keepalive time (s)
—period of time between OPTIONS or REGISTER management message transfers, in
seconds.
–
Full RURI compliance
—when checked, all URI elements (
user, host and port
—
subscriber number, IP