Spectralink 84-Series Series Wireless Telephones Administration Guide
1725-86984-000_P.docx
September 2016 232
registration: the handset tries the primary server again when the registration renewal signaling begins.
duration: the handset tries the primary server again after the time specified by
reg.x.outboundProxy.failOver.failBack.timeout expires.
reg.x.outboundProxy.failOver.failBack.timeout
The time to wait (in seconds) before failback occurs (overrules
reg.x.server.y.failOver.failBack.timeout).If the fail back mode is set to Duration, the handset waits
this long after connecting to the current working server before selecting the primary server again. If 0, the handset
will not fail-back until a fail-over event occurs with the current server.
reg.x.outboundProxy.failOver.failRegistrationOn
When set to 1, and the reRegisterOn parameter is enabled, the handset will silently invalidate an existing
registration (if it exists), at the point of failing over. 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.
Note that reg.x.outboundProxy.failOver.RegisterOn must be enabled.
reg.x.outboundProxy.failOver.onlySignalWithRegistered
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 that has failed
(even though failback hasn’t been attempted or failover hasn’t occurred).
reg.x.outboundProxy.failOver.reRegisterOn
This parameters overrules reg.x.server.y.failOver.failBack.RegisterOn. When set to 1, the handset
will attempt to register with (or via, for the outbound proxy scenario), the secondary server. If the registration
succeeds (a 200 OK response with valid expires), signaling will proceed with the secondary server. When set to 0,
the handset won’t attempt to register with the secondary server, since the handset will assume that the primary and
secondary servers share registration information.
reg.x.server.y.failOver.failBack.mode
DNSTTL, registration,
duration
The mode for failover failback (this parameter overrules voIpProt.server.x.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.
registration – the handset tries the primary server again when the registration renewal signaling begins.
duration – the handset tries the primary server again after the time specified by
reg.x.server.y.failOver.failBack.timeout.
reg.x.server.y.failOver.failBack.timeout
The time to wait (in seconds) before failback occurs (overrules
voIpProt.server.x.failOver.failBack.timeout).If the fail back mode is set to Duration, the handset
waits this long after connecting to the current working server before selecting the primary server again. If 0, the
handset will not fail-back until a fail-over event occurs with the current server.
reg.x.server.y.failOver.failRegistrationOn
When set to 1, and the reRegisterOn parameter is enabled, the handset will silently invalidate an existing
registration (if it exists), at the point of failing over. 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.
To Next Page
Loading...
