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

Tags: Cisco Support

Similar Questions

  • CUCM + MCU + CISCO TMS integration

    I'm marching integration with MCU 4.5, 10.5 CUCM, sx20 and TMS 14.5

    According with manual bellows

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

    I ve done a Deploying an MCU as a multimedia resource for Unified CM.

    MCU has a SIP trunk with 10.5 CUCM, MCU is recorded as the Conference on the multimedia resource.

    SX20 Conference ad hoc works well with another 7 codecs.

    My question is

    I want to plan conferences by mcu or cisco TMS, but I am not able to do.

    How can I integrate Cisco TMS or planning by MCU?   It s not working not on my side.

    Hello

    Please see the following guide

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

    HTH

    Manish

  • Question about commissioning of the E20s - CUCM and TMS

    If we now run software CUCM 8.6.2 and 4.1 E20.  I played with CUCM and TMS supply by and a few questions.

    It seems that there are some features that can be set via the TMS models that cannot be resolved via CUCM (MTU, custom, etc commands).  Is it possible to apply these settings through TMS while having the unit registered in CUCM?

    Essentially, I want my call recording platform CUCM and control, but want to keep the granularity that TMS offers in terms of commissioning etc..  I expect the same problems with C-series, etc.

    Am I right in saying that, in order to get the E20 to join CUCM, I need to define the external Manager to "CUCM", and thus eliminate any possibility of TMS to manage? Otherwise, what is I could have managed by TMS and then set the SIP of the E20 to point to CUCM via templates in TMS?

    Any tips on that?

    Hello

    Having both TMS and CUCM to manage endpoints is not a good idea (yet). TMS and CUCM will return to each of the other toes with unpredictable results.

    With TMS 13.2, I understand that you should be able to import the CUCM in TMS and then find all systems registered to it and import these into TMS, however in this case TMS plan only systems conferences and will manage them not active (you can see status of the call as well).  13.2 TMS is not yet released, so that's what I said must be in this version.

    So basically now if you use CUCM, use CUCM provisioning and don't use TMS.  We focus on interactions with systems registered with CUCM TMS and it will be more developed on this in the future.  I recommend you check out the TMS13.2 release notes released to see if it is mentioned.

    Thank you

  • Import and export directory for CUCM and TMS

    How can I configure TMS and CUCM use of TMS directory for an endpoint registered to CUCM? I've added to TMS but and TMS can shoot CUCM Phonebook, but how does he see the directory for other infrastructure in TMS to fill in the directory of CUCM CUCM?

    If the endpoint of telepresence is running TC7.0 or later, you can configure in CUCM using TMS as a source of spare phone book, there are also TMS 14.4.  Refer to the Administration of the TC on CUCM 10.5.1 endpoints (TC7.2) on page 24 for more information.

  • Conductor XC2.2 and TMS 14.3 automatic connects

    Hello

    I've also seen a topic on current versions of beta XC2.2 conductor and TMS 14.3, so I'll post my question here.

    I use the conductor with VCS, CUCM, MCU 4505 and TS. I am able to create ad hoc via CUCM and VCS and regular calls through TMS conferences.

    If I create a conference with automatic connect and the conductor in the call I can see that the MCU or TS tries to achieve a participant, but not with the URI. To use my email address (findme ID) to call me, but instead, it uses strange URI identifiers: [email protected]/ * /: 5073

    1.1.1.1 is the IP address of the driver. On the front part @ I do not know where it comes from, but it looks like an internal identifier.

    These are the logs of the MCU for a test with a participant conference to be connected automatically:

    13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: "Videokonferenz 101" is

    13307 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], numerische Favorites auf ID '88800010 '.

    13308 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], pine Favorites auf "114".

    13309 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], Gast-PIN options auf "114".

    13310 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [101 Videokonferenz], busy 'public '.

    13311 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] content mode set to 'convert '.

    13312 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] Stummschaltung EIB participation [Audio = deaktiviert]

    13313 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] Stummschaltung EIB participation [video = deaktiviert]

    13314 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [101 Videokonferenz], Layoutsteuerung uber FECC/DTMF "use FECC and relief to DTMF".

    13315 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], maximum Dauer Favorites auf 'permanent '.

    13316 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], Ende Favorites auf "kein Enddatum.

    13317 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] auto remove time limit set to "600 seconds".

    13318 13:38:06 admin API /HTTP/TCP/1.1.1.1:38141 API-Endpunkt-Einstellungen Info: Endpunkt [e922d880ee1854c242ba94e69b113af: [email protected]/ * /: 5073] via API zu Conference "Videokonferenz 101" added

    13319 13:38:06 admin API /HTTP/TCP/1.1.1.1:38141 Info API-Endpunkt-Einstellungen: Endpunkt [3805: [email protected]/ * /: 5073] via API Conference "Videokonferenz 101" added zu

    13320 13:38:36 API admin /HTTP/TCP/1.1.1.1:38149 Info API-Endpunkt-Einstellungen: Endpunkt [3806: [email protected]/ * /: 5073] via API zu Conference "Videokonferenz 101" added

    Unfortunatetly newspapers are in German, but I think you can see that there are a few strange added URI.

    If I create a conference without a conductor the log shows the URI:

    13386 14:07:14 /HTTP/TCP/172.21.10.12:52001 Info API-Endpunkt-Einstellungen admin API: Endpunkt [Paul Woelfel: [email protected] / * /] via API zu Conference ' 1234 - Videokonferenz 07/08/2013 "added.

    1.1.1.1 is the IP of the conductor (of course not the real IP ;-))

    Someone at - test the latest versions as expirenced this question?

    Hi Paul,.

    You use the conductor and VCS B2BUA deployment? If so, this behavior is correct. MCU must not call endpoint directly, MCU must compose a unique URI of the driver, something like [email protected]/ * /, so Condcutor will take this URI and route the call to VCS replacing this strange URI of the right destination SIP URI according to what you have planned.

    But to make it work, MCU must not be registered for VCS, MCU should only be integrated with driver, without registration, SIP and H323 for VCS.

    Can you confirm what type of deployment you have? What integration between your MCU and conductor?

    Concerning

    Paulo Souza

    Please note the answers and mark it as "answered" as appropriate.

  • Problems with VCS - C, VCS - E and TMS

    I hope someone can help me because I nearly pulled my hair with this problem.

    We have a VCS - C and VCS-E the two X7.2 running.  Our TMS runs 13.2.1.  We used it for several months with the 'transfer', which worked well.  Recently, I am currently having of Movi/Jabber clients authenticate via LDAP/AD, in addition to using local accounts (we have some vendors and partners who register through our infrastructure).

    I have gone through all the documentation and think I have it configured correctly, however, things work behind what I need them for.  Currently, a client who is on our internal network can sign up by using the credentials of the AD, but may NOT use local credentials.  Customers who are outside our network can register using the information of local identification, but NOT using their AD information.

    My configuration on the devices of VCS is:

    VCS - C

    Credentials of the default TextBox control

    Course credentials Check box

    By default, subarea treat as authenticated

    VCS-E

    Course credentials Check box

    SIP Proxy record tried Off and known Proxy Proxy at all.  Currently set to Off

    What I'm missing here as I'm more on the side things CTS and just try to learn the VCS Cisco Tandberg product?

    Thank you

    Allen

    Allen,

    When you enable the NTLM protocol challenges on your VCS - C, this means that only NTLM authentication will be used for devices that support NTLM, namely Movi 4.2 and later, video Jabber 4.3 and more more Jabber for iPad. Other devices that do not support NTLM authentication will use either the local database or LDAP authentication, depending on what you have set up on your VCS.

    Is there a particular reason why you want to use Digest authentication and NTLM for video devices Jabber?

    -Andreas

  • AD authentication environment VCSe, VCSC and TMS

    Hello

    We have VCSe, VCSC and TMS work with commissioning on the VCSC through TMS.

    VCS, Version 6.1, 13.1 TMS

    Movi (4.3) external Clients have registration with the VCSC. VCSe does proxy registration.

    Users have been configured on the MSDS. There is still no configured AD authentication.

    Everything works fine.

    We now want to configure AD authentication.

    There are several deployments to do, but for me, some of them are not so sure than others.

    I need a top secure deployment.

    I need ideas to make the deployment.

    Thank you

    Martin

    Hi Martin,

    I understand perfectly what you want, but I do not understand why. When you set a directory of provisioning in TMS to be integrated with AD, users are imported automatically according to the 'search string', that you are configuring. But passwords are not imported from AD, basic information only from users are imported. When any user try to connect, TMS challenge for authentication in real time.

    For me it is not a problem, because the MSDS do not save passwords in its own database. Is this a problem for you? Why?

    If you try to do it only because you want to limit which users are allowed to use the customer Movi, if your problem is the following, so you can solve it by using a 'search filter' in the configuration directory configuration, so that you afin que vous serez will be able to import only users who belong to a specific group, for example.

    Please, explain to me why you want to do.

    Paulo Souza

  • Failed installation of CUCM IM and presence in be6k

    Dear all,

    There is a new facility in our lab on be6k, we have completed the installation of CUCM.

    However, we cannot install the CUCM IM and presence in the be6k in the section "first node access configuration.

    Please refer to the photo 1/2/3.

    I created the password of security during installation of CUCM, however, it incorrect report in CUCM 1 M and the installation of presence.

    Please comment on this issue.

    Thank you very much.

    Best regards

    Benjamin Lai

    Hello

    -Can you confirm if IM & P server is added IM & P in CUCM under system > server?

    -Is the NTP on accessible CUCM (open SSH > ntp utils status)?

    Thank you

    Shadi

  • Do we need to purchase the license to upgrade the VCS, VCSe and TMS?

    Hello

    We need to get a new license when upgraded version of VCS, VCSe and TMS?

    Hi Kelvin,

    xxx. OVA files are package files to deploy the VCS on virtualize platforms.

    Release key are required to upgrade the VCS for major updates. for p. ex. upgrade of x 6 x 7 software version worm.

    However for improvements minor as x7.2 to x7.2.2 these are the released hotfix version or bux fixes release and you don't need a license for this upgrade.

    in any case if you your devices are less covered by valid contract you can get the license key anytime just contact cisco license team on "[email protected] / * /" and they should be able to provide the necessary license.

    Rgds

    Alok

  • How to take backup for VCSC, VCSE, MCU and TMS. I'm new in the world of video. A brief step by step would be appreciated

    How to take backup for VCSC, VCSE, MCU and TMS. I'm new in the world of video. A brief step by step would be appreciated.

    You can back up each server by following these steps:

    For VCS, see "Backup and recovery of data from VCS" section in the Cisco VCS Administrator Guide X8.5, page 340.

    For MCU, see "upgrade and save the MCU" section in the Cisco Telepresence MCU series online help 4.5, page 212.

    For MSDS, see back up and restore SQL Server databases you will back up the database of TMS 'tmsng' of the SQL Server itself.  It could either be hosted locally on the TMS server if you have installed TMS with the default settings, or an external user provided SQL server.

  • Dx80 CUCM 9.1.2 and TMS 14.6

    I have the same problem as on this post: Dx80 on CUCM 8.6.2 and 13.2 TMS

    I have the DX80 registered on our CUCM correctly but when I go to the TMS, I can't remove it from the CUCM.

    But with CUCM 9.1.2 with the last set of device (9.1.2.14089 - 1) and 14.6 of TMS.

    In TMS, when I enter systems > Navigator > settings > extended parameters

    DX 80 does not appear in the list of supported devices.

    Cisco has a plan to change that?

    Hi Matthew,

    There is an improvement open to follow this

    https://Tools.Cisco.com/bugsearch/bug/CSCup84943/?reffering_site=dumpcr

    TMS Support for DX series
  • Integration of CUCM 8.6 and CRM, what service API or XML?

    Hello

    Asked me to find documentation on the developer interface CUCM. We would like our CRM system to connect to CUCM and receive CID/CTI and duration calls real time to start.

    Which way we look? Our CRM supplier must watch AXL interface or XML functionality for the call real-time data? or in another way? any suggestions?

    Thank you

    Kristian

    Data in real time would require the TSP that provides the TAPI interface or JTAPI to subscription to the devices/DNs via CTI Manager. XML interfaces you mentioned are for administrative functions. ICT applications can impact the scalability of the CUCM pole so plan accordingly.

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

  • Integration of CUCM LDAP

    We are currently running CUCM 10.5.1 and using all users the.  We want to Setup LDAP integration, and I try to understand what services will be performed.

    Can someone inform me what services use the database of the CUCM end-user for authentication?  I guess it's only administrators who log on to the Web site and the Jabber clients.  Is there any other use of these credentials?

    Are there any other warnings should I be concerned?  A thought is that I do not want to import a bunch of accounts of service or distribution groups, so I need to put some LDAP filters.  Are there other traps that I should know about?

    If you enable access for end users ccmadmin, they would use their LDAP credentials for this, if you set UCMuser, for this as well. If you use Jabber, too.

    There is a filter by default for what to import, documentation of CUCM to LDAP synchronization is, what source directory you use, only users will be imported, you can change it if necessary.

  • Cisco unity conn cluster integration with cucm cluster best practices

    Hi all

    I'm trying to integrate a cucm with a cluster of cuc 9.1 9.1 cluster. Some confusing points that I hope can be clarified.

    for cucm

    1. I created a voicemail with 48 ports server that will satisfy both servers of cuc

    for cuc

    I created a phone with two groups of ports system.

    two point of Group on the same server port voicemail prefix but different servers cuc. each pg also has a different sequence of the tftp servers.

    the problem with this design is that voice on the cucm ports not recorded with the port group that is configured to point to the cucsub. port groups cucpub point fits very well.

    Is how to configure the integration of a cluster of cuc. I saw the guides but it is more oriented towards stand-alone configurations.

    Help please!

    The SRND for CXN stipulates that all calls should be directed to the Subscriber with the Publisher handling overflow beyond the capabilities of the Subscriber and/or failover when the Subscriber is offline. They should not be balanced alternating.

    You can create two servers of voicemail with the wizard and give them separate device classes if you need to register for the various nodes of CCM.

    PS - You can also avoid this mess of all of the port on CUCM by integrating on SIP instead of SCCPS. In this case, you still have the CXN ports but they are only logical entities; CUCM has just a SIP trunk to each node. There is a separate for this integration guide.

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

  • Why did did you spent much time for the integration of the Pocket and not in the resolution of the 'impasse' - vulberability?

    The deadlock problem solved no?
    I think it is more impotant than the Pocket-integration.

    You can also switch the prefs involved to false on the topic: config page.

    • Security.SSL3.dhe_rsa_aes_128_sha
    • Security.SSL3.dhe_rsa_aes_256_sha

    You can open the topic: config page via the address bar.
    You can accept the warning and click on "I'll be careful" to continue.

Maybe you are looking for