Account Settings
101
in a dialog.
Note
: It works only if “account.X.outbound_proxy_enable” is set to 1 (Enabled).
Permitted Val-
ues
0
-Disabled, only the new SIP request messages from the IP phone will be sent to the outbound proxy
server in a dialog.
1
-Enabled, all the SIP request messages from the IP phone will be sent to the outbound proxy server in
a dialog.
Default
0
Web UI
Features->General Information->Use Outbound Proxy In Dialog
Server Redundancy
Server redundancy is often required in VoIP deployments to ensure continuity of phone service, for example, take the
call server offline for maintenance, the server fails, or the connection between the IP phone and the server fails.
Two types of redundancy are possible. In some cases, a combination of the two may be deployed:
l
Failover:
In this mode, the full phone system functionality is preserved by having a second equivalent capability call
server take over from the one that has gone down/off-line. This mode of operation should be done using the DNS
mechanism from the primary to the secondary server. Therefore, if you want to use this mode, the server must be
configured with a domain name.
l
Fallback:
In this mode, a second less featured call server with SIP capability takes over call control to provide basic
calling capability, but without some advanced features (for example, shared line and MWI) offered by the working
server. IP phones support configuration of two servers per SIP registration for the fallback purpose.
Note
For concurrent registration mode, it has certain limitation when using some advanced features, and for successive regis-
tration mode, the phone service may have a brief interrupt while the server fails. So we recommend you to use the failover
mode for server redundancy because this mode can ensure the continuity of the phone service and you can use all the call
features while the server fails.
Phone Configuration for Redundancy Implementation
To assist in explaining the redundancy behavior, an illustrative example of how an IP phone may be configured is
shown as below. In the example, server redundancy for fallback and failover purposes is deployed. Two separate serv-
ers (a working server and a fallback server) are configured for per line registration.
Summary of Contents for W53P
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 ...