User's Manual
operational database. Avaya recommends that you make a fresh copy of the operational
database, because then you are sure there is no database inconsistency.
Using eCONFIG (Remote) on remote PC (client) in the Network
After the eCONFIG is installed on the DECT Messenger server PC the database is handled
as shown in Figure 21: eCONFIG database handling when used on a remote PC (client
PC) on page 92.
Figure 21: eCONFIG database handling when used on a remote PC (client PC)
After you start the eCONFIG for the first time on the remote PC, a copy is made of the
configuration database of DECT Messenger (Messenger_CFG.MDB). This copy is stored on
the remote PC where the eCONFIG is running, in the eCONFIG directory: C:\SOPHO
Messenger@net\eConfig\Mdb with the file name: Messenger_WRK.cfg. You cannot make
system configuration changes in this database, only changes in:
• Users
• Groups
• Devices
After you make changes in Users, Groups or Devices, these changes are stored in the
eCONFIG database (Messenger_WRK.cfg) and in the operational database
(Messenger_CFG.mdb), and are therefore immediately active. Saving this information into the
operational database is done by sending an XML string from the eCONFIG to the eKERNEL.
The eKERNEL stores this information into the operational database.
Note:
If more than one eCONFIG is active at the same time on different PCs, the individual
eCONFIG databases are not updated or synchronized after changes are made in one
eCONFIG. Only the operational database, and the database in the eCONFIG module where
the change is made, are updated. Changes made in Groups using the eWEB interface are
DECT Messenger Customer Engineer Manual
92 DECT Messenger Fundamentals March 2012
Comments? infodev@avaya.com