Polycom IP 320 Administrator's Manual page 123

Central Configuration file:
sip.cfg
(provisioning
server)
Configuration file:
phone1.cfg
Note
For more information, refer to "Technical Bulletin 5844: SIP Server Fallback
Enhancements on SoundPoint IP Phones" at
http://www.polycom.com/support/voice/soundpoint_ip/VoIP_Technical
_Bulletins_pub.html .
Configuration changes can be performed centrally at the provisioning server:
Specify global primary and fallback server configuration parameters.
• For more information, refer to
Specify per registration primary and fallback server configuration
parameters values that override those in sip.cfg.
• For more information, refer to
DNS SIP Server Name Resolution
If a DNS name is given for a proxy/registrar address, the IP address(es)
associated with that name will be discovered as specified in RFC 3263. If a port
is given, the only lookup will be an A record. If no port is given, NAPTR and
SRV records will be tried, before falling back on A records if NAPTR and SRV
records return no results. If no port is given, and none is found through DNS,
5060 will be used.
Refer to http://www.ietf.org/rfc/rfc3263.txt
Failure to resolve a DNS name is treated as signaling failure that will cause a
failover.
Behavior When the Primary Server Connection Fails
For Outgoing Calls (INVITE Fallback)
When the user initiates a call, the phone will go through the following steps to
connect the call:
1. Try to make the call using the working server.
2. If the working server does not respond correctly to the INVITE, then try
and make a call using the next server in the list (even if there is no current
registration with these servers). This could be the case if the Internet
connection has gone down, but the registration to the working server has
not yet expired.
3. If the second server is also unavailable, the phone will try all possible
servers (even those not currently registered) until it either succeeds in
making a call or exhausts the list at which point the call will fail.
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:
Configuring Your System
Protocol <voIpProt/> on page A-7.
Registration <reg/> on page A-134.
for an example.
4 - 61