![SpectraLink 8440 Administration Manual Download Page 231](http://html.mh-extra.com/html/spectralink/8440/8440_administration-manual_1343808231.webp)
Spectralink 84-Series Series Wireless Telephones Administration Guide
1725-86984-000_P.docx
September 2016
231
Parameter
Permitted Values
Default
When set to
0
, and the reRegisterOn parameter is enabled, existing registrations will remain active. This means
that the handset will attempt failback without first attempting to register with the primary server to determine if it
has recovered.
reg.x.server.y.failOver.onlySignalWithRegistered
If you use proxy servers, set this parameter instead
:
reg.x.outboundProxy.failOver.onlySignalWithRegistered
0 or 1
1
When set to
1
, and the reRegisterOn and failRegistrationOn parameters are enabled, no signaling is accepted
from or sent to a server that has failed until failback is attempted or failover occurs. If the handset attempts to send
signaling associated with an existing call via an unregistered server (for example, to resume or hold a call), the call
will end. No SIP messages will be sent to the unregistered server.
When set to
0
, and the reRegisterOn and failRegistrationOn parameters are enabled, signaling will be accepted
from and sent to a server th
at has failed (even though failback hasn’t been attempted or failover hasn’t occurred).
Note: This setting primarily affects signaling associated with existing dialogs that are RFC-mandated to
communicate with the servers through which they were establish
ed. A new dialog’s signaling will be sent through
the ‘current’ server.
reg.x.server.y.failOver.failBack.mode
If you use proxy servers, set this parameter instead
:
reg.x.outboundProxy.failOver.failBack.mode
DNSTTL,
registration,
duration
registration
When set to
DNSTTL
, the primary server is retried after a timeout equal to the DNSTTL configured for the server
the handset is registered to (or via, for the outbound proxy scenario).
When set to
registration
, the primary server is retried when the current wo
rking server’s registration requires
renewal.
When set to
duration
, the primary server is retried after the amount of time defined by the
timeout
parameter (as
shown in the next row).
Note: When failback mode is set to DNSTTL
or
duration, re-registration with the primary server takes place only if
the handset is idle (that is, the handset has no calls or active lines). If the timeout period expires and call activity is
detected, failback will be retried every second.
reg.x.server.y.failOver.failBack.timeout
If you use proxy servers, set this parameter instead
:
reg.x.outboundProxy.failOver.failBack.timeout
0, 60 - 65535
3600
When failBack.mode is set to
duration
, the time in seconds after failing over to the current working server before
the primary server becomes the first server to forward new requests to.
If you set a value between
1
and
59
, the timeout will be 60 seconds. If you set a value of
0
, the primary server
won’t be selected as the first server to forward new requests to until a failover event occurs with the current
working server.
Table 10-20: All possible reg.x parameters used to set up server redundancy
Parameter
Permitted Values
Default
reg.x.auth.optimizedInFailover
0 or 1
0
The destination of the first new SIP request when failover occurs. If 0, the SIP request is sent to the server with the
highest priority in the server list. If 1, the SIP request is sent to the server which sent the proxy authentication
request.
reg.x.outboundProxy.failOver.failBack.mode
DNSTTL, registration,
duration
registration
The mode for failover failback (overrules
reg.x.server.y.failOver.failBack.mode
).
DNSTTL:
the handset tries the primary server again after a timeout equal to the DNS TTL configured for the
server that the handset is registered to.