Polycom SIP 2.2.0 manual Automatic Off-Hook Call Placement, Call Hold

Administrator’s Guide SoundPoint IP / SoundStation IP

Automatic Off-Hook Call Placement

The phone supports an optional automatic off-hook call placement feature for each registration.

Configuration changes can performed centrally at the boot server:

Central	Configuration file:	Specify which registrations have the feature and what contact to call
(boot server)	phone1.cfg	when going off hook.
		• For more information, refer to Automatic Off-Hook Call Placement
		<autoOffHook/> on page A-89.

Call Hold

The purpose of hold is to pause activity on one call so that the user may use the phone for another task, such as to make or receive another call. Network signaling is employed to request that the remote party stop sending media and to inform them that they are being held. A configurable local hold reminder feature can be used to remind the user that they have placed calls on hold.

Configuration changes can performed centrally at the boot server or locally:

Central	Configuration file:	Specify whether RFC 2543 (c=0.0.0.0) or RFC 3264 (a=sendonly or
(boot server)	sip.cfg	a=inactive) outgoing hold signaling is used.
		• For more information, refer to SIP <SIP/> on page A-10.
		Specify local hold reminder options.
		• For more information, refer to Hold, Local Reminder
		<hold/><localReminder/> on page A-58.
Local	Web Server	Specify whether or not to use RFC 2543 (c=0.0.0.0) outgoing hold
	(if enabled)	signaling. The alternative is RFC 3264 (a=sendonly or a=inactive).
		Navigate to: http://<phoneIPAddress>/appConf.htm#ls
		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.
	Local Phone User	Use the SIP Configuration menu to specify whether or not to use RFC
	Interface	2543 (c=0.0.0.0) outgoing hold signaling. The alternative is RFC 3264
		(a=sendonly or a=inactive).

4 - 16