Table of Contents
Advertisement
Central
Configuration file:
sip.cfg
(boot server)
Configuration file:
phone1.cfg
Local
Web Server
(if enabled)
Local Phone User
Interface
Bridged Line Appearance
Configuration changes can performed centrally at the boot server or locally:
Specify whether diversion should be disabled on shared lines.
•
For more information, refer to
A-67.
Specify line-seize subscription period.
•
For more information, refer to
Specify standard or non-standard behavior for processing line-seize
subscription for mutual exclusion feature.
•
For more information, refer to
page A-16.
Specify per-registration line type (private or shared), barge-in
capabilities, and line-seize subscription period if using per-registration
servers. A shared line will subscribe to a server providing call state
information.
•
For more information, refer to
Specify per-registration whether diversion should be disabled on
shared lines.
•
For more information, refer to
Specify line-seize subscription period.
Navigate to http://<phoneIPAddress>/appConf.htm#se
Specify standard or non-standard behavior for processing line-seize
subscription for mutual exclusion feature.
Navigate to http://<phoneIPAddress>/appConf.htm#ls
Specify per-registration line type (private or shared) and line-seize
subscription period if using per-registration servers, and whether
diversion should be disabled on shared lines.
Navigate to http://<phoneIPAddress>/reg.htm
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.
Specify per-registration line type (private or shared) using the SIP
Configuration menu. Either the Web Server or the boot server
configuration files or the local phone user interface should be used to
configure registrations, not a mixture of these options. When the SIP
Configuration menu is used, it is assumed that all registrations use
the same server.
Calls and lines on multiple phones can be logically related to each other. A call
that is active on one phone will be presented visually to phones that share that
line. Mutual exclusion features emulate traditional PBX or key system privacy
for shared calls. Incoming calls can be presented to multiple phones
Configuring Your System
Shared Calls <shared/>
Server <server/>
on page A-7.
Special Events <specialEvent/>
Registration <reg/>
on page A-107.
Diversion <divert/>
on page A-114.
on page
on
4 - 27
Advertisement
Table of Contents
