Update of telepresence

Dear Sirs,

our clients have three CTS-3000, CUCM Cluster, Manager of CTS, CTMS.
CTS-3000 - Firmware version is 1.4.3.
CUCM - Version is 5.1.3.2000 - 3, the material is MCS-7825-H3.
CTS Manager - Version is 1.3.1.0 (460), the material is MCS-7835-H2.
CTMS - Version 1.1.0.0 (254), material is MCS-7845-H2.

Customer has a Cisco warranty. The customer now wants
upgrade of the solution up to 1.6 version and CUCM up to version 7.1.

1. the following (after 1.4.3) versions of firmware are available for the CTS-3000:
a. 1.4.7 (2229);
b. 1.5.1 (2082).
c. 1.5.10 (3648);
d. 1.5.11 (3659);
e. 1.5.12 (3701);
f. 1.5.13 (3717);
g. 1.5.3 (2115);
h. 1.6.0 (3954);
i. 1.6.2 (4023);
j. 1.6.3 (4042).
Should install us all versions of firmware under the instruction of one or
There is a recommended update sequence?

2. the following versions of software are available for the CTS Manager:
a. 1.3.2 (466);
b. 1.4.0 (279);
c. 1.5.1 (420);
d. 1.5.2 (423);
e. 1.6.0 (220);
f. 1.6.2 (64);
g. 1.6.3 (113).
Should install us all versions of the software under the order by one or
There is a recommended update sequence?

3. the following versions of software are available for Community trade marks:
a. 1.1.1 (30);
b. 1.1.2(6);
c. 1.5.0 (222);
d. 1.5.1 (2);
e. 1.5.2 (21);
f. 1.5.3.12;
g. 1.5.4(4);
h. 1.5.5(1);
i. 1.5.6(1);
j. 1.6.0 (108);
k. 1.6.1(2);
l. 1.6.2(3);
Mr. 1.6.3(2).
Should install us all versions of the software under the order by one or
There is a recommended update sequence?

4. what sequence of update should be used?
Firstly the CUCM, then CTM, Community trade marks and the CTS-3000 to last.
Or there are more good sequence?

Thanks in advance.

1. you can go directly to the latest version 1.6.3

2. If you want to go 1.6.X you must update in 1.4 first and then do a direct to 1.6.3 upgrade once you run 1.4.0

http://www.Cisco.com/en/us/partner/docs/Telepresence/cts_manager/1_6/Admin/ctm_instalCTS_M.html#wp1080226

3.

The upgrade to version 1.6.0 CTMS

When the upgrade to CTMS version 1.6.0 you run CTMS Release 1.1.2 or later. If you are running a version prior to CTMS Release 1.1.2 update to version 1.1.2 CTMS before the upgrade to CTMS version 1.6.0.

http://www.Cisco.com/en/us/partner/docs/Telepresence/multipoint_switch/1_6/release/notes/CTMS_1_6_RNs.html#wp96444

4. I first put the CTM CUCM, then CTM and last endpoints

HTH

Tags: Cisco Support

