Spectralink 84-Series Series Wireless Telephones Administration Guide
1725-86984-000_P.docx
September 2016
210
Phone Configuration
The handsets at the customer site are configured as follows:
Server 1 (the primary server) will be configured with the DNS name of the service provider
call server. The IP address of the server(s) will be provided by the DNS server, for
example:
reg.1.server.1.address=voipserver.serviceprovider.com .
Server 2 (the fallback server) will be configured to the address of the router/gateway that
provides the fallback telephony support and is on-site, for example:
reg.1.server.2.address=172.23.0.1 .
Note: Caution When Using Multiple Servers Per Registration
It is possible to configure the handset for more than two servers per registration,
but you need to exercise caution when doing this to ensure that the handset and
network load generated by registration refresh of multiple registrations does not
become excessive. This would be of particular concern if a handset had multiple
registrations with multiple servers per registration and it is expected that some of
these servers will be unavailable.
Phone Operation for Registration
After the handset has booted up, it will register to all the servers that are configured.
Server 1 is the primary server and supports greater SIP functionality than other servers. For
example, SUBSCRIBE/NOTIFY services used for features such as shared lines, presence, and
BLF will be established only with Server 1.
Upon the registration timer expiry of each server registration, the handset will attempt to re-
register. If this is unsuccessful, normal SIP re-registration behavior (typically at intervals of 30 to
60 seconds) will proceed and continue until the registration is successful (for example, when the
Internet link is once again operational). While the primary server registration is unavailable, the
next highest priority server in the list will serve as the working server. As soon as the primary
server registration succeeds, it will return to being the working server.
Failover to Servers that are Not Registered
If
reg.x.server.y.register
is set to 0, the handset will not register to that
server. However, an INVITE will fail over to that server if all higher priority servers
are down.