TIM Enterprise can synchronize its directory with Microsoft Azure and on-prem Active Directory, Cisco UCM, Avaya ACM and many others.
The entire directory - or just a selected portion - can be synchronized in this way, so your new installation will be ready-populated with all of your user data.
Whenever your users move around your organization, change their name, or leave, the system automatically keeps on top of that, so you don't need to.
You have full control over the frequency of when the changes are automatically updated, so it's literally a case of adding the synchronization, then forgetting about it.
TIM Enterprise automatically synchronizes its directory with your Microsoft Azure directory every 24 hours to ensure that all of your Teams user details are kept up-to-date.
The synchronization mechanism is read-only so you can never accidentally change your Azure Directory data from TIM Enterprise.
Because the access is read-only, you can group Teams users into separate groups on the TIM Enterprise side without affecting those users' group membership in Azure, which can be useful for comparing people from different Teams groups.
Synchronizing with your Active Directory structure allows TIM Enterprise to automatically populate its directory with the users stored by Active Directory.
The synchronization will pick up several properties from Active Directory including:
* Different organizations store the extension number in an arbitrary field so this can be changed during configuration.
When users are disabled/removed from Active Directory they are also disabled within TIM Enterprise to avoid using additional license.
Synchronizing with Cisco phone systems allows TIM Enterprise to automatically populate its directory with user and channel information.
Depending on the phone system different properties are available during the synchronization:
When synchronizing with a Cisco UCM TIM Enterprise uses the AXL API to collect various information related to phones, User Device Profiles, system devices (e.g. Hunt groups, UCCX ports, voicemail ports, conference bridges), and channels (e.g. Gateways and SIP trunks).
This information is cross referenced with End User profiles to allow the following properties to be picked up:
This synchronization also allows features based on the CDR that would not be possible with the CDR alone. Shared lines, for example, will pick up the primary extension of the user that received the call rather than showing only the shared line number. This allows for more accurate reporting.
Users that have their department changed will automatically be reassigned to their new department within TIM Enterprise, and if an extension is removed from the UCM, it will be disabled within the TIM Enterprise directory.
Synchronizing with a Cisco UCME will pick up the user properties from the UCME allowing the TIM Enterprise directory to auto populate. The Cisco UCME contains less information than the Cisco UCM but updates to names and extension numbers are picked up.
This synchronization also allows features based on the CDR that would not be possible with the CDR alone. Shared lines, for example, will pick up the primary extension of the user that received the call rather than showing only the shared line number. This allows for more accurate reporting users.
If an extension is removed from the UCME, it will be disabled within the TIM Enterprise directory.
Synchronizing with an Avaya IP Office allows TIM Enterprise to auto populate its list of users, extensions and hunt groups. Changes to the name and extension within the Avaya IP Office will be reflected with TIM Enterprise
If the extension is removed from the Avaya IP Office, will be disabled within the TIM Enterprise directory.