Automatic off-hook call placement, Call hold – Polycom SOUNDPOINT SIP 2.2.0 User Manual

Page 64

Advertising
background image

Administrator’s Guide SoundPoint IP / SoundStation IP

4 - 16

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:

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

(boot server)

Configuration file:
phone1.cfg

Specify which registrations have the feature and what contact to call
when going off hook.

For more information, refer to

Automatic Off-Hook Call Placement

<autoOffHook/>

on page

A-89

.

Central

(boot server)

Configuration file:
sip.cfg

Specify whether RFC 2543 (c=0.0.0.0) or RFC 3264 (a=sendonly or
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

(if enabled)

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).

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. Changes will permanently
override global settings unless deleted through the Reset Local
Config menu selection and the <Ethernet address>-phone.cfg is
removed from the boot server.

Local Phone User
Interface

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).

Advertising