Page 230 of 910 Features
553-3001-365 Standard 4.00 August 2005
Supported run-time changes
Therefore, IP Line 4.5 supports only run-time changes for the following:
• changes to the CONFIG.INI file
• add card or delete card changes to the BOOTP.TAB file
Configuration changes have an effect only on new calls. Existing calls are not
interrupted. However, there are exceptions:
• If the active Call Server ELAN link’s configuration data is changed (for
example, a changed IP address), then active calls are released.
Note: If the non-active Call Server is changed (for example, survivable
side IP address), then the calls are not affected.
When the Call Server’s ELAN network interface is re-initialized to
implement the configuration change, the IP Phones and gateway
channels registrations are unregistered on the Call Server. The Call
Server releases the calls. When the link is re-established, the LTPS
synchronizes the call states and releases the active calls. Service is
interrupted during this re-establishment period and the following are
affected:
— New IP Phones cannot register.
— Registered IP Phones cannot establish new calls.
— The Voice Gateway Media Card’s faceplate displays S009.
Once the ELAN link comes back up, the Line Terminal Proxy Server
(LTPS) reregisters the IP Phone s with the Call Server and all service is
resumed.
• If the codec list is changed, the Voice Gateway Media Card's DSPs might
need to be reloaded. For instance, one DSP image contains G.711, FAX,
and G.729A/G.729AB. The other DSP image contains G.711, FAX, and
G.723.1. If the user has a node configured with the G.729AB codec and
the user performs an administrative change to use G.723.1 (or vice
versa), the DSPs must be reloaded.
After the CONFIG.INI file containing the administrative change is
downloaded to a Voice Gateway Media Card, the card's DSPs are