Cisco Prime Collaboration Provisioning Guide - Standard and Advanced, 10.0
Managing Devices
Downloads: This chapterpdf (PDF - 1.18MB) The complete bookPDF (PDF - 6.23MB) | Feedback

Managing Devices in Prime Collaboration Provisioning

Managing Devices in Prime Collaboration Provisioning

This chapter contains the following topics:

Managing Devices Overview

To use Provisioning, you must first add the IP communications infrastructure devices that are part of your IP telephony environment.

After adding devices, you synchronize the data in Cisco Unified Communications Manager, Cisco Unity systems, and Cisco Unified Presence with Provisioning. This populates Provisioning with the existing active users and services, and provides a consolidated view of all of the infrastructure and user information.

Provisioning also provides support for Cisco IOS routers. When a Cisco IOS router device is added to Provisioning, it appears in Provisioning as a Generic IOS Router. Through the Generic IOS Router capability, Provisioning can configure additional voice functionality on the router.

Call Processors are proxies for each instance of a Cisco Unified Communications Manager or Cisco Unified Communications Manager Express device. Unified Message Processors are proxies for each instance of a Cisco Unity, Cisco Unity Express, or Cisco Unity Connection device. Unified Presence Processors are proxies for each instance of Cisco Unified Presence. You will find these terms used in place of their respective devices.

Adding Devices

You must add devices to Provisioning to provision services for users. For a list of devices you can add to Provisioning, see Supported Devices for Prime Collaboration Provisioning - Standard and Advanced, 10.0.

Note the following points while you are adding a device to Provisioning:

  • Before you add devices to Provisioning, you must make sure the Cisco Unified Communications Manager, Cisco Unified Communications Manager Express, Cisco Unity, Cisco Unity Connection, Cisco Unity Express devices are configured correctly. For details on configuring these devices, see Setting Up Devices for Prime Collaboration Provisioning.
  • There are some significant differences in how a Generic IOS Router is set up in Provisioning in comparison to a Cisco Unified Communications Manager or a Cisco Unity device. Most notably, Generic IOS Routers are not synchronized and they are not associated to a Domain or a Service Area.
  • Before you can create a Call Processor based on a Cisco Unified Communications Manager Express in Provisioning, you must:
    • Disable the auto-allocation of directory numbers. Do this through the Cisco IOS interface.
    • Disable the ephone auto-registration for Cisco Unified Communications Manager Express.

To add devices to Provisioning:

