Polycom SIP 3.1 Speaker System User Manual


 
Configuring Your System
4 - 7
Distinctive Ringing
There are three options for distinctive ringing:
1. The user can select the ring type for each line. This option has the lowest
priority.
2. The ring type for specific callers can be assigned in the contact directory.
For more information, refer to Distinctive Incoming Call Treatment, the
previous section. This option has a higher priority than option 1 and a
lower priority than option 3.
3. The
voIpProt.SIP.alertInfo.x.value
and
voIpProt.SIP.alertInfo.x.class
fields can be used to map calls to
specific ring types. This option has the highest priority.
Configuration changes can performed centrally at the boot server or locally:
Distinctive Call Waiting
The
voIpProt.SIP.alertInfo.x.value
and
voIpProt.SIP.alertInfo.x.class
fields can be used to map calls to distinct
call waiting types, currently limited to two styles.
Configuration changes can performed centrally at the boot server:
Central
(boot server)
Configuration file:
sip.cfg
Specify the mapping of Alert-Info strings to ring types.
For more information, refer to Alert Information <alertInfo/> on
page A-15.
Configuration file:
phone1.cfg
Specify the ring type to be used for each line.
For more information, refer to Registration <reg/> on page A-107.
XML File: <Ethernet
address>-directory.
xml
This file can be created manually using an XML editor.
For more information, refer to Local Contact Directory on page
4-9.
Local Local Phone User
Interface
The user can edit the ring types selected for each line under the
Settings menu. The user can also edit the directory contents.
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.
Central
(boot server)
Configuration file:
sip.cfg
Specify the mapping of Alert-Info strings to call waiting types.
For more information, refer to Alert Information <alertInfo/> on
page A-15.