VCS & MSDS requirement

Similar Questions

• License of VCS & MSDS

  Hello world

  I need to clarify some doubts with permission of TMS and VCS:

  Our customers need to add endpoints SX20, the customer already has a deployment of TP with TMS, VCS Expressway & control, MSE8510.

  I have two options:

  1 - save the SX20 endpoints in CUCM and use of TMS for planning.

  -The permit required for CUCM 9.x: R-UCL-UCM-LIC-K9 (LIC-TP-9 X-ROOM)
  -The permit required for TMS 14.3.1: L-TMS-SW-PAK (LIC-TMS-100)

  2 - save the SX20 endpoints in VCS and use of TMS for planning.

  -The permit required for TMS 14.3.1: L-TMS-SW-PAK (LIC-TMS-100)
  -The permit required for VCS X.7.2.2: L-VCS-PAK (LIC-VCS-100), I'm not sure if I need this license for firewall VCS non-traversal?. If each SX20 is registred in VCS is not necessary this kind of license, right? Will be requerided if I need SIP-H323 o IPv4-IPv6?

  Could you please confirm if I'm wrong? Y at - it another option? Do I need other permits?

  Any other comments are welcome.

  Thank you

  Pablo

  Hi Pablo.

  If you add just additional end points, the easiest way would be to add to the existing deployment (option 2 above) rather than adding additional complexity with CUCM (option 1).

  According to the license on the current deployment, you may or may not need to purchase additional licenses.

  (1) to check their existing TMS to see if there are licenses available system (this is shown on the display main portal when you open a session (near bottom of box to the left).  If you need more, you can buy them - you don't mention how you add - but you can buy them in smaller than 100 packages if you need (IE a L-TMS-25 is 25 licenses of system).

  (2) check the VCS control the number of licenses currently installed (they are once again, on the first screen get you when you open a session).  Check the license limit and of leading figures - that should give you an indication as to the relevance any more necessary or not (that is to say, if the vertex figure is not closer to the limit, you will not need to buy more).  Again, you can buy them in containers smaller than 100. They allowed to 'simultaneous call', so you generally do not have one for each device.  If all calls are within one organization on the VCS, Non-Traversal licenses, you will need on the control VCs.

  Let us know how you go, or if you have any other questions.

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

• Client Jabber Viceo registry for VCS/MSDS

  Hello

  I am trying to record a video jabber VCS or TMS customer but his does not work. Whenever I was

  "Bad username, domain and/or password". Check spelling and caps lock.

  Do not know why. Should what I do to register a customer with username and password? VCSC and VCSe are configured for access from inside and outside VCSe.

  Is there a guide for video Jabber clients?

  Best regards

  Jason

  Hi Jason!

  You need a starter pack of VCS-highway or TMS (license + Movi licenses) and a VCS (with the option of commissioning key device).

  As you write VCSe and c its more likely that you do not have the starter pack.

  She has need of configuration and user creation, so it would work not just out of the box.

  The recommended method is the TMSPE, you will find here the deployment guide:

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

  If you have older versions of TMS/VCS you will use it (but I recommend you upgrade and use TMSPE!):

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

  In addition to this documentation Cisco for TMS, VCS and JabberVideo control.

  TMS:

  http://www.Cisco.com/en/us/products/ps11338/tsd_products_support_series_home.html

  VCS:

  http://www.Cisco.com/en/us/products/ps11337/tsd_products_support_series_home.html

  JabberVideo:

  http://www.Cisco.com/en/us/products/ps11328/tsd_products_support_series_home.html

  Jason: Please note the validations and define the thread if it's an answer!

• VCS on multiple cluster

  Hello Experts! I'm hoping to get help on the SCV Clustering... I know that with the VCS X7.1, it says that VCS clustering requires a configuration with the same cluster name on all VCS, same pre-shared key for cluster on all VCS communication and same feature option keys (i.e. provisioning, findme, H.323 - SIP gateway, etc.).

  That said, can someone please confirm if a peer of VCS can participate in a single Cluster VCS? Or - is it possible to have a single VCS to join two or more different VCS groups? If so, can you point me to the right docs?

  Hi Rose,

  You can not only VCS join 2 different groups.

  To join a cluster, you must have some common paramtere through peers as FULL, pre-shared key domain name.

  VCS only single entry to these settings so I don't see a layout in which you can not enter the FULL domain and pre-shared mupltiple.

  Hope this helps

  Kind regards
  Sagar

• Software Version Upgradation

  Hi Experts,

  We have Cisco VC configuration with details as below:

  1. Control of VCS with version X.7.0.1
  2. MCU 4501 with software version 4.2 (1.46)
  3. Codec C40 with version TC4.2.1.265253

  The existing installation works independently and not integrated with Cisco Call Manager. Now, since we need to integrate VC with Call Setup Manager 10.5, so, we must update the versions of above material according to the link thebelow

  http://www.Cisco.com/c/en/us/TD/docs/voice_ip_comm/uc_system/unified/communications/system/versions/IPTMtrix.html#pgfId-1163447

  So, my question is on the pre-requistie to keep in mind as any DRAM or we can simply upgrade to the latest version now and later on we can upgrade integrate with Call Manager 10

  Finally, I can find the firmware TC6.3.3 and TC7.3.0 to C40. Which one should I go to?

  regds,

  Aman

  You can go directly to TC 6.x or TC7.x if you want to, with all the different security issues, probably the best going with the latest version of the software. Just need a version key valid since it is a major release of the version you currently have.

  Looking to register your telepresence to CUCM codecs? If so, suggest you read Administration of running TC7.2 on 10.5 UCM endpoints.  If you plan to save your end points of CUCM, you CUCM destined firmware.  If you plan to save your VCS or use as a standalone codec, then the software package that you have surrounded in your image, it is what you want.

  VCS will require a release key as well, since it will be a major version upgrade, the latest version is X8.5 that came out last month. MCU requires that no key release at all, so you can improve it without concern.

  If you have valid support contracts you can get the keys to release of Cisco Licensing Portal, select "Get the other licenses", then "Telepresence Software Release Key.

• 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.

• Cisco VCS - C keeps filling in Purge on MSDS systems

  Hello

  I have a very weird question that is quite difficult to explain. We had a few failures of Fan on my Cisco VCS - C and we did a RMA number and received a new one. I installed this VCS in April this year. I start then notice every time we add a new system to their MSDS ID TMS is of the order of 2860. We have only 42 systems at this stage. Then I noticed when I'm in the systems tab Purge TMS keep my new Cisco VCS - C, populating the name of the system and the type of system, this product about 2800 times. Someone else experiencing something similar to this?

  I'll try to purge these systems, the only thing is that this happen, what can I do else do I completely purge my VCS of TMS and readd it?

  TMS system IDs are generated by TMS and increases when you add several systems.  You might be able to change the ID of the SQL database, systems are stored in the dbo.objSystem table, but I do not recommend because the ID of the system could be used elsewhere and you can potentially break TMS and make things worse.

• VCS StarerPack + MSD - reports

  Hello

  Customer a VCS Starter Pack + TMS for the management.

  I know that VCS Starter Pack more than TMS does not support the report files. He don't suport. not all reports of type or kind of reports?

  Custome really want to get TMS reports, what can I do to fix this?

  Thank you

  I never tried to add a starter pack to TMS, just out of curiosity, have you tried it?

  I would say that it needs to be upgraded to a full VCS - E + Movi to do this.

  (at least the documentation given).

  If he has managed in TMS end points at least the call Info

  but you will not have the movi stats (which are not so good in the TMS standard reports in any case)

  and anything else related to the VCS-CDRs.

• Cisco VCS-highway network Dual interface option key required

  Dear expert;

  I'm new on TV Cisco presence.

  We have below BOM ordered by the customer as well as the VCS-Express is device without network double button Option Interface.

  Now they have made the redundant system with VCS-highway in VM and want to use Nating for which we need double Network Interface license key option.

  How we get this.

  Appreicate your valuable response.

  The option key double network is provided with virtual VCS, however, is a separate post for the VCS material, to enable network features dual on your existing hardware VCS, you will need to order LIC-VCS-DI.

• Purchase MSDS is required for RemoteObject?

  The language reference indicates at the top of some class descriptions that Flex Data Services is required to use this class. However, I installed Flex without SDS, and I use some of these classes (notably, RemoteObject) without problem. Of course, I can't use the FDS services that require the installation of the FDS package; but it seems that I am able to use RemoteObject (and other classes that are marked as "Adobe® Flex™ Data Services 2 only") even if I have not installed FDS. Anyone know if I will have problems on the road? Is it legal for me to use these classes?
  
  Thanks much for any input on this! Of course, I want especially to hear something official from Adobe!
  
  Andy
  

  It's really not a license issue as a technical issue. It is possible to use RemoteObject without FDS or ColdFusion or LCD screens. As long as you connect to something that has a compatible AMF protocol, you can use RemoteObject. However, that is not to say we won't reorganize some SWCs and put the classes related to the server in SWCs available only when purchasing a package of Data Services.

  You can certainly use HTTPService and WebService without any of our server-side products.

• TMS and virtual VCS

  Hello

  I know that the VCS and TMS can be virtualized.

  On the documentation, I found that the VCS can be deployed on the same host as the other virtual machines (cohabitation) following some guidelines for sizing (resourses must be allocated 1:1, it means that there is no excess applications).

  I also read that MSDS can also be virtualized, following the same guidelines of resources:

  "Cisco TMS can be installed in a virtualized server environment as long as the virtual machine by a Cisco TMS is allocated sufficient resources dedicated to meet the requirements of server and hardware for installation. The resources allocated to the Cisco TMS server instance must be dedicated and not shared with other instances of server. ""

  What I do not know if the TMS accepst co-residensy with other applications. Which makes me doubt is:

  "Cisco TMS is resource intensive with specific server requirements, which increase with the level of activity and the size of the managed network video. With the help of a server that hosts other applications or Web sites for accommodation Cisco TMS is therefore not supported. "

  I don't know if this means that non-corresidensy is supported or that no other application in addition to TMS must be deployed on the same OS.

  What I really want to accomplish with it is to virtualize the TMS, the VCS Highway and control of the VCS on the same server of UCS. Would it be supported by TAC?

  Kind regards

  Hi, this means that the TMS server should be dedicated to the application of TMS. No other hosted applications should be present on the same OS.

  Hope that helps.

  Sent by Cisco Support technique iPhone App

• 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

• VCS - sense VCSE

  Hey there,

  So, I got the mandiate to get our VCSE to talk and work fully with our VCS... and to do it in 1 day, oh and by the way, I have no idea what I'm doing... I have the config General vcse made with IP and other and VCS and VCSE can ping eachother, so we're good up to L3. There can someone be so kind as to explain the main steps in making these things work together? I created a zone of customer journey control vcs to vcse and a crossing area of server vcse for vcs... But the VCS, displays the message: ' SIP: Unknown "and VCSE shows"failure "... I have set up a search rule on each and associated with the zone pointing to each other about everything for... Alas, they claim that they do not speak.

  Here are some general questions:

  Should I make the VCS and VCSE a cluster? and why? I can do what I do without cluster configuration?

  We have a TMS, is required to get VCSE to connect to MSDS? and if so, how is this work?

  I appreciate your kind help!

  Steve

  Check:

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

  And other information available via:

  http://www.Cisco.com/en/us/products/ps11337/tsd_products_support_series_home.html

  Make sure your firewall is open and that you have not any nat-helper, alg, or other features enabled on the router/firewall.

  You can find an info of firewall on the site of cisco doc as well.

  The destination port of the tcp packet must be 7001 (or what ever is configured on the VCS - C - E.

  the source port is not really serious and if his behind nat may even have changed.

• Cisco VCS Expressway / Starter Pack = part number / Option key

  Hello

  I m a bit confused about ordering cisco information. My document: http://www.cisco.com/c/en/us/products/collateral/unified-communications/...

  First what we want to do. Quick and short: LAN-MCU -/- DMZ-VCSE VM -/-

  -set up a new environment VCSE only for remote workers.

  -ensure the video service just over the internet for Jabber and SIP/h.323 conference systems

  -only the MCU as a peripheral local registerd to provide several conferences

  That share and option key is therefore the best choice?

  Our plan:

  VCSE:

  R VMVCS-EXPWY-K9 (comes with the Cisco telepresence video Communication Server(OVA file) Network Interface feature, characteristic of the motorway, gateway functionality, 1800 TURN relay Option, VCS-Dual)

  1. what inscriptions? There are 2500 built-in?
  2 what of interoperability feature for h.323/SIP? CAN´t find in the list options.

  Options:

  LIC-VCSE-50, LIC-VCS-OCS

  Now the thing of Jabber:

  We want to connect on WAN Jabber clients. This is why the VCSE STRATER PACK has the nice feature of 50 video of Jabber Cisco TelePresence licenses with management in there. But if we get that the CTI-VCS-STPAK-K9 instead of the VCSEVM, we have a limitation of 50 records and 10 calls trasversal, right? Only then the VCSE is intresting (culture and systems to support), but we want the Jabber options on it without buying an MSD.

  1 can we install the CTI-VCS-STPAK-K9 key as an option on the VCSEVM and Jabber use 50 records without losing other features of Highway?
  2 or is it possible to install the CTI-VCSE-SPUPG-K9 key as an option to enable Cisco Jabber 100 user on this VCSEVM?

  Or do we buy the CTI-TMS-SW-K9 with LIC-MOVI-25 (the different today: LIC-JAB-MOB-25, LIC-TMS-EP-25)

  Thanks a lot for answering

  One of the first things I would consider on VCS Starter Pack is that it is almost end of sale, first of September 2014, so think of this forward.

  / EOS-EOL-Notice-C51 - 731300.html

  • What these records? There are 2500 built-in?
    • A single VCS will support up to 2500 records out of the box with a valid key.
  • As for the functionality of H323/SIP Interworking?
    • Interoperability is supported out of the box as long as no separate option key not required.
  • Options: LIC-VCSE-50, LIC-VCS-OCS
    • LIC-VCS-OCS is necessary only if you plan to integrate with Microsoft OCS/Lync VCS, otherwise it is not necessary, especially for the video of Jabber.
  • Can we install the CTI-VCS-STPAK-K9 key as an option on the VCSEVM and Jabber use 50 records without losing other features of Highway?
    • The VCS Starter Pack is a separate server from the VCS control and highway.
  • Or is it possible to install the CTI-VCSE-SPUPG-K9 key as an option to enable Cisco Jabber 100 user on this VCSEVM?
    • It is possible to upgrade a VCS Starter Pack for VCS control or a highway, but you will lose the original pack starter call licenses and Jabber video optoins, like they are not transferable.  The licenses or options you have purchases on top of the basic starter pack will however is transferable.
  • Or do we buy the CTI-TMS-SW-K9 with LIC-MOVI-25 (the different today: LIC-JAB-MOB-25, LIC-TMS-EP-25)
    • If you buy the VCS Starter Pack, it will manage the delivery of Jabber video for you.  If you buy a highway of VCS, you can also buy MSD and install Extension of provisioning of TMS is free.  To use TMSPE, you will need provisioning option keys installed in TMS, the difference between the start-up option keys are simply the types of devices you can fund, all kind of do the same thing really, but for the video of Jabber, you want to ICA-MOVI-XX.

• 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