Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Last Updated: April 2016 Cisco TMSPE 1.7 Cisco TMS 15.2.1 Cisco VCS X8.5 TelePresence Conductor XC 4.2 Cisco Systems, Inc. www.cisco.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 2
Contents Introduction 11 This Deployment Guide 11 Related Documents 11 Prerequisites and Recommendations 13 Estimating Your Deployment Size 13 Hardware Requirements 14 Regular Deployment and Cisco Business Edition 6000 14 Large Deployment 14 Recommended Hardware and Virtualization for Large Deployments 15 Cisco TMSPE server software and configuration requirements 16 SMTP server requirements 17 SQL Server software and permission requirements 17 Cisco VCS requirements 17 Cisco Collab
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Browser requirements 20 Administrator interface 20 User portal 20 Licensing requirements 20 Best practices for deployment 21 Upgrade endpoints to the latest software 21 Automate user creation and management with AD/LDAP 21 Use secure communication 21 Synchronize time in Cisco VCS and Cisco TMS 22 Multiparty Licensing 22 Configuring Cisco VCS for Provisioning 22 Provisioning Within Your Network
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Creating Address Patterns 39 Address Pattern Types 39 Adding the Patterns 40 Example Patterns 41 Setting up Configurations for Provisioned Devices 42 Obtaining Template Schemas 42 Uploading the Schema to Cisco TMS 43 Adding Configuration Templates 44 Assigning Configuration Templates to Groups 47 Provisioning Phone Books 48 Creating and Configuring Provisioning Phone Book Sources 48 Associating
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Setting up Host and Guest Roles in CMRs 63 Host Privileges 63 Allowing the Guest Role 64 Disallowing the Guest Role 64 Including WebEx Participants in CMR meetings 64 Before you start 64 Enabling WebEx in CMRs 65 Making Changes that Affect Collaboration Meeting Rooms 65 Modifying or Replacing the Template for a Group 65 Deleting Templates 66 Deleting Users 66 Moving Users Between Groups 66 Tou
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Including the ISDN Gateway Prefix in the Caller ID 78 Regenerating FindMe Locations and Devices 78 Accounts and Groups 79 Location Templates 79 Device Templates 79 Modifying a User's FindMe Locations and Devices 79 Additional Information 80 Determining How to Overwrite a Caller ID with a FindMe ID 80 FindMe in a Cisco VCS Cluster 80 FindMe Accounts Hosted on Hifferent Cisco VCSs in a Network 81 Fi
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Running a health check 89 Viewing system status 89 Viewing Cisco VCS Communication History 90 Restarting the TMS Provisioning Extension Windows Service 90 Logs 90 Cisco TMSPE and Cisco TMS Logs 90 Cisco VCS Logs 91 Endpoint Logs 91 Troubleshooting the Installation 91 Checking the Installation Log 91 Unable to Establish SQL Connection Through Java Runtime...
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Cisco Trademark 98 9
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 10
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Introduction Cisco TMS Provisioning Extension (Cisco TMSPE) is an application for Cisco TMS that offers the following features for telepresence users and administrators: ■ Large-scale provisioning of telepresence users through Cisco TelePresence Video Communication Server (Cisco VCS). ■ FindMe, a user-configurable, Cisco VCS-based telepresence call forwarding feature.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Training Training is available online and at our training locations. For more information on all the training we provide and where our training offices are located, visit www.cisco.com/go/telepresencetraining Glossary A glossary of TelePresence terms is available at: tp-tools-web01.cisco.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Prerequisites and Recommendations This section describes prerequisites and best practices for installing and deploying Cisco TMSPE with Cisco TMS and Cisco VCS. Estimating Your Deployment Size The requirements for Cisco TMS depend on and grow with the size and complexity of the deployment.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Other factors that influence Cisco TMS performance and scale include: ■ The number of users accessing the Cisco TMS web interface. ■ Concurrency of scheduled or monitored conferences. ■ The use of ad hoc conference monitoring. ■ Simultaneous usage of Cisco TMSBA by multiple extensions or custom clients. Booking throughput is shared by all scheduling interfaces including the Cisco TMS New Conference page.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide When planning for a large deployment, also keep in mind that: ■ The disk space needed for a large tmsng database is typically 20-30 GB. ■ The size of the three Cisco TMSPE databases will not exceed 6 GB in most deployments. ■ The prime performance limiters in SQL Server are RAM and disk I/O. For optimum performance, increase these values as much as possible.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Microsoft SQL Server Virtual Machine CPU 4 x vCPU Memory 16 GB Disk 250 GB Cisco TMSXE Virtual Machine CPU 4 x vCPU Memory 8 GB Disk 100 GB Cisco TMSPE server software and configuration requirements Cisco TMSPE must be installed on the same server as Cisco TMS. Product Cisco TMS Version and description ■ Cisco TMSPE 1.7 requires Cisco TMS 15.1.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide No support for multiple network cards Multiple network cards on the Cisco TMS server are not supported. Cisco TMSPE cannot use multiple network cards on a server and will only bind to the first available network interface. SMTP server requirements Cisco TMSPE requires a valid SMTP server that will accept SMTP relay from the Cisco TMS server to send account information to users from Cisco TMSPE.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide ■ one or more WebEx sites ■ WebEx credentials for each user (not service user), either manually added or using WebEx/Cisco TMS single sign-on For guidance on setting up Cisco Collaboration Meeting Rooms Hybrid with or without single sign-on, see Cisco Collaboration Meeting Rooms Hybrid Configuration Guide. Collaboration Meeting Room requirements Cisco TelePresence Conductor Cisco TelePresence Conductor XC3.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide ■ used to book on behalf of Smart Scheduler users in Cisco TMS. Every time a meeting is booked or updated, an email notification will be sent to this user as well as to the meeting owner. If you do not want this email sent to the service user, the user must be set up without an available email address.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide ■ Active Directory ■ Active Directory with Kerberos ■ Lightweight Directory Access Protocol (LDAP) Service account You must define a service account in Active Directory that has read access to the Global Catalog. This service account must have a password with no retention policies applied to it so that the password does not expire.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Feature License requirement User synchronization with Active Directory None Collaboration Meeting Rooms No license required in Cisco TMS. One or more of the following required: Smart Scheduler Device provisioning FindMe ■ Screen licenses on TelePresence Server. ■ Appropriate MCU port licenses. ■ Shared Multiparty License / Personal Multiparty License on Conductor.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Synchronize time in Cisco VCS and Cisco TMS Keep time synchronized between Cisco TMS and Cisco VCS. We recommend configuring them to use the same NTP (Network Time Protocol) server : ■ To configure the NTP server in Cisco VCS, go to System > Time. ■ Cisco TMS uses the NTP setting for the host Windows Server operating system.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Control or the VCS Expressway), we recommend that you configure and enable provisioning only on the VCS Control (or VCS Control cluster). If a soft client or other endpoint registers to a VCS Expressway, provisioning requests will be routed (using search rules) to the VCS Control associated with the VCS Expressway via the appropriate traversal zone.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Enabling SIP SIP must be enabled on each VCS Control and VCS Expressway in the network: 1. Ensure that SIP mode is turned on (Configuration > Protocols > SIP). This is enabled by default. 2. Ensure that at least one SIP domain is specified (Configuration > Domains).
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Adding Cisco VCS to Cisco TMS This procedure is compulsory for the Cisco VCS (or Cisco VCS cluster) on which provisioning is enabled (typically the VCS Control), and optional for other Cisco VCSs (a VCS Expressway, for example). In each Cisco VCS: 1.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 3. Click the Add Systems button in the right pane. Follow the instructions in Cisco TMS to add the Cisco VCS. 4. Enter the FQDN of the Cisco VCS, for example vcs1.example.com, and click Next. Cisco TMS will collect information from the VCS about how best to communicate with it.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Enabling Presence on the Cisco VCS Endpoints such as Jabber Video can use Cisco VCS as a presence server to share presence information (for example Offline, Online, Away, or Busy) with other users. ■ You must only enable presence on a single Cisco VCS or Cisco VCS cluster per SIP domain in your deployment. ■ Enabling Presence is optional. Presence on VCS Control 1.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Verifying Device Authentication The Cisco VCS's Provisioning Server requires that any provisioning or phone book requests it receives have already been authenticated at the zone or subzone point of entry into the Cisco VCS. The Provisioning Server does not do its own authentication challenge and will reject any unauthenticated messages.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Installing Cisco TMSPE This section covers the process of installing or upgrading Cisco TMSPE. Installing Cisco TMSPE with a Redundant Cisco TMS Setup When installing Cisco TMSPE to a redundant Cisco TMS deployment using a network load balancer, the extension must be installed on all servers. The general installation instructions apply, with some exceptions. The overall process is as follows: 1.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Performing a New Installation To install: 1. Ensure that all critical Windows Updates are installed on your server. 2. Close all open applications and disable virus scanning software. 3. Extract the Cisco TMSPE installer from the zip archive to the Cisco TMS server. 4. Run the Cisco TMSPE installer as administrator. 5. Follow the setup instructions: a. Click Next to initiate the setup. b.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 3. Verify that Cisco TMSPE features are now available and functioning. a. Browse to the following pages in Cisco TMS: • Systems > Provisioning > Users. If this page reports a problem connecting to User Repository, the database connection is not working. See Troubleshooting the Installation, page 91.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 4. Adjust the connection settings according to your telepresence infrastructure. — The default and recommended Encryption setting is TLS, see Use secure communication, page 21. If opting not to use secure communication, make sure to change this setting to Off, or the connection will be refused. If enabling encryption, also select whether to check for a valid certificate and certificate hostname.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Table 1 Settings on the Provisioning tab Field and buttons Description Save Save the settings Force Refresh Sends the current settings available in Cisco VCS page, as the same settings on the Cisco VCS UI must be same as seen in Cisco TMS. Set Default Connection Settings Set default connection settings.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 34
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Setting up Users and Provisioning This section describes the required procedures to configure Cisco TMSPE for provisioning. Creating Groups and Adding Users Users can be added to Cisco TMSPE by importing from an external directory, or manually adding individual users. Before users can be added, you must set up a group hierarchy.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 1. In Cisco TMS, go to Systems > Provisioning > Users. 2. In the Users and Groups container, navigate to and click the group into which you want to import user accounts. Information about the selected group is displayed in a number of panes. 3. In the User Import pane, click Configure. 4. If you want to copy user import settings from the parent group as a starting point, click Copy from parent. 5.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 6. In the fields provided, specify the information that Cisco TMSPE requires to contact the external directory. Configure the fields according to the following table: Field Active Directory (AD) Active Directory with Kerberos (Secure AD) Lightweight Description Directory Access Protocol (LDAP) Hostname Yes Yes Yes Server hosting the external directory. Provide a fully qualified domain name (FQDN).
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Field Active Directory (AD) Ignore No certification errors Active Directory with Kerberos (Secure AD) Lightweight Description Directory Access Protocol (LDAP) No Yes Select Yes or No. 7. Click Save. For detail on mapping of Active Directory and LDAP fields to Cisco TMSPE attributes and instructions on performing manual synchronization, see Synchronizing User Data, page 83.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 3. Modify the settings as desired: — Connection Timeout in milliseconds — Filter Template will be applied to all group imports. The %s variable in the template will be replaced by any Search Filter set for a group import. 4. Click Save. Adding Users Manually The alternative to importing user accounts from external directories is to add user accounts manually.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Adding the Patterns To create a device address pattern, a video address pattern, and optionally an image url pattern: 1. In Cisco TMS, go to Systems > Provisioning > Users. 2. In the Users and Groups container, navigate to and click the group to which you want to assign a device address pattern. 3. In the User Settings pane, click Edit. The User Settings dialog box opens. 4.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 5. In the Device Address Pattern field, specify the pattern that you want Cisco TMSPE to use when creating names of provisioned devices. You can use any of the above listed user attributes in the pattern. You can also use any of the following device attributes in the pattern: — {device.model} This resolves to the device model; for example, e20, movi, ex90. — {device.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Advanced Parameters (Regex) When working with user setting (Video Address Pattern, Caller ID Pattern, Device Address Pattern) and when edit or creating CMR templates (SIP Alias Pattern) you have the option to use regex to remove or change the value of these field. All these fields uses fields from AD/LDAP. You can use as many regex replacements as you need.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Uploading the Schema to Cisco TMS 1. In Cisco TMS, go to Systems > Provisioning > Users. 2. On the Users page, click the Configuration Templates container. Folders are displayed representing models and versions of devices for which template schemas have already been uploaded. 3. In the Configuration Templates container, click Add schema. The Upload Template Schema dialog box opens. 4.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Adding Configuration Templates A configuration template specifies the collection of configurations that you choose to assign to groups of users. The configurations that you choose from are defined in the associated template schema (see Obtaining Template Schemas, page 42).
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 4. Add configurations in either of the following ways: — Copy configurations from an existing template: 1. Above the Configurations pane, click Copy Configurations. The Copy Configurations dialog box opens.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 2. Select the template from which you want to copy all configurations, and then click Copy. The Status field reports the result of the copy. The number of successfully copied configurations is displayed, as well as the number that failed to copy, for example, due to the target template's schema not supporting the same keys as the originating template's schema. 3. Click Close.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide — Add individual configurations: 1. In the Configurations pane, click Edit configurations. The Edit Configurations dialog box opens. 2. Select the Configure check box for each configuration that you want to add to the template, and then select or enter a value in the Value field. 3. Click Save to save your settings. The configurations you have added are displayed in the Configurations pane.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 2. Click Assign templates. The Assign Templates dialog box opens. 3. Select the check box for each configuration template that you want to assign to the group. 4. Click Save. Provisioning Phone Books You do not set phone books to provisioned endpoints the same way as with Cisco TMS-registered endpoints. The Phone Book URI you configure for groups, for example phonebook@example.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 1. In Cisco TMS, go to Phone Books > Manage Phone Book Sources. 2. In the right-hand pane, click New. 3. In the Name field, add a descriptive name for the new source. 4. From the Type drop-down menu, select Cisco TMS Provisioning Directory. 5. Click Save. Follow procedure below to modify the configuration of the new provisioning source, including its root directory.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide To associate phone book access to a group: 1. In Cisco TMS, go to Phone Books > Manage Phone Books, and then in the Directory pane, click the required phone book. Information about the selected provisioning phone book is displayed in the Workspace pane. 2. In the Workspace pane,click the Access Control tab. 3.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 1. In Cisco TMS, go to Administrative Tools > Configuration > Provisioning Extension Settings. 2. In the Account Information Email pane, configure the fields as follows: Sender Address Email address Cisco TMSPE uses as the sender email address when sending email notifications. The address appears in the From field of the recipient's email client Subject Subject of the email notifications.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 4. Click Save. If you import users from Active Directory and choose to enable automatic email sending, you do not need to follow the procedures below. Sending Account Information to a Single User We recommend sending account information to a single user as a test, for example your own account, prior to sending account information to a large group of users: 1. In Cisco TMS, go to Systems > Provisioning > Users. 2.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 1. In Cisco TMS, go to Systems > Provisioning > Users. 2. In the Users and Groups container, navigate to and click the required group. Information about the selected group is displayed in a number of panes. 3. In the area above the User Settings pane, click Send Account Information. A confirmation prompt is displayed. 4. Confirm that you want to send account information to all users in the group.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Smart Scheduler is a part of the Cisco Collaboration Meeting Rooms Hybrid solution, allowing users to set up telepresence meetings with and without WebEx. Users can book: ■ Telepresence rooms Any bookable system in Cisco TMS can be scheduled directly. ■ Call-in participants Any system that is not supported by Cisco TMS booking can be scheduled as a call-in participant, including devices provisioned by Cisco TMSPE.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide ■ When a service user is performing all bookings, the booking permissions are the same for all users. Individual permissions and restrictions in Cisco TMS are ignored. ■ Meetings in the past cannot be changed or deleted, and you cannot move a meeting from the past to the future. ■ If sufficient system licenses are not available at the time of editing an existing booking, the booking will be deleted.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Access Rights and Permissions For the user to be able to access the Smart Scheduler, the permission must be set for the user . 1. Go to Administrative Tools > User Administration > Groups >. 2. Select Group. 3. Click Set permissions. 4. Go to > Booking > Misc. 5. Check Booking.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 3. The Cisco TMS user entered during installation of Cisco TMSPE is the service user for Smart Scheduler. This user creates the booking in Cisco TMS on behalf of the Cisco TMSPE user. If the Cisco TMSPE user does not already exist in Cisco TMS, it will be created at the same time as the booking. 4. When the booking is complete, Cisco TMS sends an email confirmation to the user who booked the meeting.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide template determines the address pattern and available parameters for each user's CMR. ■ Applies required template to groups. You can only apply one template per group. When notified by the administrator that the CMR service is available, each user can initiate the creation of their own CMR on their TelePresence User Portal page.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide On each TelePresence Conductor to be connected with Cisco TMSPE: 1. Go to Users > Administrator accounts. 2. Click New. 3. Add a new user exclusively for Collaboration Meeting Rooms, with the following settings: — Access level: Read-write — Web access: No — API access: Yes — State: Enabled 4. Click Save. In Cisco TMS: 1. Go to Systems > Provisioning > Users. 2.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 3. Fill in the settings: Table 2 Collaboration Meeting Room template configuration fields Field Description Template Name Assign a descriptive name to each template to ease the selection and maintenance of templates as the list grows. For example, include a descriptor for video quality, geographical location, or other signifier that clearly conveys what the template does.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Table 2 Collaboration Meeting Room template configuration fields (continued) Field Description Number Ranges Enter one or more number ranges to use for the numeric aliases. Ranges must be written with a hyphen and no spaces, and multiple ranges must be separated by commas. Note that: — Both parts of the range must contain the same number of digits. For example, 01-99 will work, but 1-99 will not .
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Table 2 Collaboration Meeting Room template configuration fields (continued) Field Description Maximum Content Quality From the range of available qualities for content (presentation) sharing, select the maximum quality that users will have access to.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Table 2 Collaboration Meeting Room template configuration fields (continued) Field Description Allow Cascading Choose whether to allow the user of this CMR to seamlessly expand an ongoing meeting if there is an available bridge in your environment. This requires reserving one or more bridge ports or connections for cascading, which will always be available to the CMRs defined by this template.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide A PIN may be required for them to join, depending on the configurations made by the administrator and the CMR owner. Depending on the bridge used, participants connecting as guests may be required to wait until a host joins the meeting before they will be allowed into the CMR. ■ Cisco TelePresence MCU Series: guests must always wait for a host to join.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide ■ To prevent potential toll fraud issues, we recommend disabling Call-back teleconferencing on the WebEx site that is used for CMRs. Enabling WebEx in CMRs You must enable WebEx for CMR before you can include the feature in one or more templates: 1. In Cisco TMS, go to Administrative Tools > Configuration > Provisioning Extension Settings. 2. Under Collaboration Meeting Room, set Allow WebEx Connections to Yes. 3.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 4. Repeat the previous steps for any other templates that need modifying. 5. When all template changes are completed, the counter next to the Check sync status button will let you know how many rooms are currently out of sync with the modified templates. Click the Regenerate CMRs button to synchronize.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Auto-connected Participants Users can use the Favorites feature to add a recording alias as an auto-connected participant that will be connected whenever a new meeting is initiated in the CMR. Auto-connected participants can also be used for adding other participants in support of different scenarios, such as: ■ The user's own endpoint– to avoid the user having to wait in their own meeting for others to join.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Deploying FindMe FindMe is an integrated, but optional part of Cisco TMSPE. Provisioning and FindMe can be deployed separately or together. FindMe can also be added to a Cisco TMSPE deployment at any time. FindMe Basics FindMe provides the ability to specify which endpoints (video and audio-only) should ring when someone calls a user's FindMe ID.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 3. In the User Settings pane, click Edit. The User Settings dialog box opens. 4. In the Caller ID Pattern field, specify the pattern that you want Cisco TMSPE to use to define callback numbers for users in the selected group, or the explicit callback number for the selected user. You can use any of the following user attributes in the pattern: — {office_phone} — {mobile_phone} 5. Click OK.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide ■ Groups will not be added if they do not have a video address pattern defined. ■ Users without video addresses, either manually configured or based on their group's video address pattern, will not be added. See Creating Address Patterns, page 39 for further instructions on video address patterns. To enable FindMe: 1.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 1. In Cisco TMS, go to Systems > Provisioning > FindMe. 2. In the Accounts and Groups container, navigate to the group into which you want to add an account. 3. Above the explorer view, click Add Account. The Add Account dialog box is displayed. 4. Configure the fields as follows: Display Name Display name for the account. Username Username for the account. FindMe Address The FindMe ID for the account.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 2. Above the explorer view, click Add Device Template. The Add Device Template dialog box is displayed. 3. Configure the fields as follows: Display Name The FindMe device name; for example, E20. Device Type The picture to display. Select from the following: — Video Endpoint — Telephone — Mobile Phone — Laptop — Person — Voice Mail.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Adding FindMe location templates The endpoint devices available to FindMe users may vary depending on their current location. You can add location templates to represent these variations. For example, use location templates to represent different physical locations such as "home" or "office", as well as different circumstances such as "on vacation" or "in a meeting". To add FindMe location templates: 1.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide ■ If the designated default devices are busy. ■ If a call is not answered within the location's configured ring duration. To associate devices to a location: 1. In Cisco TMS, go to System > Provisioning > FindMe, click the Location Templates container, and then in the explorer view, click the location template to which you want to assign a device template. 2. In the Device Templates pane, click Assign Templates.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 4. Click Save. Assigning Location Templates to Groups When you assign location templates to a group and apply them by regenerating the group's locations and devices, the information is passed on to and used by the configured VCSs. The location templates also becomes visible to all users in the group the next time they access their user portal. Locations are also inherited by all users in subgroups.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 6. Click Save. 7. Click Regenerate Locations and Devices... to apply the templates for all accounts and subgroups in the current group. See Regenerating FindMe Locations and Devices, page 78 for details. Note that while you cannot assign templates directly to single users/accounts, you can access the FindMe portal on their behalf and modify their locations and devices.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 3. We recommend that you set Caller ID to FindMe ID. The options are: — FindMe ID : the caller ID of a call being made through this Cisco VCS is replaced with the relevant FindMe ID. — Incoming ID: the caller ID is not altered; the caller ID presented to the called endpoint will be the ID of the endpoint initiating the call.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Full configuration and implementation details for ENUM are described in ENUM dialing on Cisco VCS Deployment Guide. Including the ISDN Gateway Prefix in the Caller ID It is easier to return a PSTN / ISDN call that has been received through an ISDN gateway if the Cisco VCS is configured to include the prefix of the ISDN gateway in the caller ID. To configure the Gateway caller ID on the Cisco VCS: 1.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Note: Regenerating FindMe locations and devices is a background process that can take up to 30 minutes to run with very large user bases. For this reason, best results are obtained by clicking the Regenerate button once and then allowing the process to complete.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 1. Go to Systems > Provisioning > FindMe. 2. Open the Accounts and Groups container, and navigate to the FindMe account you want to modify. 3. Click Edit in FindMe User Portal. A separate browser tab or window will now open the user portal. 4. Add locations or make other modifications as needed. 5. Save your updates and close the browser tab. Note that you remain signed in as administrator, not as the user.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide FindMe Accounts Hosted on Hifferent Cisco VCSs in a Network FindMe accounts can be distributed across multiple Cisco VCSs (or Cisco VCS clusters), but each individual account can be hosted on only one Cisco VCS (or Cisco VCS cluster). For FindMe to overwrite a caller ID with the caller's FindMe ID, the call signaling must pass through the Cisco VCS (or Cisco VCS cluster) that hosts the relevant account.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide If other characters are needed they must be “escaped” using "%" followed by a pair of hexadecimal digits that represents the ASCII value for the required character. For example, "alice smith@example.com" must be encoded as alice%20smith@example.com (where %20 represents the space character).
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Maintaining Users and Devices This section describes maintenance tasks you may need to perform after setting up Cisco TMSPE. Synchronizing User Data When you configure the import of user account data from external sources (see Creating Groups and Adding Users, page 35), Cisco TMSPE uses the information you supply to set up a synchronization schedule. Synchronization takes place once a day.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 1. In Cisco TMS, go to Systems > Provisioning > Users. 2. In the Users and Groups container, navigate to and click the group you want to test. Information about the selected group is displayed in a number of panes. 3. In the User Import pane, click Test import. Information is displayed in the User Import pane to indicate that the test is in progress.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 1. In Cisco TMS, go to Systems > Provisioning > Users. 2. In the search field below the heading of the Users and Groups container, enter the display name of the user account you want to find. You can enter a partial search string. User accounts that match the search string are displayed in the Users and Groups container. 3. To display details of a matching user account, click the account. 4.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide upgrade your configurations. To upgrade configurations: 1. Download and add the new schema. See Obtaining Template Schemas, page 42. 2. Add a new configuration template based on the new schema: a. Copy the configurations from the old template. See Adding Configuration Templates, page 44. b. Depending on your deployment, add any new configurations needed that were not available in the previous version of the schema.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Updating Cisco TMS Connection Details To update connection details for Cisco TMS: 1. Go to Administrative Tools > Configuration > Provisioning Extension Settings. 2. Scroll to the Cisco TMS Connection section. 3. Modify settings as desired. 4. Click Save. 5. Restart the Provisioning Extension service, see Restarting the TMS Provisioning Extension Windows Service, page 90.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide With a redundant Cisco TMS deployment, the above steps must be repeated on both servers. After updating the database instance, restart the Windows service for the connection settings change to take effect, see Restarting the TMS Provisioning Extension Windows Service, page 90 for instructions.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Troubleshooting This section describes the Cisco TMSPE built-in diagnostic tools and describes troubleshooting scenarios and strategies. Running Cisco TMSPE Diagnostics Cisco TMSPE runs a regular health check every 30 minutes, and displays problems encountered in a list of alarms available in Cisco TMS at Administrative Tools > Diagnostics > Provisioning Extension Diagnostics.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 1. On the Provisioning Extension Diagnostics page, scroll down to the System Status pane. 2. View the following color-coded status circles: — Red circles indicate an error or warning. — Gray circles indicate 'No status Available'. — Green circles indicate Successful status. 3. To attempt to fix a problem or to update the status of a service, click the corresponding button: — System Status: click Cleanup.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Cisco VCS Logs ■ Go to Status > Logs > Network Log to see registrations, failed registrations and other network traffic. ■ Go to Status > Logs > Event Log for a listing of all events. ■ Go to Status > Logs > Configuration Log to get an overview of Cisco VCS configuration changes. Endpoint Logs For hard endpoints, browse to their IP address to view/download logs.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Provisioning Problem Scenarios Database Connection Failure When Cisco TMSPE fails to connect to the database, an error message will appear in the lower right corner when accessing the Users page. No alarms will be raised in the diagnostics, but red indicators will show that the services are not functioning.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Cisco VCS Reports Data Import Failure If Cisco VCS raises a Cisco TMS ticket with the alarm "TMS Provisioning Extension services data import failure", there is a problem with the data format or the number of entries received from Cisco TMSPE.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide 3. In the Devices pane, make sure Enable Service is selected. For further instructions, see Configuring Cisco VCS via Cisco TMS. Signing in Fails When No Template Available A device will not be able to sign in for provisioning if no template exists for the type of device. If no template exists for its version, Cisco TMSPE will fall back to the latest template available for earlier versions.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Portal Troubleshooting Cannot Access FindMe or Smart Scheduler Error message: Access denied. Verify that all critical Windows Updates are installed on the server. Using Search History to Diagnose FindMe Issues Looking at search history (on the Cisco VCS or Cisco VCS cluster that hosts the relevant user account) is usually the best place to start diagnosing FindMe-related problems.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Removing Provisioning From a Cisco VCS If provisioning is no longer required or if provisioning was accidentally enabled on a VCS Expressway, follow the instructions below: In Cisco VCS: 1. Go to Maintenance > Option keys. 2. Select the Device Provisioning option key. 3. Click Delete. Document revision history Date Description April 2015 Release of Cisco TMSPE 1.7. September 2015 Release of Cisco TMSPE 1.5.
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide Date Description 2012-10-30 Clarified Java 6 requirements, added related troubleshooting item. Added IIS redirection limitation to Cisco TMS requirements. Modified endpoint recommendations to include Cisco Jabber Video for TelePresence 4.2. Specified that database name is case sensitive. Added information about FindMe URL. 2012-09-13 Clarified SQL prerequisites in requirements section.
Cisco Legal Information THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
