VCS with TMS Cisco compatibility

Similar Questions

• VCS v8.6.1 will work with TMS v13.2.2?

  Hello

  I want to update the version of the software 8.6.1 the VCS C and E, but don't want to touch the TMS again.

  V8.6.1 will work with TMS v13.2.2?

  Thank you

  If you do not use TMSPE or Agent of TMS so I think it shouldn't matter.

  If you have MSD Agent or TMSPE enabled in TMS, then I think you must upgrade to the version the TMSPE support.

  VCS 8.7 is released the week next too

• Integration of control VCS with VCS ExpressWay

  Hi all

  I had to submit the question to your experience and knowledge:

  We will integrate a control of VCS with OS X7.1 onboard with an EpressWay VCS with X7.0.1instead.

  Is it going to work or will we need to have corresponding versions of OS/FW?

  If the latter, is possible to downgrade VCS - C OS without the need to have a maintenance and support contract?

  Thank you

  Andrea

  Hello Andrea,

  In my opinion, it should work. Only thing you should take care of bugs that could be corrected in the version of x7.1.

  If you want to downgrade the VCS - c software to x7.0.1, you will be able to do as the key to unblocking would be same for the x version 7 software.

  in my opinion it would be better if you upgrade the operating system version on vcs-Highway to x7.1 as the key to unblocking would be same and just download the software from the site and cisco unity upgrade.

  Thank you

  Alok

• Upgrading from 2.3.1 to 3.02 with TMS 14.1.1 TMSXE

  Hi all

  I ahev a general questions about the Migration of TMSXE 2.3.1 to 3.02 with Exchange 2003.

  Is there something to do? or might be a risk that I am loose all my calendar on the Exchange entry?

  It is also possible to upgrade to 3.02 in way tracking:

  1 detach the room (on 2003) mailbox-> is no longer to synchronize the calendar in the TMS

  2 uninstall the TMSXE 2.3.1

  3. now I'm clearly all booking resource on MSDS

  4. move / convert mailboxes to room mailbox to Exchange 2010

  5. installation TMSXE 3.02

  6. installation and configuration TMSXE 3.02 as New Installation

  7 configure the VC system with the associated mailbox room (Exchange 2010)

  Now the existing calendar entry are synchronously with TMS should beo OK.

  Any input appreciated for my questions.

  Best regards

  Georg

  Hello

  performing migration of 2.3.1 is possible and the process must be documented in the installation guide for TMSXE:

  http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/tmsxe/Install_Guide/Cisco_TMSXE_install_guide_3-0.PDF

  / Magnus

• Vcs Tandberg and Cisco VCS control

  Hello

  I have a client with an old would invest video and new servers.

  Old video servers

  Control system Tandberg video Communication Server - part number = 117500

  Application of Tandberg video Communication Server Expressway - part number = 1163402

  New video servers:

  VCS License Control - Part Number - R-VMVCS-CTRL-K9

  VCS Expressway License - Part Number - R-VMVCS-EXPWY-K9

  According to Cisco x8.2 Clustering:

  -Each peer runs on a hardware platform with equivalent functionality; for example, you cannot cluster one
  peer running on one core 2 average VM with peers running on base 8 large virtual machines

  Means that the physical old VCS cannot be grouped with new virtual VCS.

  Thank you.

  Hi zizou.

  You can include a device VCS with a VCS VM as long as their matches of software and their hardware platforms have equivalent capabilities.

  Device VCS clustered with VCS VM running on core 2 MediumVM = YES

  VCS machine clustered with VCS VM running on 8 cores LargeVM = No.

  "you can even cluster that are running on the standard devices with peers running on core 2 Medium VMs, but you can not group a peer running on a standard unit with peers running on base 8 large virtual machines.

  (p.4)

  http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/infrastructure/VCs/config_guide/x8-7/Cisco-VCs-cluster-creation-and-maintenance-deployment-guide-x8-7.PDF

• The CTS-CTRL-DVC8 is compatible with the Cisco MX200 G1 telepresence?

  Hi team,

  Please confirm whether CTS-CTRL-DVC8 = (Cisco TelePresence Touch device) is compatible with the Cisco MX200 G1 telepresence.

  Thank you very much.

  Sorry, misread the Gen1 in your message.  Yes, the 8 Touch works with old Gen 1 MX200 of TC software running.  This is mentioned on the MX200 data sheet.  Older hardware (MX Gen1 and C40/60/90) press the 8 only and cannot be upgraded to the new software for THIS.

