Account Settings
103
At the start of a call, server availability is determined by SIP signaling failure. SIP signaling failure depends on the
SIP protocol being used as described below:
l
If TCP is used, then the signaling fails if the connection or the send fails.
l
If UDP is used, then the signaling fails if ICMP is detected or if the signal times out. If the signaling has been
attempted through all servers in the list (this list contains all the server addresses resolved by the DNS server) and
this is the last server, then the signaling fails after the complete UDP timeout defined in
. If it is not the
last server in the list, the maximum number of retries depends on the configured retry counts (configured by the
parameter “account.X.sip_server.Y.retry_counts”).
Registration Method of the Failover/Fallback Mode
Registration method of the failover mode:
The IP phone must always register to the primary server first except in failover conditions. If this is unsuccessful, the
phone will re-register as many times as configured until the registration is successful. When the primary server regis-
tration is unavailable, the secondary server will serve as the working server. As soon as the primary server registration
succeeds, it returns to be the working server.
Registration methods of the fallback mode include (not applicable to outbound proxy servers):
l
Concurrent registration (default)
: The IP phone registers to SIP server 1 and SIP server 2 (working server and fall-
back server) at the same time. Note that although the IP phone registers to two SIP servers, only one server works at
the same time. If it fails, a fallback server can take over the basic calling capability, but without some advanced fea-
tures (for example, shared lines and MWI) offered by the working server.
l
Successive registration
: The IP phone only registers to one server at a time. The IP phone first registers to the work-
ing server. In a failure situation, the IP phone registers to the fallback server, and the fallback server can take over all
calling capabilities.
Fallback Server Redundancy Configuration
The following table lists the parameters you can use to configure fallback server redundancy.
Parameter
account.X.fallback.redundancy_type
[1]
<MAC>.cfg
Description
It configures the registration mode in fallback mode.
Note
: It is not applicable to outbound proxy servers.
Permitted
Values
0
-Concurrent registration
1
-Successive registration
Default
0
Parameter
account.X.fallback.timeout
[1]
<MAC>.cfg
Description
It configures the time interval (in seconds) for the IP phone to detect whether the working server is avail-
able by sending the registration request after the fallback server takes over call control.
Note
: It is not applicable to outbound proxy servers.
Permitted
Values
Integer from 10 to 2147483647
Default
120
Parameter
account.X.outbound_proxy_fallback_interval
[1]
<MAC>.cfg
Description
It configures the time interval (in seconds) for the IP phone to detect whether the working outbound
proxy server is available by sending the registration request after the fallback server takes over call con-
trol.
Summary of Contents for W60P Telesystem
Page 1: ......
Page 18: ...Table of Contents 11 Appendix 255 RFC and Internet Draft Support 255...
Page 19: ...Administrator s Guide for W60P W53P W41P DECT Phones 12...
Page 47: ...40 Administrator s Guide for W60P W53P W41P DECT Phones...
Page 73: ...66 Administrator s Guide for W60P W53P W41P DECT Phones...
Page 123: ...116 Administrator s Guide for W60P W53P W41P DECT Phones...
Page 125: ...118 Administrator s Guide for W60P W53P W41P DECT Phones...
Page 139: ...132 Administrator s Guide for W60P W53P W41P DECT Phones...
Page 171: ...164 Administrator s Guide for W60P W53P W41P DECT Phones...
Page 193: ...186 Administrator s Guide for W60P W53P W41P DECT Phones...
Page 227: ...220 Administrator s Guide for W60P W53P W41P DECT Phones...
Page 253: ...246 Administrator s Guide for W60P W53P W41P DECT Phones...
Page 261: ...254 Administrator s Guide for W60P W53P W41P DECT Phones...
