|
Auto Provisioning for phones or Cisco Extension Mobility allows for rapid service provisioning and fault free commissioning of every Cisco phone user in the enterprise based on the user's detail in Microsoft Active Directory. In conjugation with auto registered, logged out Cisco phones and Cisco Extension Mobility device profiles, the Cisco telephone system will no longer require highly trained experts for daily telephony MACD operations which allows them to concentrate on more advanced tasks. Even further, only a single job needs to be raised to a service desk to make changes to user AD accounts as the Uplinx Auto Provisioning for phones and Cisco Extension Mobility will handle all user telephony MACD operations based on changes to AD. Staff contact information in AD and the telephony environment will never be out of sycnhronization again! Administrative efforts and costs are minimal when telephony users are synchronised to Active Directory. Rapid service provisioning and fault free commissioning for every Cisco phone user is now available!
Features
Extension Mobility Auto Provisioning creates (automatically, or on approval by the site administrator) the following configuration objects based on user information in Microsoft Active Directory: CUCM end user with roles and associated devices and voicemail extension.Device Profile to login with Extension MobilityPhone with Extension or logged-out phone: Automatically configures auto registered phones according to model and location. There are no other steps involved other than plugging the phone in on a desk.Automatic, assigned or approved allocation of telephone number out of a site pool. Updating of Active Directory phone extension.Voicemail on Cisco Unity, Cisco Unity Connection or Microsoft Exchange (other 3rd parties server can be supported via a custom plugin)Presence on CUPS and Microsoft LyncUser information changes in Microsoft Active Directory are automatically detected and a workflow or auto provisioning activity for telephony users is then initiated. An email can notify the end user of their setup and how to use their telephony device and can also include attachments for training purposes. Before commissioning any new users on the relevant Cisco and Microsoft servers, the system can be configured to allow an administrator to approve the changes or alter the telephony profile. How it worksUplinx has extended the Uplinx Provisioning System to allow for fully automated Provisioning of Extension Mobility profiles based on the state of users defined in Microsoft Active Directory. 
CUCM end users, logged out phones and device profiles are now automatically provisioned (added, updated and deleted) based on defined enterprise rules when a change is detected. Changes to users in Microsoft Active Directory are automatically detected by the system and actioned, but can also be optionally approved by a telephony administrator. The Uplinx Change Tracker which is part of the Uplinx Provisioning System detects added, updated or deleted users and assigns a site and telephony class to this change. The system supports both multiple site deployments, and also multiple CUCM clusters. The system can be customized via the Uplinx WebGUI to accommodate a wide range of configuration options. Microsoft Exchange 2010 and Cisco Unity Connection/Enterprise are supported for voicemail. Cisco presence (CUPS) server and Microsoft Lync are supported in conjunction with device profiles for Extension Mobility. Cisco DirSync and AD authentication are supported. Any change can optionally be approved by an administrator before provisioning takes place and a workflow can be enforced by the system. Alternatively, changes can be made to Active Directory and then automatically reflected in a users Cisco Extension Mobility profile.
To facilitate Auto Provisioning, a filter and rule module maps AD user attributes to telephony classes which contain Cisco specific settings. CUCM users and device profiles are commissioned by using templates and telephony site specific definitions. (for example device pools or Calling Search Spaces). Automatic or predefined allocation of extensionsExtensions can be predefined in the AD user, assigned by a telephony administrator or automatically allocated from the site extension range. During commissioning the allocated extension will be updated in the Active Directory to reflect the commissioned extension of the device profile. This means that the phone or AD administrator do not need to worry about maintaining free phone extension lists. For more complex setups or if AD users cannot be classified, the telephony administrator can use the Uplinx Provisioning System console to select telephony specific settings such as site, extensions and calling permissions to complete the provisioning request. Documents
API-Integration
By using the Uplinx Provisioning System, an Enterprise can now easily extend any existing Enterprise Configuration Management (ECM) to include provisioning end users into their Cisco Telephony system. The Uplinx Provisioning System API and configuration platform offers a working API which allows submitting complex and complete provisioning operations within hours from any existing CMDB or ticketing systems. Other solutions require weeks or even months of software developer work for basic commissioning tasks and require a detailed understanding of the published Cisco internal APIs as well as laborious configuration and testing. By utilizing the Uplinx Provisioning system API, once users are provisioned in Microsoft Active Directory, one simple call to the Uplinx Provisioning System API can execute an add, update or delete all end user objects associated with an end user. The required templates and logic are easily configured on the Uplinx Provisioning System web interface and within hours the Provisioning System will be available to test all functionality. The API can then be used to:
|
|
Products |
Cisco telephony deployments which use phones or Cisco Extension Mobility can now automatically synchronize telephony details from Microsoft Active Directory.
