# What User Service Data is Synchronized?

You can synchronize the data listed in the table below. The table provides the following information:

- User Service Data - identifies the data in the MiVoice Business IDS application.

- LDAP Attribute - identifies the data in the directory server (defaults to Active Directory object names).

- Default Handling - determines the how the system handles queries with blank fields:

- None: No action (if a field is blank, it remains blank).

- Template: A User and Service Template provides the missing data, provided that the Role is provided. If no Role is provided, the default template is used.

- System: Default handling is determined by the system. If the User ID field is blank, the update is rejected and an error log is posted. If both the First Name and Last Name fields are blank, the update fails and is posted to the IDS Data management form with an "application error" status.

- Single-valued - indicates whether the LDAP attribute is normalized from a multiple-value field, into a single-valued field using the first value provided by the directory server.

- Global Catalog - indicates whether the LDAP attribute is contained in the GC partial attribute set. If possible, use LDAP attributes that are included in the GC in order to speed searches.

- Required Value - indicates whether the value must be set for the record to be accepted by the MiVoice Business IDS application.

Use the User Service Data to LDAP form to update the default LDAP attributes and default handling parameters. One record, "DistinguishedName," does not appear on the form because its LDAP attribute and default handling parameters cannot be modified.

User Service Data Field | Default LDAP Attribute | Default Handling | Single Valued | Global Catalog | Required Value | Notes
First Name | givenName | System Defined | Yes | Yes | Yes | At least one name, either first or last, is required. The handling cannot be modified.
Last Name | sn | System Defined | Yes | Yes | Yes
User ID | ObjectGUID | System Defined | Yes | Yes | Yes | The handling cannot be modified.
Department | department | Template | Yes | No | No | You can change the LDAP attribute for this record and/or add it to the GC partial attribute set.
Location | physicalDeliveryOfficeName | Template | Yes | No | No | You can change the LDAP attribute for this record and/or add it to the GC partial attribute set.
Language | preferredLanguage | Template | Yes | No | No | You can change the LDAP attribute for this record and/or add it to the GC partial attribute set.
Role | employeeType | None | Yes | No | No | You can change the LDAP attribute for this record and/or add it to the GC partial attribute set. If a role is provided, the associated User and Service Template is used to complete the user data. If no role is provided, the default template is used.
Directory Number | telephoneNumber | None | Yes | Yes | No | You can change the LDAP attribute for this record.
Home Element | ipPhone | None | Yes | Yes | Yes (if DN is configured) | You can change the LDAP attribute for this record.
Secondary Element | otherIpPhone | None | No | Yes | No | You can change the LDAP attribute for this record.
Email | mail | None | Yes | Yes | No | You can change the LDAP attribute for this record.

Related Topics

- About IDS

- IDS Forms