This suggestion is an enhancement request to the pbx ldap replicator for active directory replication.

Currently (as of V13r3 and before) the pbx ldap replicator fails if an object with the same CN that shall be replicated from the active directory exists within the pbx ldap.
The replicator then stops at this object with a "1,Common Operations Error" message in the replicator status and a message with "CN already exists" containing the conflicting CN is written to the tracebuffer.
See https://wiki.innovaphone.com/index.php?title=Reference7:Configure_Active_Directory_Replication#Replication_fails_due_to_1.2CCommon_Operations_Error

Unfortunately this hint often goes unoticed and unrecognized by administrators and users are either added manually (leading to further errors) or support requests regarding non-functioning AD replication are raised.

The enhancement thus consists of two changes:

- If an object with a given CN from the AD already exists within the pbx ldap the pbx ldap replicator should raise an alarm under Maintenance -> Alarms containing the CN of said object (and a severity level). The alarm should be persistent as long as the replication conflict is unresolved.
- The pbx ldap replicator should then skip the conflicting object and continue the replication