sipXecs

Alarms from sipXalarms-config.xml are persisted in 'alarm-codes' table - this way alarms are available also after an upgrade is issued. However, sipxsupervisor RPM install writes a new sipXalarms-config.xml file and define new types of alarm - these are not part of 'alarm-codes' table.
sipXconfig must parse sipXalarms-config.xml and learn about the new alarm types *before* it overwrites the file.
Alarm types added in sipXalarms-config.xml should be persisted as well.