VCS - C and E

Similar Questions

• Control of VCS - H460 and punishment should be active?

  I have control of VCS and highway in production the sanction and h460 are both active on the highway, but inactive on the control.  Is this correct?

  I guess you saw the 'dormant' on a xstatus page https:///h323, right, or it is mentioned

  somewhere else as well?

  Maybe that Andreas might followed a request for improvement, because at least it can be confusing.

  On a VCS - C it appears in red (at least) letters on h323 config page.

  May not show at all on the vcs - c might be useful as well...

  In general h460 is a party which makes the highway a highway.

  If you would like to try for example to access to the

  https:///locallyregisteredendpoints page he would tell you that you do not have a license.

  H460 is a party that makes the fast lane of the motorway.

  So this 'inactive' is nothing you need to worry, this is the desired behavior. And its

  OK h.460 is not used on the SCV - c (this is not a bug it's a feature :-))

  If your firewall allows it and your VCS-E is set up to do this, you can try to register endpoint

  with the VCS E h.460.

  Generally when having strange symptoms its worth checking that there is no NAT help / Application

  bridge layer or what ever between the components involved and firewall ports are correctly

  configured and zone rules and the research of course are configured correctly.

  Read also the notes of publication and eventually upgrading to the latest versions of software.

  The course area has options has two h323 options that I would try to play in such a case:

  Demultiplexing "H.460.19" and "Protocol" mode (must be the same on vcs - c and - e).

  Andreas: What are the use cases of these parameters?

  In any case, his strange with his scrambled.

  J.House: Please note the answers using the star under the messages!

• Where can I find documentation on how to get the VCS - C and VCS-E to Exchange presence information

  I turned presence on my VCS - C and VCS-E, but depending on whether I am VPNed or not, I don't see the State of the presence of my side of the firewall.

  I checked for x7.1 Administrator's guide, I looked in the guide of authentication devices, and I'm at a bit of a loss.

  Is what I'm trying to do as possible, and if so, what do I have to do to make this work?

  I have a pretty simple setup - that works very well, could give you some ideas;

  Two VCS - Independent C (soon to be clustered) and a VCS-E;

  all internal clients of the JabberVideo register with a VCS - C, and when external registers with the VCS-E (all of my users of Singapore recorded with the VCS-E).

  Authentication is directly with AD and is made on the a WHAT VCS - C regardless of the user is registered with the VCS - C or the VCS-E.

  PUA and presence disabled on VCS-E and activated on the VCS - C, which is used as SIP registrar.

  Authentication on VCS - e:

  Default subfield "do not check".

  Default zone "do not check".

  Traversal server box "do not check".

  Authentication on VCS - C:

  Default subfield "audit powers.

  MOVI area 'audit powers.

  Point final SIP registration box "treat as authenticated.

  Course customer area 'audit powers.

  Authentication works well, the users cannot sign up for the VCS-E with the wrong password or user name, and presence works well too - both inside and outside.

  /Jens

• VCS - C and VCS-E switch to x8.7

  Hi, I plan on upgrading to VCS version x8.7 (of x8.2) to meet the needs of encryption for a RMC-cloud deployment and looking for some feedback from the community on a number of things:

  -I shouldn't need a key to unlock because the upgrade is the same version, correct?

  -J' need to upgrade the VCS - C and VCS - E with the same version of software, correct?

  N ' needs nothing to do away with the MCU? We are currently at version 4.5 software (1.45).

  Thanks for your help,

  Brad

  Release keys are only required if the major software version changes, minor changes for example, ranging from X8.2 to X8.7 does not require a key to unlocking.

  VCS - C and E must be on the same version, the only time where they should be on separate versions is when software updates.

  Nothing should be changed from the MCU.

• 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

• Call the flow of VCS-E and VCS - C

  Hi all

  I'm looking for some documents describing the call flow of VCS-E and VCS - C in H.323 as the jpg I have attached.

  (Especially when endpoint dials on internet to the intranet)

  Are there documents like tthat?

  Best regards

  Kotaro Hashimoto

  Call the stream while VCS - E uses the SANCTION for traversal Protocol (almost identical even use H.460.18 to signal flow).

  Please note that this call flow only not understand key messages each Exchange of messages between VCS & endpoint as well as VCS-E & VCS - C.

• 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

• VCS - C and VCS-E switch to 7.2.2 8.1

  Hello Experts,

  We want to deploy Jabber via Expressway Edge (ARM) solution and we must improve our course VCS-C and E servers (7.2.2).

  We have a few old polycoms I wonder if the upgrade of VCS may break legacy polycoms.

  TMS units and MCU does not require the upgrade.

  Recording methods recording of an endpoint of the VCS has not changed, so if your endpoints are now save correctly, they should continue to do the upgrade so.following.

  Support for some of the older devices of Polycom fell in new versions of TMS, so if you are considering upgrading from TMS at any time, you may need to close look at the release notes.

  Please note that it is changed a bit between X 7 and X 8 port, so make sure that before any upgrade, you had a good thorough read of version X8.1.1 and notes to any firewall for ports has changed.

  PS - You should X8.1.1 on the VCSes, not only X8.1, as X8.1.1 the OpenSSL software vulnerability patches.

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

• Is it possible to send an alert through TMS when a crossing box fails between a VCS - C and VCS-E?

  Hi all

  TMS has many features to alert, but I don't see an easy way to alert us to the fact that a crossing area may have failed between a VCS - C and VCS - E, or even neighbor or other types of areas than peers with other devices. Is this possible?

  As we now have a large number of VCS, it is important for us to know that these peering is active. It is not necessarily the case that individual machines become inaccessible, just the interconnection network fails for some reason any.

  Thank you very much

  Chris

  As much as I know tms cannot do that, she must be a feature request.

  / Magnus

  Sent by Cisco Support technique iPhone App

• Interoperability VCS control and Expressay - various versions

  Hi team,

  We settled on a client control VCS about 6 months. The customer has decided to buy, after this period, VCS highway as well.

  The version of VCS is x7.2 control and we are already in the version x8.2.1.

  My question is:

  There is some incompatibility between the VCS control version x 7 and VCS Expressway in x 8 version?

  Best regards

  VCS X7.2.x and X8.x backward compatibility were considered in depth since the published software X 8.  The following discussion is the latest X8.2 version that resolves the compatibility between versions X 7 and X 8 of the VCs.

  https://supportforums.Cisco.com/discussion/12240026/VCs-x82

  If you care to learn more about the compatibility of the software versions X 7 and X 8, you can take a look at this discussion, there are others out there as well, just look for them.

  https://supportforums.Cisco.com/discussion/11720871/VCs-Expressway-and-control-different-versions

• video conferencing through vcs-e and vcs - c

  can I make calls using video conferencing devices using vcs - c and vcs - e only? or is cucm involved in the process? also if I set my camera to call using only H.323 and SIP disabled, can I call sip addresses? also if im calling via vcs - c and vcs-e do I need to implement natting to the local address of videoconferencing unit? Lastly can someone please link any document on how to set my vcs - c and vcs-e and my videoconferencing unit to send and receive sip and h323 calls.

  "can I make calls by means of video conference devices using vcs - c and vcs - e only? or is cucm involved in the process? »

  If there are termination points recorded on the CUCM and want to call the end points on the VCS, CUCM is involved in the appeal process as the call goes through the trunk SIP between CUCM and VCS. Even also on the endpoints registered on VCS if they call endpoints on CUCM.

  If end points locally stored on the VCS and making calls to another, CUCM is not involved.

  "also if I set my camera to call using only H.323 and SIP disabled, can I call sip addresses?

  Yes, so that interoperability is enabled on your VCS.

  "also if im calling via vcs - c and vcs-e do I need to implement natting to the local address of videoconferencing unit?"

  No need. The VCS - c and VCS - e will do their work for calls of crossing of firewall. Until the end point is stored on the VCS then an area between these VCS are enabled, you can join located outside the network of endpoints and they can also reach your internal termination points as well.

  The Cisco VCS Expressway and the VCS control - Basic Configuration will be the guide you're looking for.

  http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/infrastructure/VCs/config_guide/x8-7/Cisco-VCs-basic-configuration-control-with-Expressway-deployment-guide-x8-7.PDF

  Kind regards

  Acevirgil

• VCS ExpressWay and control over the different Versions

  Hello world

  Can be used on a newer VCS Highway then control VCS?

  Currently we have a highway of VCS and a tester of VCS X6.1 running. I plan to upgrade to X7.2.1 and will temporarily have the South, the new version with the old version running control.

  I don't see any documentation that may not be completed. Especially since X7.2.1 had interop tests already performed with X6.x.

  Mark

  Hi Mark,

  Please check the following page 8, section "Prerequisites", document

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

  Prerequisites

  Before you begin the configuration of the system, make sure that you have access to:

  -Guide the administrator of VCS and VCS Getting Started Guide (for reference purposes)

  -control of VCS running the version X 5 or later

  -a PC connected by Ethernet to a local network that allows to route HTTP (S) traffic to the VCS

  -a web browser runs on the PC

  -a serial interface on the PC and the cable (if the initial configuration must be performed on the interface series)

  Answer to your question, there is no problem if VCSE and VCSC installed on versions of different software.

• VCS-Express and the integration of control VCS

  Hello

  I have the following question on the integration between VCS and VCS Express behind NAT devices.

  Control of VCS in the configuration of the area customer I will use the (Real) Global IP address location > Peer Address or I have to use the private IP address.

  Thank you

  Hello

  It depends on the interface how you have connected on the highway. So if you have two connected interfaces then the internal one is configured with a private address, and that you would use on the control to send traffic to. But to your question, I assume you have a connected only interface so you can use the public ip address for sent traffic of venture capital control.

  Ask if you need more information.

  Best regards / / Andrey

• 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

• Running the VCS 4 and ESX 4 and computer virtual on a PC using VMWare Workstation 7.01

  Hello

  I could not install on my PC Windows 7.01 vCenter. I was getting a "28035.Setup error". I was told that you can run vcs on a virtual machine, so I decided to create a machine virtual W2K3 just for my VCS. I have 1 VM ESX 4.0 and 1 VCS 4.0 VM on my PC. I'm using VMWare Workstation 7 to join my VM and vSphere Client on the desktop. How can I run VCS? Normally, it will show on vShere customer. Do I need to reinstall from the CD of vCenter? Any ideas? Thank you.

  When I try to add my vcs on the domain controller server

  I don't understand exactly what you are trying to add?

  Basically, what you need to run a test environment is:

  -a domain with DNS controller and - if you want - DHCP

  -Member Server windows on which you are installing vCenter Server

  -one or more host ESX (i)

  On your client, you must install the vSphere Client and connect to the server vCenter Server by using your credentials of the AD. Using the vSphere Client, you can add hosts ESX(I) and your installation configuration.

  André