Polycom SIP 3.1 manual Automatic Call Distribution, Server Redundancy

Administrator’s Guide SoundPoint IP / SoundStation IP

Local	Local Phone User	Use the SIP Configuration menu to specify the local SIP signaling
(continued)	Interface	port, a default SIP server to register to and registration information for
		up to twelve registrations (depending on the phone model). The SIP
		Configuration menu contains a sub-set of all the parameters available
		in the configuration files.
		Either the Web Server or the boot server configuration files or the
		local phone user interface should be used to configure registrations,
		not a mixture of these options. When the SIP Configuration menu is
		used, it is assumed that all registrations use the same server.
		Changes are saved to local flash and backed up to <Ethernet
		address>-phone.cfgon the boot server. Changes will permanently
		override global settings unless deleted through the Reset Local
		Config menu selection and the <Ethernet address>-phone.cfgis
		removed from the boot server.
		For more information, refer to Local <local/> on page A-6, Server
		<server/> on page A-7, and Registration <reg/> on page A-107.

Automatic Call Distribution

The phone allows automatic call distribution (ACD) login and logout. This feature depends on support from a SIP server.

Configuration changes can performed centrally at the boot server:

Central	Configuration file:	Turn this feature on or off.
(boot server)	sip.cfg	•	For more information, refer to Feature <feature/> on page A-92.
	Configuration file:	Enable this feature per registration.
	phone1.cfg	•	For more information, refer to Registration <reg/> on page A-107.

The phone also supports ACD agent available and unavailable. This feature depends on support from a SIP server.

Configuration changes can performed centrally at the boot server:

Central	Configuration file:	Turn this feature on or off.
(boot server)	sip.cfg	•	For more information, refer to Feature <feature/> on page A-92.
	Configuration file:	Enable this feature per registration.
	phone1.cfg	•	For more information, refer to Registration <reg/> on page A-107.

Server Redundancy

Server redundancy is often required in VoIP deployments to ensure continuity of phone service for events where the call server needs to be taken offline for maintenance, the server fails, or the connection from the phone to the server fails.

4 - 56