Procedure
    Step 1   Choose Design > Infrastructure Setup.
    Step 2   In the Infrastructure Setup page, Click Add to add devices to Provisioning.
    Step 3   In the Add Device window, select the required application from the drop-down list and enter the necessary information such as Name, IP address and so on. See the tables below for field descriptions.
    Note   

    For the device name, valid values are space, alphanumeric characters (A-Z, a-z, 0-9), underscore (_), hyphen (-), period (.), and at sign (@).

    Step 4   Click Save.

    Devices are added to Provisioning. You will see two status messages appearing at the bottom of the page. One on whether the addition of the device was successful or not, and another on the Test Connection stating whether the connectivity test was successful or not . Devices with multiple applications are added as separate devices in the table.

    Note    While adding Cisco Unity Connection 10.0, you must configure both Unity Connection administrator and Operating System (OS) administrator credentials.

    To view the details of the device, hover over Quick View. You can start synchronization, view synchronization logs, test the connectivity of the device, and cross launch Cisco Unified CM Serviceability and Cisco Unity Connection Serviceability from Quick View.

    To update or change the device details, click Edit.

    To import devices from Prime Collaboration Assurance, click Import. The Device Setup page lists the devices in Assurance (devices that are in managed state only appear in the list). Select the device you want to import and click Import Selected Devices.


    Note


    • You can import devices from Assurance in converged mode only.
    • You cannot import a device that already exists in Provisioning.
    • You cannot import Cisco Unified Communications Manager Express and Cisco Unity.

    Some devices have more than one application on it (devices with same IP address). If you are adding devices with more than one application on it, add the first device and save it. After the device is successfully added to Provisioning, add the device again, selecting the second application. Save the device. Both the devices will appear in the Device Setup table.

    You can add Prime License Manager and Deployment Manager from the Infrastructure Setup page. After you add these devices, Prime License Manager and Deployment Manager links are displayed under the Administration menu. Click on the Prime License Manager or Deployment Manager link to cross launch the Prime License Manager or Deployment Manager login page.

    Note


    You can add only one Prime License Manager and Deployment Manager device to Provisioning. If you try to add another Prime License Manager or Deployment Manager device, an error message will be displayed.


    Table 1 Call Processor Fields

    Field

    Description

    LDAP Integration

    Options are None, Synchronization, Synchronization, and Authentication. The value you choose must exactly match the value configured in Cisco Unified Communications Manager. If Cisco Unified Communications Manager is integrated with an external LDAP, users are not created through Provisioning; instead they are synchronized through Cisco Unified Communications Manager.

    While provisioning a service, if a user is not available on Cisco Unified Communications Manager, the workflow subsystem waits for a predefined period of time (24 hours by default) for the user to be available on Cisco Unified Communications Manager and then continues provisioning the service.

    The 24-hour period can be configured on Provisioning in the ipt.properties file. Change the following settings:

    • dfc.oem.extdir.retries: 24
    • dfc.oem.extdir.retry_interval: 3600
      Note   

      LDAP integration is available only for Cisco Unified Communications Manager versions 5.0 and later.

    Extension Mobility Details (Optional)

    Service Name

    The name of the Extension Mobility Service configured on a Call Processor.

    Service URL

    The URL of the Extension Mobility Service configured on the Call Processor:

    http://<ip-address>/emapp/EMAppServlet?device=#DEVICENAME#

    Where ip-address is the name or the IP address of the server where Extension Mobility is installed.

    Note   

    The Service Name and Service URL you enter in Provisioning should match the Service Name and Service URL in Cisco Unified Communications Manager.

    Table 2 Unified Message Processor Fields

    Field

    Description

    LDAP Integration

    Note   

    This option is available only for Cisco Unity Connection.

    Specifies whether Cisco Unity Connection is integrated with an external LDAP.

    If you select Yes, while provisioning voicemail account, Provisioning will search the LDAP users list in Cisco Unity Connection. If the user name is found in the list, it will import the user details and provision a voicemail account.

    If you select No, Provisioning will not search the LDAP users list and will follow the normal process for provisioning voicemail account.

    Username

    This field is case-sensitive. The username supplied in this field should match the following:

    • Cisco Unity—Database password.
    • Cisco Unity Connection—Any user with Cisco Unity Connection administrator privileges.
    • Cisco Unity Express—Username of the router where Cisco Unity Express is installed.

    Password

    This field is case-sensitive. The password supplied in this field should match the following:

    • Cisco Unity—Database password.
    • Cisco Unity Connection—Administrator password.
    • Cisco Unity Express—Password for the router where Cisco Unity Express is installed.
    OS Administrator Name
    Note   

    This option is available only for Cisco Unity Connection 10.0.

    The OS administrator name is created during the installation of Cisco Unity Connection.

    OS Administrator Password
    Note   

    This option is available only for Cisco Unity Connection 10.0.

    The OS administrator password is created during the installation of Cisco Unity Connection.

    Enable Password

    Enable password for the router where Cisco Unity Express is installed.

    Create by Import

    Indicates whether a new account should be created on an Exchange server for new voicemail accounts created in Cisco Unity.

    If selected, creating user accounts on the Exchange server is prevented. User accounts are associated only if they already exist on the Exchange server.

    (Optional) Line User Name

    Username for the Cisco Unity Express module.

    Line User Password

    Password for the Cisco Unity Express module.

    Service Engine Interface Number

    The interface number of the Cisco Unity Express service engine on the router.

    Table 3 LDAP and ACS Server Configuration Fields

    Field

    Description

    LDAP Server Type

    Type of LDAP server.

    The following options are available:
    • Microsoft AD server or Microsoft ADAM (Active Directory Application Mode)
    • Lightweight directory services

    For information about the Microsoft AD versions supported by Provisioning, see http:/​/​docwiki.cisco.com/​wiki/​Supported_​Devices_​for_​Cisco_​Prime_​Collaboration_​Provisioning_​10.0

    Backup Server Port

    Port number for the backup AAA server.

    Admin Distinguished Name

    The administrative user ID of the LDAP manager that has access rights to the LDAP directory.

    Admin Password

    The administrative users password (LDAP manager).

    LDAP User Search Base

    The user search base. Provisioning searches for users under the base, CN=Users, DC=Cisco,DC=com.

    Use SSL

    You should check this check box if Provisioning should use Secure Socket Layer (SSL) encryption for the transmission channel between Provisioning the AAA server.

    ACS Authentication Protocol

    Protocol used by the ACS server for authentication.

    Enable Data Encryption

    Enables data encryption between Provisioning and the ACS server.

    Working with Cisco Unity Connection Device

    For Cisco Unity Connection clustering and failover support, be aware of the following:

    • When adding a Cisco Unity Connection that includes a Cisco Unity Connection cluster server pair, add only the publisher server of the pair.
    • If the primary Cisco Unity Connection fails over to a secondary Cisco Unity Connection, you can change the IP address to the secondary device, and Provisioning will communicate with the secondary device before failback occurs.

    If a network has more than one location, individually add all of the locations for either the Cisco Unity Connection server or Cisco Unity Connection cluster to Provisioning.

    If Cisco Unity is used in the configuration, configure the Cisco Unified Communications Manager voicemail ports.

    For more information on these devices, see Setting Up Devices for Prime Collaboration Provisioning.

    Prime Collaboration Provisioning allows an administrator to cross launch Cisco Unity Connection Serviceability and Cisco Unified Serviceability from the configured Cisco Unity Connection and Cisco Unified Communications Manager respectively.


    Note


    Cross launching serviceability is supported for Cisco Unified Communications Manager and Cisco Unity Connection devices only.


    When you cross-launch serviceability, you can access the serviceability UI and perform any operation directly on the server of that device. To learn about serviceablity in CUCM, refer the Cisco Unified Serviceability Administration Guide, Release 10.0. Similarly, to learn about serviceability in Cisco Unity Connection, refer the Administration Guide for Cisco Unity Connection Serviceability Release 10.0.

    With the cross-launching serviceability feature, Prime Collaboration Provisioning facilitates you to activate, deactivate, start and stop services (directly) on all managed nodes. Rest your mouse pointer over Cisco Unified Communications Manager or Cisco Unity Connection in the device table, and click the quick view icon to view theServiceability cross launch link under the Actions pane.

    Adding Cisco TMS

    You can enable scheduling for video endpoints by adding a Cisco TMS device that synchronizes with Cisco Unified Communications Manager to discover devices. Note that the scheduling is executed only in Cisco TMS and you can launch the scheduling UI from Prime Collaboration Provisioning.

    Procedure
      Step 1   Add Cisco TMS (see the procedure on Adding Devices).
      Step 2   Associate an application user to Cisco TMS. For each Cisco Unified Communications Manager that you want to provision, you can select the application user to be associated with Cisco TMS. Choose Deploy > Unified Communication Services. Under TMS Service, select an application user for a Cisco Unified Communications Manager, and click Apply.

      Note that the application user must belong to these groups: Standard CCM Admin Users and Standard CTI Enabled

      and have the one of the following roles:

      Standard AXL API Access, Standard CCM Admin Users, Standard CTI Enabled, Standard CUReporting, Standard RealtimeAndTraceCollection, Standard SERVICEABILITY

      Step 3   Provision an endpoint. See Provisioning Services for Users.To enable scheduling: In the Service Specific Configuration Layout, click Enable Scheduling.
      The endpoint is added and provisioned on the Cisco Unified Communications Manager for an application user that is associated to the specific Service Area.
      Note   

      When you create a new order for an endpoint, you could have many services pointing to different Cisco Unified Communications Managers. In this case, you must select the Service Areas applicable for the respective Cisco Unified Communications Manager (under Unified Communication Services).


      Deleting Devices

      To completely remove a device from Provisioning, you must delete it through the Infrastructure Setup page. Note the following points when you are deleting a device:

      • No active released orders, including unrecoverable or recoverable errors.
      • No active batch projects.
      • No synchronizations in progress. If these conditions are not met, a message appears on the page when you attempt to delete a device. Avoid performing any activities until the deletion is complete.
      • Before deleting a AAA server, make sure it is not assigned to a Domain.
      • There must not be any pending orders on the device. You do not need to be in maintenance mode to delete the device capability. However, if another capability is already configured on the router, system must be in maintenance mode to remove the other capability.
      • Before deleting a device, make sure that:
      To delete devices:
      Procedure
        Step 1   Put Provisioning in maintenance mode. (See Maintenance Mode.)
        Step 2   Choose Design > Infrastructure Setup.
        Step 3   In the Infrastructure Setup page, select the device you want to delete and click Delete.
        Step 4   In the confirmation dialog box, click OK to confirm deletion.

        Enabling Cisco Jabber Services

        You can enable Cisco Jabber services for devices in Prime Collaboration Provisioning. Cisco Jabber services allow you to interact with instant messaging and presence.


        Note


        Cisco Jabber service is available for Cisco Unified Communications Manager 9.1.1 and above version, and Cisco Unified Presence only.


        To enable Cisco Jabber service for a call processor:

        Procedure
          Step 1   Choose Deploy > Unified Communication Services.
          Step 2   In the Unified Communication Services page, click Enable.
          Step 3   Enter the SIP Profile, Service Profile, Softkey template fields and Service Parameter information, and click Apply. See Infrastructure Configuration Product Fields for information on these fields. You can click View Order to see the order details in the User Record page. The date when the Jabber Service is enabled is displayed.
          Note   

          Once you enable Cisco Jabber service for a call processor, you cannot edit or disable it.