I am working in a situation where an LDAP backend is used by multiple client programs. Among these are Luma and Evolution.
In Evolution, a user can enter multiple entries for each of the possible options for phones, faxes and pagers.
For example, one user could enter two homePhone entries and two mobile entries in an LDAP object. This is perfectly legal in LDAP.
However, when viewing this entry in Luma, only one of the entered values for these attributes is shown, so only one mobile and one homePhone value is visible. This is normal, because there is only one field available for this.
But if the Luma user changes something for that LDAP object (for example, add a note), the second (invisible) entry for mobile and homePhone are removed. Probably, this is because Luma rewrites all attributes when saving a change.