Arne B. Østensen is the team lead of the Cisco TelePresence Solution Group in Cisco's Technical Assistance Center in Lysker, Norway. Before joining Cisco, he worked at Tandberg as a product specialist for telepresence infrastructures. He holds a bachelor's degree in computer science and engineering from the Norwegian School of Information Technology (NITH), Oslo. He has over four years of experience working and supporting telepresence products.
The following experts were helping Arne to answer few of the questions asked during the session: Andreas Wintervoid and Steve Hight. Andreas and Steve are top Voice experts and have vast knowledge in Voice and Telepresence topics..
You can download the slides of the presentation in PDF format Telepresence-webcast-presentation here. The related Ask The Expert sessions is available Ask The Expert:Cisco TelePresence Video Communication Server Update here. The Complete Recording of this live Webcast can be accessed TelePresence VCS Webcast here.
A. We do rigorous testing before and after code is released and we found a DNS issue, which we felt would be damaging to a very few customers, but damaging enough that we did not want to have it hence the removal of X7.0 and quick replacement by X7.0.1 which is X7.0 plus the one fix we have 100s of VCSs successfully running X7.0 and actually only seen the issue on 3 VCSs
A. We have now increased the total number of SIP domains to 200 in this version.
A. The X7 now support 10,000 credentials in its local database
A. You can upgrade from any versions newer than X5.1.1. So if you are on X5.1.1 or later, you should upgrade the VCS to X5.2 and then upgrade to X7
A. The X7.1 final is expected to become publically available in the February/March timeframe
A. You still need to use TMS 12.6 or later when using provisioning or FindMe
A. Its available for today for download.
A. All zones in X5.2 or later will be set to “Threat as authenticated”
A. You probably use Mozilla Firefox version 5 or 6? As Mozilla have updated their Firefox a couple of times lately, we just haven’t added these version is the supported browser list, which the VCS checks. If you are using a newer version than the VCS displays for supported browsers, you should be good to go, and the warning can be ignored
A. Yes, this is now supported.
A. Currently, we have limited this to 50 calls. The 51st call will get “503 Service unavailable”–response
A. VCS will be available in the first half of 2012
A. VCS products work best with OCS R2 and from X6.1 Lync is also supported. OCS R1 was supported in the early days ... and will still work, but Microsoft have improved a lot, so we do not recommend or support R1 any more preference is to use X7.0.1 with the new B2BUA to connect to OCS R2 or Lync.
A. Conductor is a kind of managing MCUs. If you have 2 or more MCUs conductor will find MCUs which is best fit for components you are trying to integrate and if you have pool of 30 MCUs and more participants and conductor will allign this based on the requirement.
A. The root login shell is available in X7.0 but we recommend only accessing it when instructed to do so by TAC.
A. As VCS moves forward with additional functionality and shared information in clusters, configuration is gradually moving to a different database and some config remains in xconfig.You will see that in X7.0.1 there are new system snapshot options - logging and status. These are needed to capture the logs and configuration that you used to use xconfiguration.
A. Increasing the log levels will increase the system load of the VCS, so the levels should only be increased when performing troubleshooting, and should be set back when troubleshooting is completed.
A. The VCS can interoperate with CUCM via a SIP trunk. Currently, the presence implementation which the VCS uses is not compatible with the presence implementation in CUCM.
A. The root shell is both valuable and potentially harmful. We are therefore doing our best to migrate various useful tools (For instance ping, nslookup and traceroute) into the VCS web interface to lessen the need to log into the root SSH shell.
A. It depends on the type of calling. If the call is interworking then you will use Traversal license and if the call is H.323-H.323 then in that case you will not use traversal license.
A. SIP<->H323 call is a traversal call and will consume a traversal call license on the VCS.
A. Running on VMware esxi version 5.0
A. X7.0.2 is due to be available by the end of the year. Not sure where the 'bugginess' of X7.0.1 came from; it has lots of fixes and good new features
A. Well we will have some kind of early trial release sonn for the Apple IOS and IPad to handle the device capability. More information will be released soon.
A. No - licences will be per VCS
A. Not available at present.
A. Each VCS support 2500 registration and you are able to have 6 VCS in cluster and 4 will be active. That means 10,000 registration is supporter per cluster.
A. DNS SRV is our recommended solution
A. We have cluster with more than 10,000 registration and its scalable. This is possible if you have more than one cluster.
A. If the SIP domain used for provisioning/Movi is identical with your AD domain, you shouldn't have to prepend the username with the domain. If the domains are different, then you will have to prepend the username with domain.
A. Yes it does.
A. Right now it cannot be registered with CUCM .
A. We are working to make this happen. Hopefully we will have a solution as VCS team is working to get this functionality.
A. Yes. You can upgrade from x5.2 to x7.0. In earlier versions you need to upgrade to x5.2 and then to x7.0
A. No. You always need the domain name and the username for authentication for Movi and AD.
A. All VCS deployment guides are available on www.cisco.com
Go to support > VCS and select configuration guide and there is a new X7 and B2BUA with Lync/OCS guide due out in 1 to 2 weeks. OCS and Lync guides are already available for older versions of VCS.
A. No, a backup should be performed by using the 'Backup and restore' page found in the 'Maintenance' section of the VCS web interface.
A. Yes, the deployment guide is called 'Authenticating devices' and can be found in the 'Configuration guides' section for the VCS on
Two documents exist. Please start with the TMS provisioning deployment guide to configure Movi operation. Once working then use the VCS device provisioning guide for the AD direct authentication and deployment guides for VCS on www.cisco.com
Choose support then VCS then Configuration Guides
A. Today only a single P-Asserted ID is used witin the video world. There is no reason why multiple P-Asserted IDs couldn't be used, but VCS will delete ones if the device does not authenticate
A. With X7.0, provisioned devices such as Movi and E20 can access the phone book via the VCS through SIP messaging, instead of getting phone books from TMS (This has not changed since X6.1).
A. This is not supported, if AD authentication is enabled on the VCS, then AD authentication will be used for all Movi authentication for Movi version 4.2 and higher. Movi 4.1 and older will however still use Local database or LDAP, depending on VCS config.
A. VCS Control and Expressway versions will be available
A. This is being worked on - expect to need CUCM version 9.x in order to work with encryption on VCS. Audio encryption does work in CUCM8.6.2 and VCS X7.0.1.
A. For provisioning, the Provisioning Deployment guide contains instructions on how to set up phone books for provisioned devices. For regular phone books, instructions can be found in the TMS documentation on www.cisco.com/support
A. The presentation can be now downloaded at https://supportforums.cisco.com/docs/DOC-19067