Polycom SIP 2.2.2 manual Call Transfer, Local / Centralized Conferencing

Configuring Your System

Call Transfer

Call transfer enables the user (party A) to move an existing call (party B) into a new call between party B and another user (party C) selected by party A. The phone offers three types of transfers:

•Blind transfers—The call is transferred immediately to party C after party A has finished dialing party C’s number. Party A does not hear ring-back.

•Attended transfers—Party A dials party C’s number and hears ring-back and decides to complete the transfer before party C answers. This option can be disabled.

•Consultative transfers—Party A dials party C’s number and talks privately with party C after the call is answered, and then completes the transfer or hangs up.

Configuration changes can performed centrally at the boot server:

Central	Configuration file:	Specify whether to allow a transfer during the proceeding state of a
(boot server)	sip.cfg	consultation call.
		• For more information, refer to SIP <SIP/> on page A-10.
		Specify whether a transfer is blind or not.
		• For more information, refer to Call Handling Configuration <call/>
		on page A-55.

Local / Centralized Conferencing

The phone can conference together the local user with the remote parties of a configurable number of independent calls by using the phone’s local audio processing resources for the audio bridging. There is no dependency on network signaling for local conferences.

The phone also supports centralized conferences for which external resources are used such as a conference bridge. This relies on network signaling.

Note	Conferences are not available when the G.729 codec is enabled on the
	SoundStation IP 4000 conference phone.

4 - 17