Call Hold; Call Transfer - Polycom SoundPoint IP 300 Administrator's Manual

Administrator's Guide - SoundPoint
Local

3.2.2 Call Hold

Call hold is a fundamental feature of the phone. The purpose of hold is to pause activ-
ity 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.
Central
(boot
server)
Local

3.2.3 Call Transfer

Call transfer enables the user (User A or transferring user) to transform an existing call
with User B (primary call) into a new call between User B and a third user C (trans-
ferred-to user) selected by User A. The phone offers three types of transfers;
• Blind transfers: The call is transferred immediately to C after A has finished
52
®
IP / SoundStation
Web Server
(if enabled)
Local Phone User
Interface
Configuration file:
sip.cfg
Web Server
(if enabled)
Local Phone User
Interface
dialing C's number. User A does not hear ring-back.
Copyright © 2006 Polycom, Inc.
®
IP
None.
None.
Specify whether RFC 2543 (c=0.0.0.0) or RFC 3264 (a=sen-
donly or a=inactive) outgoing hold signaling is used.
• For more information, refer to 4.6.1.1.4 SIP <SIP/> on
page 88.
Specify local hold reminder options.
• For more information, refer to 4.6.1.12.2 Hold, Local
Reminder <hold/><localReminder/> on page 127.
Specify whether or not to use RFC 2543 (c=0.0.0.0) outgo-
ing hold 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.cfg on the boot server. They will perma-
nently override global settings unless deleted through the
Reset Local Config menu selection.
Use the SIP Configuration menu to specify whether or not to
use RFC 2543 (c=0.0.0.0) outgoing hold signaling. The
alternative is RFC 3264 (a=sendonly or a=inactive).
Features