SMGR : INIT synchronization between Avaya System Manager and Communication Manager failed


Doc ID    SOLN387116
Version:    1.0
Status:    Published
Published date:    13 Oct 2026
Author:   
anilkumark
 

Details

Both SMGR and CM are running version 10.2.1.4.

Problem Clarification

Synchronization retrieves CM objects correctly, but the job finally ends with Sync failed.

The issue started around the time of a migration from G650 to G450, before the CM upgrade from 10.1 to 10.2.1.4. Current trunk groups and signaling groups in CM appear to be configured correctly.

Cause

The IPTCM debug log shows that the failure occurs during cleanUpOrphans() due to a database foreign key constraint:

ERROR: update or delete on table "ipt_sig_group" violates foreign key constraint on table "ipt_trunk_grp"
Detail: Key (id)=(54) is still referenced from table "ipt_trunk_grp".

The issue was that there is a trunk group associated with a signaling group number that was not configured. There were no trunk members as well. This was causing the issue.

CM corruption.

Solution

Remove the reference of the unconfigured signaling group from the trunk group.

This resolves the issue. 

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy