When you perform an administrative task from System Manager, the local database is immediately updated. If you do the action through a Communication Manager SAT screen, or through a phone, or from any of the several management applications such as Site Administration, MultiSite Administration, Native Configuration Manager, or MyPhone, it is not immediately reflected in System Manager. This scenario creates an out-of-sync condition between the Communication Manager and System Manager.
The CM notify sync feature provides:
Near-real time notifications from Communication Manager to System Manager whenever you run certain tasks against a Communication Manager object from a system other than System Manager
Notifications whenever the tti-m, tti-s, psa-u, psa-a, or psa-d login perform predefined actions against a Communication Manager station object.
After a Communication Manager sends notifications to System Manager, System Manager discovers the complete details of the task you preformed. The transmission of notifications in the form of event messages from Communication Manager to System Manager is based on the existing rsyslog capability of Communication Manager. rsyslog uses UDP or TCP to send event messages from the originating Communication Manager to the System Manager.
Note:
The daily default synchronization and any other scheduled synchronization operations are unaffected by the CM notify sync feature.
You need Communication Manager 6.2 or later to enable the CM notify sync feature. System Manager 6.3 supports one-way and two-way TLS.
Note:
If you log on to Communication Manager using SSH from a system with IPv6 address assigned and execute add/change/duplicate/delete commands on Communication Manager, Notify sync does not operate successfully.
You must log on to Communication Manager from a system with IPv4 address assigned for Notify sync feature to operate.