Avaya Aura® System Manager (SMGR) holds a copy of the Avaya Aura® Communication Manager (CM) database, and it is important that the database is kept identical in both SMGR and CM. If they ever stop be

Question

Options

• AGo to the Inventory > Synchronize > Communication System, and send the database from SMGR
• BIssue a save translations all command in CM.
• CGo to the Replication page and issue a Repair of the database on SMGR.
• DGo to the Inventory > Synchronize > Communication System, and synchronize the database from

• B
  3% (1)
• C
  6% (2)
• D
  91% (30)

Explanation

Option D is correct because when SMGR and CM fall out of sync, the authoritative source to pull from is CM itself - you navigate to Inventory > Synchronize > Communication System and perform a synchronization from CM into SMGR, ensuring SMGR reflects the live CM database state.

• Option A is wrong because it sends the database from SMGR to CM, which would overwrite the live CM data with a potentially stale copy - the opposite of what you want.
• Option B (save translations all) saves CM's data to its own local storage, but does nothing to synchronize or communicate with SMGR.
• Option C is wrong because the Replication page and "Repair" function address SMGR's internal replication health (e.g., among SMGR nodes), not the SMGR-to-CM synchronization relationship.

Memory tip: Think of CM as the "source of truth" for telephony config - when in doubt, always pull from CM into SMGR, never push the other direction. The path "Inventory > Synchronize > Communication System" is your go-to for any CM sync operation.

No community discussion yet for this question.