Polycom 1725-11530-310 User Manual

 Configuring Your System

4 - 7

There are three options for distinctive ringing:

The user can select the ring type for each line. This option has the lowest 

priority.

The ring type for specific callers can be assigned in the contact directory. 

For more information, refer to 

, the 

previous section. This option has a higher priority than option 1 and a 

lower priority than option 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:

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:

Configuration file: 
sip.cfg

Specify the mapping of Alert-Info strings to ring types. 

 For more information, refer to 

 on 

page 

.

Configuration file: 
phone1.cfg

Specify the ring type to be used for each line. 

 For more information, refer to 

 on page 

XML File: <Ethernet 
address>-directory.
xml

This file can be created manually using an XML editor. 

For more information, refer to 

 on page 

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.

Configuration file: 
sip.cfg

Specify the mapping of Alert-Info strings to call waiting types.

For more information, refer to 

 on 

page 

.