• Problem with switch Cisco SG300

  Hi guys,.

  I have a problem with switch Cisco SG300-20. After the failure of the switch boots in a kind of mode. It requires

  MAC address and serial number to be entered manually for the device. I tried to find information on this mode, but without success.

  My question is: what is this mode and how to make the start switch in this mode?

  How can I turn on the switch in this mode on purpose if it happens again and I enter the wrong information by accident.

  Thank you

  Hi Aegx, this is a rare case where the switch basically forget his identity. Although the switch is recoverable, it is recommended the switch RMA.

  If you are certain that you have neither taken under warranty, all the information that is asked is on the bottom of the switch sticker. If the thumbnail is is not present you wouldn't able to do this is correct.

  In addition, if you make a typographical error, the switch will have undesirable failures that are permanent, such as the inability to update software.

• Question of EX60 with TMS and Callmanager.

  Hi all

  I have a saved on my MSD EX60 and works very well. But I need to make phone calls of this endpoint.

  The device is registered on MSDS which is another country (DE) and therefore on another call manager using his background and rules.

  The point is: is possible to keep the record of TMS to videocalls and register my callmanger to make phone calls?

  I tried to make the deployment process on the device... To receive phone calls from my callmanager works very well. Just phone calls. Outgoing calls continue smoothly in TO callmanager.

  I think it's possible to do. But I can't imagine how...

  Thanks in advance.

  Hi Daron,

  I think you take on commissioning.

  You must be commissioned with TMS for the phone book. at present on TC 6.3, you get so stocked TMS directory by CUCM.

  However, on the next version 7 TC, a device for CUCM pack will be necessary to specify the TMS as a source directory for the endpoints CUCM provisoned.

  at this point, you can either put into service with TMS or CUCM both.

  in case you need to call to SIP, this need to go through CUCM in sip and h323 default then Protocol should be h323.

• Adobe Reader 5.0 with Windows 7 compatibility problem

  Adobe Reader 5.0 with Windows 7 compatibility problem

  version 5?

  use the most recent Adobe Acrobat Reader DC install for all versions

  Clear mcafee, unless you are sure you want.

• Integration of TMS Cisco with Microsoft office 365

  Are there other APIs of reservation positions are to integrate the Cisco TMS with Microsoft office 365?

  In short, no.. Booking API is the only API document us and support.

• VCS VCS - E, TMS, TMSPE, Jabber/Movi authentication

  Just trying to figure the best way to approach this.

  I have read the documentation and the best approach seems to get to the VCS VCS-E to Active Directory and the synchronization of the TMS with AD for user account creation. This would avoid the need to records movi proxy for control of VCS and would ensure that all (SIP and H323) registration for the VCS-E would be authenticated.

  I don't think that my client will allow the VCS-E talk to AD.

  So, what are my options?

  If I SIP proxy of VCS-E records the VCS control, how are they managing H323? I don't want just any point endpoint h323 register with the VCS-E. I need to authenticate them. The customer has exernal h323 endpoints that they would like to sign up for VCS - E. I know I could put registration rules to restrict only some URI SIP, H323 IDs etc but it's really just security by obscurity.

  The local on VCS and VCS-E database can be used for authentication Movi/SIP and H323 records? I know that I would have to duplicate accounts and passwords on both.

  What books commissioning and address through registration to the VCS-E? Would it still work?

  Any suggestions on the best way to handle this in the safest way possible without breaking things?

  If I go with the control of VCS and VCS Expressway with authentication Active Directory (directly) on the control method of the VCS as described in the guide of authentication devices, I'm looking for the reality that I will not be able to restrict who can register for the VCS-E? At this time should I just seek to restrict the search for rules to only authenticated users?

  Thank you

  Jon

  Hey Jon,

  MOVI/Jabber you won't have to worry about authenticating H323. With your endpoints however you can just use the database local to authenticate or H350 (more can be read about in the guide of the Provisioning device referred to as Tomo). You can create a different generic for all your endpoints (less secure if which is discovered). But by combining this feature with a political appeal will ensure better security.

  I highly doubt that your client will allow you to leave the talk VCSE in AD. For movi/jabber users, you can create another subfield and use a regex pattern for point movi/jabber users to authenticate it as. * (\.movi)@domain.com. In addition, you can refer to this fragment and others have used in the past.

  In a secure design, the VCS (control and Highway) would require identification for registration information.

  The Control of VCS would have Active Directory Service active and joins the Active Directory domain. For VCS authenticate the credentials of Movi/Jabber on Active Directory before the SUBSCRIPTION for the supply is sent to the service of commissioning, the default Zone would be set to verify the credentials. For requests for SUBSCRIPTION from the highway, the area on the VCS control would also to verify the credentials. It handles authentication for the provision.

  The next part is the record of the Movi/Jabber client. The subzone to which the customer will register must also be set to verify the credentials. Here's everything you need for internal records (registration to the VCS control).

  For the Highway, things get a little more complicated. For commissioning subscription, the SUBSCRIPTION is forwarded to the VCS control. With the area on the VCS game to check the credentials, you're all set. Now on registration to the highway. The subzone to which the customer will register to must be defined to check credentials. From the motorway VCS don't have direct access to Active Directory, we use local credentials on the highway. A set of credentials should be configured in VCS Configuration > authentication > devices > local database. You will create a single name and password all Movi/Jabber clients will use. The end user has NO need to know these credentials. The username and password is provided to the Movi/Jabber client via configuration data it has received. To set up these data, MSDS, you must configure a SIP of authentication user name and password for SIP authentication in the configuration of the commissioning. For these options to be available, you must ensure that you have downloaded the configuration template xml for the Movi/Jabber version you are using. The xml file is included in the zip package full of the client which can be downloaded on www.cisco.com. So, who will be recording from the highway. Now, this creates an interesting situation with VCS control. The internal Movi/Jabber client will receive the same provisioning configuration and will attempt to use those same credentials when you register for the control of VCS. The VCS control is already set to authenticate against Active Directory and Active Directory ONLY registration.

  You will need to create an account in Active Directory corresponding to these credentials. The Active Directory account didn't need special access. It is used only for authentication purposes. A few things to keep in mind: SIP authentication user name and password for SIP authentication are stored in clear text configuration configuration. This means that the data is sent in clear text. To be sure that these data are not compromised on the wire, do not forget that you are using for your communication SIP Movi/Jabber TLS.

  With this directories will always work as jabber should be authenticated in order to receive directories. Your physical endpoint points will work differently with how they receive books and whether or not they are able to communicate with MSDS (unless you choose to configure endpoints also if those you are capable).

  It is in no way the design as safe as possible. It is to you to ensure that your environment is as secure as possible and therefore tested. The best way to fix everything is a well-defined appeal policy designed with your specific needs.

  The foregoing is in no way a recommendation but just a little more information to chew while looking to choose and implement what is best for you.

  Adam

