using ctman with endpoints registered with vcs/tms

[watkins.david]

So i have a cucm and ctman environment for cts endpoints. I also have a vcs-tms environment for every other video endpoint, in particular TC 5.x endpoints. I am unable to use the TMSXE product for the time being. So i want to add in the TC 5.x endpoints into CTMAN so that it can send down meeting data.

This works fairly well, except that after hanging up on a call using the meeting info, the meeting info gets wiped out. I assume this is TMS clearing out the data. My question is, is there anyway around this? Some option i can turn off in TMS to stop this from occuring? Anyone come up with a workaround?

Eventually ctman will be turned off and TMSXE will be used but that is months off

[Tyler Wilkin]

Hi David,

Do you have CTS-Manager and TMS managing the same endpoint (even if the TMS doesn't actually have scheduled meetings)? This isn't supported and could be a reason why you see your meetings being wiped out (the two servers are competing for control of the calendar). You need to have the endpoint mangaed by only one scheduler at a time.

If that isn't the issue, do you have the logs somewhere and the timestamp of when this last happened?

Tyler

[watkins.david]

The problem is if I remove the endpoint from tms I lose the phone book, which is as important as having meetings dumped from CTman. I was hoping someone came up with a clever workaround.

[Adam Wamsley · Accepted solution]

How to Provision an endpoint in TMS and how to Utilize Both TMS and CTS-Man for Endpoints

Note this is not a supported configuration and has not been fully tested on all versions. It is a workaround.

Purpose of this Document:

• •-          Step through the process of provisioning an endpoint in TMS.

Additional Purpose:

• •-          Provide customers with a workaround to utilize both the TMS and CTS-Man for Tandberg endpoints.

Question:

• •-          Why would customers want to use both management systems to manage one endpoint?

Answer:

• •-          Some customers like their endpoints to be registered to the VCS, receive phonebooks and upgrades from TMS, and only schedule using CTS-Man in order to utilize One Button to Push (OBTP).

Note: It is highly recommended to only use one manage system for endpoints, when a system is being managed by two management systems they will overwrite each other’s settings on that endpoint.

Workaround: Provision the system in TMS, by doing this TMS will not overwrite the meetings scheduled on CTS-Man. As a provisioned endpoint in TMS the endpoint will still be able to receive upgrades and phonebooks among other configurations and features.

Note: When you provision the endpoint it should no longer be a managed system in TMS, so be sure that you purge the endpoint and check that it is no longer listed anywhere in Systems>Navigator.

•1.1      How to Provision an Endpoint in TMS

The below process will step through provisioning an EX60 in TMS.

In TMS>Systems>Provisioning>Directory

1. Create a new group for EX-Series

2. Add a user to use with EX

3. For the configuration go to the below link and choose your desired system configuration template (http://www.cisco.com/en/US/products/ps11327/prod_release_notes_list.html)

Note: Provisioning configuration templates are not available for all systems, but this does not mean it cannot be provisioned.

4. Once you have downloaded your configuration template upload it to TMS.

5. Next add in the configurations for the EX (Basic configurations below to register, additional configurations can be added and found in the endpoint administrator guide)

        a.    Public Phonebook Server URL (phonebook@domain.com) Make sure when adding the

configuration you add the one specific for the EX60, there is a + symbol given to expand to the ones for specific models.

•1.2      Configuring the Endpoint

Refer to the Administrator Guide for additional information regarding the settings used below.

For example: Cisco Telepresence System EX60/EX90 Administrator Guide (Provisioning Settings>Pg. 49)

http://www.cisco.com/en/US/docs/telepresence/endpoint/ex-series/tc5/administration_guide/ex-series_administrator_guide_tc51.pdf

-

1. In the EX-Series (TC Software)

        a.      Configuration>Phonebook Server 1

               i.      Type: VCS

               ii.     URL: phonebook@domain.com

        b.      Configuration>Provisioning

               i.      Connectivity: Auto

               ii.     HttpMethod: POST

               iii.    LoginName: "user created in TMS"

               iv.     Mode: VCS

               v.      Password: "password given to user in TMS"

               vi.     Address: vcs ip address

               vii.    Domain: domain.com

               viii.   Path: leave blank

               ix.     Protocol: HTTP

        c.      Configuration>SIP Profile 1

               i.      Make sure the Settings automatically populated after configuring the Provisioning settings

               ii.     If they did not automatically populate go ahead and manually set the following:

• •1.          URI 1
• •2.          Authentication 1 
  • •a.       LoginName: User created in TMS
  • •b.      Password: Password for user created in TMS
• •3.          Proxy 1 address: VCS IP Address
• •4.          Discovery: Manual

2. Make sure you give permissions for the new group you created in TMS provisioning directory to have  access to view the phonebooks.

Reminder: Endpoints can handle authentication differently from the normally provisioned Jabber users, so refer to the “Device authentication on Cisco VCS Deployment Guide” on cisco.com http://www.cisco.com/en/US/partner/products/ps11337/products_installation_and_configuration_guides_list.html

•2       Adding an Endpoint to CTS-Man for Scheduling

•2.1      How to add an EX-Series or C-Series endpoint to CTS-Man for Scheduling

• •1.       In CTM > Configuration > Endpoints 
  • Add New Endpoint

• •2.       Select EX or C Series under Endpoint Type 
  • Configure Email ID, IP address and Username
  • Validate

• •3.       Save and verify the status of the endpoint.