TMS 14.3.2 a HDX7000

Similar Questions

• License TMS for Polycom integration [command]

  Hello

  My customer has existing Polycom HDX7000 series and they need to use TMS for the planning meeting.

  Should I order the license 'Cisco Network TMS integration Extension (Polycom, Radvision ViaIP, MGC, Cisco 3540)' on TMS for the support of this solution?

  IF THE ANSWER IS "YES"; my client has 10 points from polycom endpoints, should I order this license for 10?

  Please help me :D

  Thank you

  Yada.

  No, this option is for third-party MCU. The comma between Polycom and MGC is a typo.

  You can simply add the HDXs MSDS and they consume a system standard license only.

  Sent by Cisco Support technique iPad App

• TMS follow-up Conference does not work after update of Java

  Just installed Java 7 update 51 and now I am not able to enter the CCC in TMS 13.2.2.

  This is the dump of Java:

  Java plug-in 10.51.2.13

  With the help of 1.7.0_51 - b13 version JRE Java hotspot Client VM

  Home Directory user = C:\Users\lhamilton

  ----------------------------------------------------

  c: clear console window

  f: finalize objects on the finalization queue

  g: garbage collection

  h: display this help message

  l: dump classloader list

  m: print memory usage

  o: trigger logging

  q: Hide console

  r: reload the policy configuration

  s: dump system and deployment properties

  t: dump thread list

  v: dump thread stack

  x: delete the cache of class loaders

  0-5: set the trace level

  ----------------------------------------------------

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  Attribute of manifest missing application name for: http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/Tandberg/Tms/UI/Monitoring/conferencecontrol.jar a future expires: Sat Feb 01 10:39:25 PST 2014 update done.

  Resources http://134.39.50.193/tms/styles/Default/images/PortalPageStatisticsChartLoading.gif a future expires: Sat Feb 01 10:37:47 PST 2014 update done.

  I had similar problems yesterday when I updated to 7u51 (with TMS 14.1.1).  I rolled back to the previous version, I had installed and it worked fine.

  Pursuit of the investigation, it seems to happen due to new security measures in the new version of Java.  You can move with the latest version of Java 7u51 by adding your server TMS in the security exception list:

  (1) Control Panel Java Open

  2) click the Security tab

  3) click on the button "change the list on the Site."

  4) click Add and type the URL of your server TMS in the location area (IE http://tmserver/tms/)

  (5) to continue beyond the warning about sites http if you use http instead of https

  6) click OK on the control panel

  Then you should be able to hit the Java pages in TMS without any problem.

  Wayne

  --

  Remember the frequency responses and mark your question as answered as appropriate.

• TC cannot connect to TMS on demand conference

  Hello community,

  I sent TCS in our video conference infrastructure and SIP Trunk to CUCM.

  I can do by opening a web session of the TCS for manual registration and dial points endpoint or lectures on the conductor using SIP.

  But if I do the Conference planning on recording of the Conference, the TCS and TMS don't auto connect to the Conference. Registration (SIP URI) alias are configured on TCS.

  I see on the connection of conference TMS setting the driver calls the CHT by using the h.323 protocol but TCS is not registered with the h.323 Gatekeeper. It's using a SIP trunk to CUCM. Is this a limitation if the TCS uses SIP trunk?

  tcs_error.jpg

  

  Thank you.

  ACCOUNT that is configured with CUCM planning only is not supported yet in TMS using the recording during a conference booking. See cisco-tms-cant-schedule-sip-recordings-tcs for more details, the solution is to add the alias to record with a participating entry model or the phone book.

• TMS and AVAYA scopia endpoint interoperability

  Hello

  I have the management console of the TMS version 13.2. It is not the latest version, but I wonder if AVAYA SCOPIA XT-4300 products are compatible for integration in the TMS. It's like the product POLYCOM HDX?

  Y at - it a document on which products are supported?

  Thank you very much!

  For TMS 13.2, you can take a look at the Documentation of integrated systems, specifically Product Support and documents using the feature to see what Cisco and 3 third-party products are supported.

  Note, for the most recent releases TMS, you will need to look at the admin guides as well as Telepresence interoperability of data because there are no available detailed compatibility document, similar to those mentioned above, for the version beyond TMS 13.2.