Similar Questions

  • Update | Migration - Cisco TelePresence Content Server

    Hello...

    I have a physical camera TCS M2, I would like to upgrade to the latest version 7. XX verified but it is apparently not possible to perform this procedure for the unit of these versions. What are my options? Is there a version compatible with the model of this device? My solution would be virtualization? Can someone help me with a possible solution?

    Best regards...

    You mention that you're running a TCS M2, which is a second generation aircraft, non - UCS Server?  If so and you want to stay on this material, you can run TCS S6.1 up to S6.2.1 as a virtual machine on that server.

    TCS S6.2.1 Release Notes

    TCS S6.2 VM Installation Guide

    If you plan on TCS S7.x running, you must migrate the TCS to the virtual device, you can run it either on a third generation or fourth generation TCS device or third spec-server meets the minimum requirements.

    TCS S7.2 Release Notes

    TCS S7.1 VM Installation Guide for existing customers

    If you need more information or help, suggest that you move your thread to the telepresence of forums where these devices are most active section discussed.

  • 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

  • THIS 8.2.1 update software of CUCM

    Hello

    I intend to upgrade a number of telepresence endpoints in the new software, endpoints themselves have not yet been installed, but I am preparing CUCM 11 so that upgrades take place during installation.

    I downloaded the package of software of THIS "complete" which should include software for all of the affected devices, it was installed in CUCM TFTP, but I noticed after installing that there are a number of. PKG files visible in TFTP for THIS software, it is not all .loads that I expect to see.

    Is this just a case of specify the .pkg file in the devices section of phone charges?

    Thank you, Simon

    You would see the .pkg telepresence settings from IP phones files where in you can see .loads files.

    If you have installed the firmware CE8.2.1 and then restart the TFTP service and check if its device listed under > Device Settings > device default settings.

    If it is under default device settings are then displayed, simply reset the device and begin the firmware update. There is no need to specify the file name .pkg under the section of load for the camera phone. Phone should be default device.

  • The MXP 95 edge Firmware update

    Recently, I came in an operation using a Tandberg Edge 95 legacy. The firmware of the device, from what I can tell has never been updated. It is currently running F6.0. I downloaded the F9.0.2 package but I am not familiar with this procedure. Can someone help or direct me to a site of insturctional on the updating of this device?

    upgrade is covered in this document - page 141

    http://www.Cisco.com/en/us/docs/Telepresence/endpoint/MXP-series/F9/administration_guide/mxp_series_administrator_guide_f90_excl-full-menu-structure.PDF

    You also need a release F9 key.

  • Provisioning configuration of extension error telepresence management suite

    Dear Team Support Cisco

    I'm Tung, FROM Sun Media Corp. in Viet Nam

    I am using 6000 BE and install TMSPE on BE6K

    But during the installation, I have problem (attach file)

    "Process must leave before the requested information can be determined.

    I have used TMS 14.4, TMSPE 1.2, Java 8.0 u20, SQL 2008, Windown sever 2008 r2

    Can you help me now?

    Thank you very much

    Java 8 is not supported; You must use the update of Java 7 51 (32-bit or 64-bit).

    See page 11 of the release notes: http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/tmspe/release_note/Cisco-TMSPE-Release-Notes-1-2.pdf

    /Jens

    Please note the answers and score the questions as "answered" as appropriate.

  • Event failed: look for software updates

    It is slightly different from that of other positions is not the download itself which is a failure, but the connection to the server and download only at certain hours of the day (midnight). I suspect there's something else running at that moment that causes the error. How can I change the time as telepresence checking them updates see if that corrects the problem?

    A little, here are the logs:

    25/08/2012-12:27 AM - download complete successfully:

    http://FTP.Tandberg.com/pub/software/endpoints/TC/TC5/s52010tc5_1_4.pkg

    25/08/2012-12:27 AM - download new software:

    http://FTP.Tandberg.com/pub/software/VCs/X7/s42700x7_2_0.tar.gz

    25/08/2012 12:32 - download completed successfully:

    http://FTP.Tandberg.com/pub/software/VCs/X7/s42700x7_2_0.tar.gz

    25/08/2012 12:32 - verification of updates completed successfully

    25/08/2012 12:32 - event completed successfully

    27/08/2012 12:00 AM - events executed by ABURPTMS01

    27/08/2012 12:00 AM - check for software updates began. Connection for the update service.

    27/08/2012 00:01 - updates checking failed. Please see the logs for more details. Note that MSDS must have access to the internet to communicate with the software update service.

    27/08/2012 00:01 - the event did not complete. Details: The update check has failed. Please see the logs for more details. Note that MSDS must have access to the internet to communicate with the software update service.

    Hello

    Go to administrative tools of--> configuration--> network settings

    Then go down to the 'automatic update check'. Sett that on no, then press Yes

    The update check should start within 3 to 5 minutes. It will run now every 2 days to the time stamp that you set the automatic update on Yes and not 12 h 00 except not if you turn it back on at 12:00 a day...

    / Magnus

  • TC7.0 blocks iframes for telepresence VC

    Is anyone know how circumvent or allow iframes for Cisco TelePresence SX20, C40 using TC7.0

    We were able to view snapshots using iframes on TC5.1 but it is now, no longer works with TC7.0

    Any help is greatly appreciated. Maybe there's a way to reactivate this setting on the web server in the VC unit?

    A simple (but not necessarily secure) way is to add the credentials in the URL, that is to say:

    [email protected]/* *//websnapshot/get">http://username:[email protected]/* *//websnapshot/get

    Updating can be done in the HTML HEAD element, IE to refresh every 30 seconds:

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

  • Cisco telepresence video Communication Server (VCS) - compatibility CTX X8.1.1?

    The Cisco TelePresence Exchange System compatibility matrix (CTX) does not cover version of VCS X8.1.1 (to solve the problem of software). Version X7.2 is recommended and supported which is affected by "heartbleed".

    X8.1.1 compatibility is tested by Cisco and the updated matrix?

    In fact we run CTX v1.3 with VCS X7.2 and solve the problem of software without leaving the support. What is the recommendation of Cisco?

    Kind regards

    C.Opwis

    You could improve your VCS to X7.2.3 which includes a fix for Heartbleed.

  • Telepresence Server RTP ports

    Hi all

    I've recently updated 5320 MCU to 320 TS. I searched the documentation for the RTP port range used by the telepresence server, but it is never mentioned. What is the range of ports, and can we change it?

    I have deployed infrastructure with XC2.2 driver in the B2BUA deployment model and a TS on 5320 version 3.1.

    Sent by Cisco Support technique iPad App

    Hi Paul,.

    Take a look at this article, this applies to all products Conference Tandberg/Codian, including TP server too, as you can see:

    http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/articles/conferencing_products_conferenceme_ports_used_kb_3.shtml

    According to the document, ports between 49152 to 65535.

    Concerning

    Paulo Souza

    Please note the useful answers and do not forget to mark questions resolved as "responded."

  • Telepresence EX60 with CUCM 8.5 - How to integrate?

    Good morning people,

    I'm building a lab with 8.5 CUCM and presence Server 8.5

    I'll install the Cisco TelePresence EX60, and I wonder how I do integration with CUCM.

    Need to install the additional server? You simply add a SIP device in CUCM?

    Can someone help me?

    Thank you

    Bruno

    Hello.

    You must have CUCM 8.6 in order to utlize the full potential of the CUCM / integration EX60. You save the unit directly to the CUCM.

    I recommend you take a look at this guide, after that you did with your laboratory update.

    http://www.Cisco.com/en/us/docs/Telepresence/endpoint/codec-c-series/TC5/administration_guide/cts_endpoint_administration_ucm86_quick_start_guide_tc50.PDF

    I have attached a screenshot showing how it should look like the description of the device.

    Thank you

    Marius

  • VCS update X5.1.1 to X7.2.2

    Hi all

    We need upgarde our client VCS-E and VCS - C of X5.1.1 to X7.2.2. Read the Release Notes, I found that I must first be upgraded to X5.2 then X7.2.2. The first update do not require unlocking new keys, but for the second we need new keys for unlocking.  There is also a TMS 12.6 used to supply.

    Can you please indicate confirm the steps above X5.1.1 X5.2 to X7.2.2 upgrade? for VCS-E and VCS - C?

    I also saw a note comment about covers them authentication.  apparently once upgrade is all areas and subareas (except the default Zone) authentication is set to "treat as authenticated.  As no auth is activate now.  Does this mean I have to turn it off once completed upgarde?

    Finally can you tell me how long it takes to do?  As I will need to plan this work out of opening hours.

    Thanks in advance.

    Ahmed

    Hi, Ahmed.

    First thing is that I will not go in one fell swoop. You can go in the parts actually.

    -If you have any installation of replication between MSDS and stood then you turn off gracefully.

    -go ahead and upgrade to x5.2 VCS and take a backup for VCS and VCS-E time.

    -go and upgrade to x6.1 then x7.2.2,

    consult the Notes version of VCS for more details.

    http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/VCs/release_note/Cisco_VCS_Release_Note_X7-2-2.PDF

    I also suggest you to install the TMS last version 14.3 and switch mode provisioning TMS extension if you previously active provisioning.

    Yes, this is true for a minor update like 5.1 to 5.2 key would be same and for major update, you need to separate key release.

    come to part of authentication, the areas are defined on ' treat as authenticated "when you upgrade is because the upgrade of VCS is troubled not customer enviornment.

    areas have three authentication supported "do not verify the credentials", 'powers of audit', & 'treat as authenticated.

    treat as authenticated is the safest option at all than VCS in this case be sure that what cross is an authentic asks and proceed to demand. Other options that might hinder the peformance.

    to upgrade a server takes 20 min but I will propose you to take a good break and plan ahead.

    Rgds

    Alok

  • Software update of MCU 4505

    To get back into the mix of things with our telepresence equipment and we have a MCU which is on an older version of software.  After downloading the new software MCU 4.5, I do just that if I update I will not lose one of my features enabled.  Our current version is 4.2 (1.46) version of software.  We have the following features enabled:

    1. Encryption
    2. Web conferences
    3. Activation of MCU 4505
    4. key feature of capacity 1080 p upgrade

    Looking at the docs online, doesn't look like I need anything that either step upgrade.  Already upgrades for my C40s since these option buttons do not disappear when you upgrade to a newer version, but was not sure of the MCU.  Any ideas would be great.

    Hi, Brandon

    Options keys do not disappear.

    Your current options keys remain valid with the new MCU software.

    BR Oleksandr

  • Telepresence Content Server

    I've reviewed a few information about the content of telepresence server and thought someone here might know the answer.  I read conflicting information.

    1. The content of telepresence Server allows to watch a live stream?
    2. The content of telepresence Server allows SIP?  The data sheet said yes, but the doc said H.323 only.
    3. Then the auto-join the content server with TMS telepresence session?  My hypothesis is Yes since the endpoints can be set to auto-answer/join.

    My goal is to set up a registration and solution to this TCS in combination with REV and a DME is proposed, but if the TCS can all do by itself and then unload the records to a NAS, so I wouldn't need the rest of the solution.  Thanks in advance.

    1. The appliance and the virtual TCS can support 5 or 10 simultaneous on the records of the application, and any one of those, 2 of them can also be broadcast live.
    2. You can use h.323 or SIP with a standalone TCS.  From TCS version 6.2, you can now have a cluster using h.323 or SIP, before 6.2 it was only H323.  The user guides and admin are incorrect and still be up-to-date to reflect the SIP enhancements in version 6.2.
    3. You can schedule recordings of TCS with TMS without problem, we do it every day.  The downside is that you can't plan a TCS cluster using SIP, TMS have not yet updated to reflect the changes in version 6.2.
  • Cisco TelePresence Manager 1.7 with EWS 2007, Timezone and purpose of the meeting of the problems

    After having successfully configured the CTMan MS EWS CASE 2007 1.7 I am stumbling on two errors/bugs very subtle and boring between these two servers.

    1. the time zone in the confirmation e-mail sent by CTS Manager to the meeting returns

    501225

    Summary

    Unresolved zone mapping

    The problem lies in the information CTMan by EWS thrust. According to the text in the zone tags, CTMan maps time zone accordingly or it does not. It's really incredibly annoying.

    For example:

    Standard time this gets the mapping OK

    (UTC + 02:00) Harare, Pretoria it is not mapped OK

    (GMT + 02:00) Harare, Pretoria it is not mapped OK

    South Africa standard time , that it becomes mapped OK

    Update the file timezonemap.xml in the telepresence Manager would be a nice gesture by Cisco to avoid these horrible bugs.

    2. the subject meeting is always the same as the organizer of the meeting.

    In other words, the subject gets crushed by the meeting of the chain of the organizer for each scheduled meeting. I don't know how much of this is the fault of CTMan, because the resulting XML has this topic in the tags all wrong.

    Someone at - he dealth with these issues in the community?

    Any thoughts?

    Hello

    For the #1 question. I checked the file of zone mapping has the whatever you specified in version 1.8. From 1.7.2 the time zone (GMT + 02:00) Harare, Pretoria is present from the fix for CSCtj95619, but the time zone (UTC + 02:00) Harare, Pretoria is missing.

    For question #2, is due to a setting on the end of the Exchange. The mailboxes for the room have the DeleteSubject and AddOrganizerToSubject the value true properties.  Follow this guide #7 step to correct the problem:

    http://www.Cisco.com/en/us/docs/Telepresence/cts_manager/1_7/Admin/ctm_instalMS.html#wp1097531

    Step 7 Set the "DeleteSubject" and "AddOrganizerToSubject" properties in room mailbox calendar to False. This sets the parameters for the meeting to be displayed on the IP Phone.

    For Exchange 2007: a. Set-MailboxCalendarSettings -Identity TelepresenceRoom9 -DeleteSubject $false b. Set-MailboxCalendarSettings -Identity TelepresenceRoom9 -AddOrganizerToSubject $false

    Thank you

    Paul

Maybe you are looking for