User`s guide

Polycom VVX Expansion Module Administrator’s Guide Addendum UC Software 4.1.6
Polycom, Inc. 47
Parameter
Permitted Values
Default
reg.x.server.y.expires.lineSeize
0 to 65535
30
Requested line-seize subscription period.
reg.x.server.y.expires.overlap
5 to 65535
60
The number of seconds before the expiration time returned by server x at which the phone should try to re-
register. The phone will try to re-register at half the expiration time returned by the server if the server value is
less than the configured overlap value.
reg.x.server.y.failOver.failBack.mode
newRequests,
DNSTTL,
registration,
duration
newRequests
The mode for failover failback (this parameter overrides voIpProt.server.x.failOver.failBack.mode):
- newRequests All new requests are forwarded first to the primary server regardless of the last used server.
- DNSTTL The phone tries the primary server again after a timeout equal to the DNS TTL configured for the
server to which the phone is registered.
- registration The phone tries the primary server again when the registration renewal signaling begins.
- duration The phone tries the primary server again after the time specified by
reg.x.server.y.failOver.failBack.timeout.
reg.x.server.y.failOver.failBack.timeout
0, 60 to 65535
3600
The time to wait (in seconds) before failback occurs (overrides
voIpProt.server.x.failOver.failBack.timeout).If the failback mode is set to Duration, the phone
waits this long after connecting to the current working server before selecting the primary server again. If 0, the
phone will not failback until a failover event occurs with the current server.
reg.x.server.y.failOver.failRegistrationOn
0 or 1
0
When set to 1, and the reRegisterOn parameter is enabled, the phone 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 phone will attempt failback without first attempting to
register with the primary server to determine if it has recovered.
reg.x.server.y.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 phone
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.server.y.failOver.reRegisterOn
0 or 1
0
This parameter overrides the voIpProt.server.x.failOver.reRegisterOn. When set to 1, the phone 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 phone won’t attempt to register with the secondary server, since the phone will assume that the primary
and secondary servers share registration information.
reg.x.server.y.lcs
0 or 1
0
If 0, the Microsoft Live Communications Server (LSC) is not supported. If 1, LCS is supported for registration x.