• Cluster TMS

  Hello

  I have 2 servers TMS lab facility. I need to make the combination between these servers with the same SQL database. I checked in google, all documents are mentioned with infront network load balancing. Because I don't have a material I don't know how the grouping between the TMS servers.

  When I asked my manager said, there is another way to do grouping without using NLB and he won't tell. BCZ I need to know about mine... which i have no idea... Please someone tell me... Here are the details...

  Primary server for the TMS (15.1) - 10.66.204.45

  Secondary server of MSDS (15.1) - 10.66.204.46

  SQL 2014 - 10.66.204.40

  Hello

  You can use the LB which is the recommended method and other could be DNS (not so great)

  Please see the link below.

  https://supportforums.Cisco.com/discussion/11921901/TMS-redundancy

  Please see page 30 for the detailed explanation.

  http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/infrastructure/TMS...

  Kind regards

  RACLOT

• TMS IP address changing

  Built a new setver 15.0 TMS in the laboratory and I now have to move to its real end IP address.

  I remember that there was a document that tells what to change to make this happen, but I can't.

  Can someone tell me the document?

  Thank you

  Either before or after you change address IP of TMS on the server itself, you need to update the field "TMS Server IPv4 address" listed under administrative tools > Configuration > network settings and use the settings option management apply on the same page under the heading Services MSDS to update IP address on all systems managed at the time. You can also go to each system managed on their settings page and use the settings option apply management it update each system one by one.

• Purge schedule on the TMS/TMSXE

  TMS is 14.3.0

  TMSXE is 3.1.2

  We gave up on the recording of our telepresence on the CUCM, we work to keep away them from the CUCM and their inclusion in the VCS - C (see here). But when you remove the CUCM non-registrant endpoints off the TMS and add it as registered endpoint C - VCS, TMS causing problems on all scheduled meetings.

  After the now the rebinding VCS - C saved telepresence endpoints for room calendar changes in the TMSXE, it

  1. Add the 'new' (actually modified) end for the calendar of meetings
  2. maintains endpoint (previously saved CUCM) former listed as a "shadow" unknown endpoint
  3. clear the multipoint resource MCU/TP server allocated meeting
  4. send an email to the host of the meeting, saying: "information your administrator is migrating to a new system of conferencing reservations." During the migration, your conference was made. Cautions due to limited resources of routing, automatic routing could not be set up for your conference. A participant dial-in/out external added to the call is not connected. To ensure that the Conference will connect and the delivery of resources are available, contact your administrator to videoconferencing. Road is not valid.

  But all meetings are internal, and there are many resources available on the telepresence Server

  I wonder if there is a way to solve this problem and what we should do. Is there a way to purge all the TMS meetings so that the TMSXE re - synchronize all the information meeting of the TMSXE.

  Hello

  There is unfortunately no history of migration in TMS between a CUCM-centric and a deployment centered on VCS. If you make a change like that, you essentially need to manually update all future bookings.

  Kind regards

  Kjetil