• Problem with the Cisco VPN and Vista client

  Hello

  I have an easy VPN server configured on a c2811 and users use the Cisco VPN client. Lately, I have users running Windows Vista 64 bit and I need to know what is the correct version of the vpn client, I have to use and the compatibility problems with the server, I configured.

  Thank you and best regards.

  Cisco VPN Client doesn't have any version that is compatible with Vista 64 bit OS. The only customer that Cisco has released that supports the 64 bit OS's AnyConnect, but it is only supported on the CISCO ASA Appliance

• Report the user in Question TMS Cisco CDR

  Hello

  Any help with this would be greatly appreciated.

  I know that you can run the RDC in Cisco TMS user report, however, that draws its stats for all users within TMS. Is there a way to group users in a model may be to only run the report on these users?

  Thank you!

  Hello Mike.

  It is not possible to the users group when you run the CDR of the user report, it appears that all users.  The only option I see, you can do this, is to export the report to an Excel spreadsheet and manually group users as you want.

  If this is something you would like to see, you can contact your Cisco account manager and ask them to create a feature request for you.  However, with most devices that this report is based on (ie: video Jabber for TelePresence, EX60/90, E20), most to soon be EOS if not already, I doubt that they incorporate such an improvement.

• Warning in VCS and TMS (inherited from TMS Agent mode)

  Hello.

  I have this massage in TMS and VCS system, how this fix?

  in TMS: #2057 - Configuration Warning - The VCS is running in a mode inherited from the officer of TMS; It is recommended to switch your system to use another mode.

  in VCS: the VCS is running in a mode inherited from the officer of TMS; It is recommended to switch your system to use another mode

  How to switch different mode?

  Thank you

  If you are not Provisioning - remove the key to implementation of the VCS.

  In the web interface, go to the maintenance, options keys, select the configuration key and press delete.

  (it might be helpful to take note of the key first, where you decide in the future that you want to install it again - but it can be retrieved otherwise if you lose, IE from the Cisco Licensing Portal).

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

• VCS with a VCSE cluster

  I have a VCSC cluster I'm trying to integrate with a single VCSE. How to create areas of course? Can I have two different areas for the two VCSC in the cluster. I have a VCSC with a traversal active area and the VCSC 2nd with an area missed causing external calls entering the to this VCSC to fail.

  Sent by Cisco Support technique Android app

  Hi George,.

  Your VCSE is the server of your course and your VCSCs are traversal clients. You must create a separate traversal server for each system that is the customer of his career. Please see page 56 of the VCS of Cisco (http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/admin_guide/Cisco-VCS-Administrator-Guide-X8-1.pdf) Administrator Guide.