Migration of TMS/VCS to CUCM

Hello

I was wondering if anyone can help please. I had a customer who uses VCS? TMS. Every endpoint registered in VCS - C.

I need migrat ethem to cucm 10.5.

What will be the best way to go, any suggestions will be appreciated.

Thakns

Of TMS directory are what kind you referring?

You can use TMS to a source of the telephone directory with the telepresence endpoints registered to CUCM, see pg 24 in the guide I linked to in my first answer.

Tags: Cisco Support

Similar Questions

  • Use the VCS to CUCM composition URI

    I have an external SX20 and internal jabber user

    The jabber username is [email protected] / * / and the extension number is 999

    I want entering through the composition by CUCM

    But the path is external SX20 > VCS-E > VCS - C > CUCM > internal jabber user

    I can dial [email protected] / * /, it is successful

    But can not be used [email protected] / * / composition

    Can VCS the [email protected] / * / of CUCM?

    Or where I put in error?

    I suggest that you have a good look through the VCS of Cisco and the deployment of CUCM Guide and verify that your configuration is at least similar to that proposed to allow calls between VCS and CUCM registered endpoints.  Looks like a lot that you are missing a search rule.

    If the above has not resolved your problem, I suggest you move your discussion in the section Unified Communications Applications forums at the section of telepresence , where are discussed more actively to these types of devices.

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

  • TMS, VCS and Jabbber "impossible to connect to the TMS on the VCS agent".

    Dear,

    We have Cisco TMS, VCSC and jabber deployment, we did before commissioning the VCSC and TMS and jabber worked well, but after the upgrade the VCSC v7.2 to jabber version 8.2 has stopped working and I can not connect more and when I go to the TMS and connect to the VCS I get "unable to connect to the TMS on the VCS agent" Please notify

    What TMS version do you use?  And you are using Extension of provisioning of the TMS (TMSPE)?

    Looks like you are using TMS Agent Legacy, which has been supported in VCS X7.2 and has since been removed from X8.1.  You will need to migrate to TMSPE and very probably upgrade your server TMS as well if you do not meet the minimum version.

    Cisco TMSPE 1.0 Deployment Guide

    Here's the guide deployment for TMSPE 1.0, there are newer versions, but 1.0 is one that you want to migrate from legacy Agent TMS.  Once installed and migrate your data, you can then go to the most recent version, which is 1.4 (see below).

    Cisco TMSPE with VCS 1.4 Deployment Guide

  • Problem with a SIP Trunk between VCS and CUCM

    Hello world

    I created a SIP Trunk between control VCS (X7.1) and a CUCM 8.6.

    I followed this Cisco_VCS_Cisco_Unified_Communications_Manager_Deployment_Guide_CUCM_6-1_7_8_and_X7 - 0.pdf deployment guide.

    The trunk is in place, but I have the following problem: I can ring since an EX90 recorded on the VCS for a registered on the CUCM 9951 but when I take the call, I have a busy signals (audio and video). When I on the EX90 9951 ring, I have the following message on VC: can not reach the contact.

    I have a 503 service unavailable status on the call history and "call rejected" on the event log.

    My transformation is OK and the call is sent to my neighbor CUCM zone

    You have an idea to solve this problem?

    Thanks for your help

    Best regards

    Bruno Z.

    Hello

    Yes, it's true! It seems at first glance a problem with codec negotiation when I see the reason 47 code.

    in any case set the region to G.711 trunk phone in case if you have different device pool and the trunk region and ip-phones.

    make G.711 end to end and test again.

    Thank you

    Alok

  • Questions of FindMe Provisioning/user between TMS & VCS

    Hello

    I have what seems to be a problem in service between TMS and VCS.

    Using TMS to import users from AD (from 2 domains of x), everything seems to work, and can see the users in the provisioning of TMS directory. MOVI users use AD authentication which connect properly.

    User login also works very well on the VCS (with connection LDAP AD). However when to call the findme users address VCS does not recognize the configured users? If you navigate in user accounts, the user is not displayed, if you run a search on VCS (users account address name or findme) findme VCS find the user. Once the user has been found and open if you click on save button (without changing details), the user will then appear in the VCS user accounts section and findme works correctly.

    We use the TMS 13.1.1 and VCS x7.0.2 (Cluster).

    I would like to know if you have solved your problems or you are still having problems? Any suggestions for help would be appreciated.

    Thank you

    Matt

    Hi Matthew.

    Findme users must fill in the "user accounts".

    But you must make sure that the VCS 'Cluster name' matches the 'SIP server address' in TMS.

    TMS:

    VCS:

    I hope this helps.

    / Magnus

  • TMS and registered CUCM phones (endpoint No. TC points)

    Hello

    A customer has a lot of 9971 series and other video capable ip saved in CUCM phones which are obviously not the criteria of TC.

    How can I go to add to TMS? Are they added only as unmanaged endpoints?

    Is it possible that I can force the TMS or the conductor also to call them so that they can join a conference?

    We have some use VIP users who want to call rather than compose themselves at the Conference and they have no endpoint of TC.

    Thanks in advance for the help!

    You probably don't have to add CUCM in TMS, unless you want to add any endpoints mentioned some of my first answer in TMS, although it wouldn't hurt to add it anyway.

    You can add IP phones as unmanaged endpoint points, although this will consume a TMS system for each license added.  If you have plenty of endpoints that you want to add and you do not have enough licenses, you can use a directory phone, as mentioned earlier, see the "Manage Sources of phonebook" on pg 187 for more details.  You can schedule video conferences using two methods, but Smart Scheduler is unable to add participating telephone directories, so the TMS advanced scheduler should be used if you add participants from telephone directories.

    What you do above in the TMS for the planning of endpoints has no impact on its PMF, you can add endpoints you want logged in as a favorite yourself in your TMS user portal.

  • Migration of TMS PE installation tool

    Hi all

    I have a problem:

    I installed the SMT Server 13.2.2.Then I want to install the tool PE. I have the type of credentials of all necessary data and identification information as identification information of MSD and SQL Remote Server on the installation of the progress of this tool of PE. Whenever this error pops up "Please check the SQL protocols.
    There are 4 parameters on the site SQL what we could to set:
    = Shared memory: enabled?
    = Named Pipes: enabled?
    = TCP/IP: enabled?
    = VIA: enabled?
    the 4 parameters must be defined on the PE tool can be installed successfully or to connect to the remote SQL database SQL database?
    We cannot install the tool of PE.
    THX for your comments

    Great and no problem, please set this resolved thread then :)

    Sent by Cisco Support technique iPhone App

  • 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

  • Content server - migration MediaSense

    Hi all

    I am currently migrating my gateway TMS\VCS to CUCM telepresence end points.

    My Tandberg Content Server just died and I already have 2 support detection servers deployed.

    The question is: detection of support will eventually replace Content Server?

    The current feature support detection seems really limited compared to the content server, but I don't need a lot more - just to be able to save and export the video.

    Is what someone running CUCM + TMS and use record support for multi detection video conferences with channel content?

    Thank you.

    6.2 to CHT's already out earlier this year and available now.  The migration is pretty cheap, on the top of my head, something like less than $5 k per server is what we paid.

  • Numbering plan of TMS actions required when changing the VCS

    Hi all

    I will be changing my exclusively H323 to SIP client only VCS dial plan. This will be done to activate the route through VCS - E and also prepare for the migration of their VC on CUCM endpoints at a later date. When I change the dial plan I'll change the end point URIs, aka Multiway and digital beaches assigned to scheduled meetings.

    Can you please help me understand what I need to do to make sure that:

    1. MSD directories are updated with new endpoint aliases; and
    2. Existing meetings are moved to the new number ranges

    Thanks in advance for your advice.

    Telephone directories TMS should update automatically as long as they do not use a source directory manually.  You should see the telephone directory changes some time after you migrate the H323 to SIP endpoints points, depending on how often you have telephone directories to update.

    A regular conference will have to be updated to reflect the change dial plan, you can simply change the Protocol that uses H323 to SIP endpoint in the settings to connect to the Conference.

  • connect the two controls of VCS to Call Manager, unity and IM/P by AXL for migration

    All,

    I'm migrating from physical to VM for my VCS-C/E. can I connect ' my existing physical VCS both my new virtual machines to CUCM, unity, IM/P by AXL at the same time? or should it be done at the during the downtime of the migration?

    The new virtual machines are not ready yet... always set up the production.

    Thank you

    RB

    You can integrate physics VCS C/E with CUCM, CUC, IMP from now. Once you are about to migrate to virtual VCS C/E, you can integrate virtualized VCS C/E with CUCM, CUC and IMP and shut down physics VCS C/E.

  • Integration of CUCM, CTS and TMS

    We currently have a 8.6/CTS-Man/CTMS CUCM environment for our telepresence system.  All systems are CTS only.  Currently, connect us to a Tandberg system via Server CUBE/VCS/telepresence.

    We are looking at the possibility of integrating the two systems together.  This would involve decommissioning our CTS-man and using their existing planning TMS.  Networks would be open to each other so that they didn't cross highway of CUBE/VCS.

    Can someone tell me please to some documents on the integration of the TMS with our CUCM for planning?

    Furthermore, is it possible to have a single MSDS to perform the planning on the two CUCM registered CTS and saved VCS Tandberg endpoints end points, as well as to perform planning tasks for Community trade marks and MSE8000/telepresence Server?

    Thank you

    Hi Nick

    It is a very good question, and the bellows are drawn from the responses on the features that each product can provide you (CTS - Man and TMS) however as we know the TP Cisco world is changing and moving quickly if the bellows has been updated / changed and can someone comment on this topic will be great for us

    Meetings 1-booking

    TMS:

    -adhoc and meetings,

    -3rd-party endpoints reservation.

    -Ms Exchange, Domino, and API

    CTS - Man:

    -mainly used for endpoints STC booking

    -You can book and include cisco webex

    -Ms Exchange, domino and API

    2 features

    TMS:

    -End suppliers Multi points

    -Telephone directories

    -planning of conf

    -management endpoints (monitoring, Reporting, strong alerts... etc)

    -commissioning

    -integration with 3rd party such as Ms exchange

    -"There is no button to push" for the endpoints of CTS (you can add CTS alis for TMS rooms and book it or add the E164 of the external endpoint CTS as a participant and not these means are a button to push the meeting!

    CTS-MAN

    -integration of calendar

    -Midware between CTS, CUCM system and society of calendaring system

    -provide 'a button to push' scheduled meetings

    -provide interoperability simplified such planning via Cisco MXE

    -Live English option and CTMS geographical selection

    for each of them can provide you with options and features and its depends on the needs of your business, you could keep both or just go with one, if you have endpoints of VCS I would say for sure to the TMS

    HTH

    Marwan

  • TMS + CUCM telephone directories

    Hi all

    When you work with a complete CPU, composed of the following deployment:

    • CUCM (8.6/9);
    • VCS-C/E;
    • MSDS;
    • Jabber for Windows (CUCM);
    • Active component URI between CUCM and VCS.

    Ideally, in this scenario, I would that all of my Jabber for Windows clients to see all room based systems that are registered in VCS, when they try to get a system/user.

    I know that these directories are two distinct entities, does anyone know if it is possible to propergate the "all systems" TMS phonebook in CUCM somehow, or would it be a manual process?

    Thank you, if

    Hi Simon,.

    We are working on a solution like this.  If your room based systems were kinesiologist to CUCM, they show up in the directory for all your CUCM based systems.  I understand that there is a reason why you want to way keep your room systems on the RESUME for the time being.

    In the next version of TMS, we will see a new type of telephone directory of "CUCM", which are all systems configured in CUCM.  So your TMS direct managed or put into service endpoints will be able to see all systems no matter where they are registered.

    TMS systems are avaiable in directories CUCM is identified as a highly desirable item, but currently I don't have a timeline.

    Andrew - TME for TMS

  • TMS with CUCM registered devices

    I'm reviewing a BOM for a customer, and the current proposal has:

    CUCM 9
    Lane Express Core
    Side of the highway
    TMS
    vTelepresence Server

    Finally, I have checked, we needed VCS control to allow some TMS plan the server TP. With the current software (CUCM 9.x, TMS 14.4, etc.) can I use TMS to annex CUCM registered endpoints and TP Server, if the server TP is to shared resources directly to CUCM? There is no conductor in this deployment. Looking for a validation test.

    THX,

    Rob

    Hi Rob,

    Since version 14.4, TMS supports the planning of bridges that are shared resources to the CUCM, so limiting earlier 'all bridges must be deployed on the side of VCS' is no longer valid.

    However: TMS can plan only telepresence servers who are in managed mode locally. Telepresence virtual servers don't support not mode managed locally, so if you want distributes them TMS, you will need to put a conductor in the mixture.

    Kind regards
    Kjetil

  • CUCM (8.6 - 9) or VCS

    in the new videoconferencing infrastructure, which is the best option, only CUCM or VCS with CUCM?

    What is the future of VCS, if new versions of ex60... ex90 c20 sx20... come with direct integration with CUCM?

    Thank you all

    My Adviser for any installation of greenfield is to use CUCM; However, it does not entirely replace VCS, and it should in the near future. Here are some examples:

    • VCS control is always the product of call control recommended for video customers other than Cisco (Polycom, Sony, generic H.323, etc.). This is also the case for other types of interoperability (for example IPv4 to IPv6).
    • VCS control is always necessary for the travesal firewall Ascend/H.460 to work with VCS Expressway. Any call to the Internet would be CUCM--> VCS - C--> VCS - E--> Internet.
    • VCS Expressway is always required for any client capable non-AnyConnect located on internet to register; CUCM is not intended to be directly Internet facing.

    CUCM is Cisco Lighthouse call control platform and this will be the design choice by default unless one arrises specific requirement that excludes it. Perhaps, if the client doesn't have a Cisco UC today and don't ever be (which seems unlikely that frankly), you may be able to justify a VCS approach only. The days of a compartmentalized video compatible infrastructure seem well numbered.

    Please remember useful frequency responses and identify useful or correct answers.

Maybe you are looking for