• TMS - automatically check updates question

  Hello

  I tried searching online but that isn't a direct response to this problem, with what I am currently blocked, he has been mentioned here https://supportforums.cisco.com/discussion/11251221/telepresence-managem...

  I have followed the instructions but still have the same issue where the MSDS cannot automatically download new software.

  My TMS version is 14.2.2

  When the automatic software update is set to Yes, TMS tries to download the software and then I got an error message (see below)

  Event log

  29/04/2016 14:25 - created event 29/04/2016 14:26 - events executed by XXXXXXXXXXX 29/04/2016 14:26 - check for software updates began. Connection for the update service. 29/04/2016 14:28 - checking for updates failed. Please see the logs for more details. Note that MSDS must have access to the internet to communicate with the software update service.

  The server is connected to the Internet, even when you try to use a proxy TMS still can not download a new software.

  Someone else maybe solved a similar problem to mine.

  Concerning

  Starting with TC6.1 and later, TMS will download is no longer automatically TC software, this is due to a change in the verification procedure and download of these versions of the software.  When the new TC software is released, you will need to log in to Cisco.com and download the software yourself and then transfer it to your TMS servers.

  New procedure to download software for the endpoints of telepresence running TC software

• REDUNDANCY OF TMS

  Hello

  One of our customers is to have a primary site and the recovery for the conferencing site. They are planning to implement redundant VC a componnents like VCS, conductor, MCU and TMS.

  I need your expert opinion in the deployment of the TMS in the main Site and recovery Site scenario.

  Primary site and recovery Site is in a totally different network. We cannot extend the primary IP address on the site of DR. Because of this redundant components will have the IP address to a different subnet.

  TMS Server A: 10.10.10.10

  TMS Server B DR Site: 10.20.20.20

  DNS A record for TMS server is tms.example.com--> 10.10.10.10

  I checked the options for redundancy of TMS, as shown in the link.

  http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/TMS/config_guide/Cisco_TMS_Server_Redundancy_Config_Guide_13-0.PDF

  Fully redundant use the concepts of the load balancer.

  I have the following questions.

  1 could you please let me know what load balancer can be used for redundancy of TMS solution considering the IP address of the MSDS are in different subnets.

  2. in several servers, manual failover option, if the failure of the principal server will we use 10.20.20.20 address IP Cisco TMS Server Local IPv4 address and update the DNS record to point to 10.20.20.20.

  Krishna.

  Option a.

  I would not recommend an A DNS record pointing at a time... since it is essentially a round robin... which means that if DC 1 is down, you will get a search on the second, it will just fail. Therefore, I would recommend you do is just enter a DNS record for the DC 1 TMS and if you get a failure on DC 1, then simply go to DNS and to update IP address for this record to the DC 2 TMS.

  Option B

  No, you don't want to do this, i.e. Add the EPs for the two TMS initially. You only want to add systems to the DC 1 TMS... which means a TMS db to "govern together." And that's why your "asynchronous mirroring ' the TMS of DC db SQL to CC 1 2 SQL." And specify "async mirrroring in SQL", when you set the "async mirroring" in SQL, a db is 'active', while the other is "passive". That's why on the DC 2 TMS all services of TMS needs for people with reduced mobility because it cannot connect to the TMS SQL db (tmsng), which is passive. And with "async mirrored" on and how often you 'mirror', the basics of data will actually be the same.

  At the end of the day, the deployment is not that big (20 systems) so all this may seem "exaggerated", but it is the approach to 2 x installation DC... unless of course you virtualize everything and go Nick road, i.e. the Group OTV and strecthed.

  Rgds,

  Dale

• TMS conference control center

  Hello community,

  We have TMS version 14.6. My question is why we cannot see the screenshot of the endpoint on the control of TMS conference center?

  The endpoint is SX80 TC7.2.3. We do not have the key Option Remote monitoring installed on the endpoint. Is this the reason why we cannot see the snapshot? Do we need to buy the key to activate it?

  Monitoring.PNG

  

  I expect this on our TMS:

  remote_display.PNG

  

  According to the names of devices hosting the conferences, I guess that for the image where no snapshots are seen is a driver (cisco-cndtr), and the other is a MCU (MCU - SD) product?

  If this is the case, snapshots are not supported with the conductor, see CSCuj02741.  When you use the driver, only a subset of the features of CCC are supported, see the section "Follow-up Conferences" of the CMR premises Solution Guide release 7.0 on pg 28.

• TMS Smart Scheduler - what can you schedule and dial a number?

  Hi Forum,

  I think TMS 13.2.1 at 14.3 TMS with TMSPE 1.1 reclassification.  However, I saw that the 'old' web scheduler has been replaced by the new smart sceduler.

  You can plan the new smart Scheduler? It seems that you can only program calls to numbers in directories?  You can schedule dial calls to:

  Directory movi/Jabber?

  External SIP/h.323

  External ISDN?

  What can't the new smart Scheduler compared to the 'old web Scheduler '?

  Thank you

  Robert

  Robert H.

  Yes, at this time, you can add managed by TMS systems (those that are added to the system > Navigator) when planning through Smart Scheduler.

  Cisco has already opened a feature request for the opportunity to add directories or call the participants in the smart Scheduler interface, but I cannot confirm if Cisco really wants to develop or when it will be available. It's the already opened by Adam feature request:

  https://Tools.Cisco.com/bugsearch/bug/CSCug76084

  A solution would be to add your external endpoint as a 'room' to TMS under system > Navigator, so that they will appear on Smart Scheduler, however, systems added as piece takes a license system just like a common system managed by TMS. So, before you follow this workaround solution, make sure that you have licenses enough for that.

  Can my personal thing, if you really need schedule the call out participating, so I suggest you use common reservation interface, at least up to the Cisco enhance Smart Scheduler.

  In addition, to raise this feature request you, your local Cisco representative so that they can help you to climb this feature in Cisco request to try and get priority on this point, it is useful. More customers are asking for the same thing, more Cisco considers that the feature request.

  Concerning

  Paulo Souza

  My answer was helpful? Please note the useful answers and do not forget to mark questions resolved as "responded."

• Adding the Polycom HDX to the TMS system

  How can I add a Polycom HDX system in TMS to manage?  What, if any configuration on the Polycom system must be made, or in the TMS?  Can't seem to find any documentation about it.

  http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/TMS/interoperability/Cisco_TMS_Product_Support.PDF

• TMS ISSUE NR #3

  I was running MSD 15.2.1 with SQL 2008 on the same server VM.   I uninstalled TMS 15.2.1 on this server.  Only of SQL is for TMSNG.

  I created a new virtual machine and put TMS15.2.1 and pointed the old VM server and everything seems OK at the moment except.

  See the screenshot below. Showing that it considers services do not run on the old server, but TMS is on a new server with a different name.  How to clear this?

  Something is always oriented to the old name of the server and I checked, service TMS is not installed or running on the old SQL Server only.

  Is there something in the comic book that I need to empty, then she stops to think THAT TMS is on the old server?

  Also regarding the encryption key.  I have the new key showing in the TMS tools on the new server but the Save button is gray?

  VR

  Chet

  It's been a while that I've migrated a SMT from one server to another server.

  If you go to administrative tools > TMS Server Maintenance, under status of service TMS, what do you see?  See services for your old server and new, if, what happens if delete you the list and let the TMS fills again?

  The encryption key, the record regarding the button will become active if the key in the tools of TMS is changed.  Also suggest you do a check for any encryption key mismatch TMS tools > Diagnostic tools, if the encryption key has been changed.

• TMS ERROR... ANYONE KNOW WHAT THIS ACTION FIX?

  TMS 15.2.1 running

  Windows 2008R2

  Get the following error:

  The task of ETL for TMS data communication has failed.

  	Ticket #:	3109	Recognize Delete
  	Status:	08/31/2016 acknowledged 09:22:33 by Chet JNCC - a SME Cronin
  	Description:	The task of ETL for TMS data communication has failed.
  	How to solve this problem:	Check the work in situation of activity and log file ETL for more details.
  	For the first time:	20/07/2016 04:06:24
  	Last report:	20/07/2016 04:06:24
  	User comments:	KKK

  It shows in the log ETL file?  (usually located in C:\Program Files (x86)\TANDBERG\TMS\data\Logs\TMSDebug\log-etl.txt)