Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CUCM not ready for Telepresence

We are completely re-designing our video-conferencing infrastructure and deploying Cisco's Telepresence solution. We have been trying to follow's Cisco's roadmap concentrating everything on the CUCM.

I have to say so far CUCM has proven not to be ready to host (register) Telepresence endpoints. When registered on the CUCM, we face to many problems are obvious things simply doesn't work. The main problems we have seen are:

  1. A Telepresence endpoint registered on the CUCM cannot get the TMS phonebook. Only the CUCM directory. So the users cannot have the video-conference/Telepresence endpoint directoy...
  2. There are no default SIP routes on the CUCM! So it is not possible to default unknown domain to the VCS-C which will route it to the VCS-E.
  3. Can't dial an IP address. You have to use a bypass explained in the documentation using an IP dialing prefix following pattern <ip prefix>AAABBBCCCDDD. Like if 7 is the prefix and 1.23.456.7 the IP address you have to dial: 7001023456007. I mean. sure it can work. But find me a single non IT end-user who can understand it and do it him/herself.
  4. We are facing curently on our 8.6 CUCM a SIP bug which make the endpoint fail dialing a Telepresence Server multipoint meeting using SIP (bug CSCty07061) (behavior described here). Should be solved in 9.1 but not sure yet (all our attempts to upgrade CUCM from 8.6.2. to 9.1 have failed so far)
  5. MCU & TP server are recommended to be registered on the VCS-C and not on the CUCM (so it can be used by Webex, external devices and internal legacy h.323 devices registered on the VCS-C) but when doing so, CUCM registered endpoints cannot escalate 2 ad-hoc meeting into a multipoint meeting as there are no video multipoint bridge ressources registered on the CUCM itself and it is not capable of grabbing them through the TMS it is registered on...
  6. Not to mention that there are still so many H.323 device and endpoints everywhere and that the CUCM doesn't handle it and apparently Cisco has no plan for it. So if we have to register endpoints on the VCS-C for H.323 anyway, what's the point of registering them as SIP endpoints on the CUCM. Simpler to have them registered both as SIP and h.323 endpoints on the VCS-C

Anyway, all in all, although Cisco is pushing CUCM as the center of everything, voice and video, it just looks to me that it is not ready for it. It is missing too many basic capabilities.

Does Cisco has any plan to fix any of these issues ?

Everyone's tags (5)
New Member

CUCM not ready for Telepresence

Hi Matthieu,

I think some of your points are already solved. For Video deployments on CUCM I would recomend to go to 9.1, because you got better URI routing, MTP with video aso.

1. As far as I know the next TMS version will support that.

2. This does not work with 8.6, but with 9.x

3. you could also make use of sip routing by dialing 123@ip. I didn't test that yet, but I'm going to, because I'm currently deploying a tp solution with systems registered on cucm

4. upgrade to 9 ;)

5. use conductor. With conductor you register the MCU to VCS and also use it as an media resource on CUCM. For one MCU/TS it's free.

6. Third party devices will still be registered to VCS in the future, because VCS is better at interopability.

Regards, Paul
New Member

Re: CUCM not ready for Telepresence

Thanks for your updates.

2 & 4 - I heard that 9.1 might solve these issues mentioned above and we would love to upgrade to 9.1.

We just spend 9 days, including 2 week-ends in a row full-time, trying to upgrade and guess what... it still fails. And we are talking about an upgrade from 8.6.2(a)-SU3 to 9.1.1 or 9.1.2. And we went back on forth with TAC support changing all sorts of settings redoing the install many times from scratch and we are still unable to upgrade...  the worst upgrade I've experienced so far !

So so far I'm unable to test if 9.1 will solve our issues and to which point...

3- Regarding point 3, yes there are many bypass. We've been trying couple, but none of them is transparent for the end user. I mean the bypass in the Cisco documentation described before does work but try to get a user to understand it and to it right...

And still as long as the endpoint is only registered as a SIP endpoint on the CUCM how do you dial an H.323 endpoint on the internet. VCS h.323-SIP interworking transcoding features works for registered endpoints, but I've failed to get the VCS translating a CUCM-registered SIP endpoint to an external H.323 endpoint.

1- for point 1 do you know when that new version is planned to be released ?

5 - For point 5, I'd like to use Conductor but in our case I'm making a deployment over 3 CUCM clusters, 3 VCS and 2 MCUs and 2 TPS. So conductor will not be free for us...

Re: CUCM not ready for Telepresence

You can definitely use VCS for SIP to H323 interoperability from CUCM endpoints.  Just make sure you have interworking turned on on the VCS, not just for locally registered endpoints.

There's no special configuration needed, just make sure that you have an appropriate search rule to change what CUCM sends (e.g. 1234@vcs-IP) into something that matches the H323 endpoints you are trying to dial.

By the way - the lack of TMS phonebooks is exactly why I haven't migrated yet - I hope they come soon!

New Member

Re: CUCM not ready for Telepresence

With the tests I made so far, even with the VCS interworking set to ON (not just locally registered endpoints), a SIP call coming from a CUCM-registered endpoint to an H.323 endpoint outside on the internet was not working. Might be something else.

By the way - then it goes back to my point saying that Cisco is pushing towards the CUCM when everything is not ready to go that direction. I guess it's all about waiting but for us who are deploying a solution now we wanted to do it according to Cisco's plan from the beginning (hence put all endpoints on the CUCM). Because if we register endpoints on VCS and have to move them to the CUCM later it will create problems with bookings as you purge the endpoints and re-add them and there's no way that I know to purge the scheduling and have TMS&TMSXE resync everything starting from a blank page

New Member

Re: CUCM not ready for Telepresence

ad 1. If you are a Cisco Partner, you can participate at the Voice of the Engineer Sessions ( Tomorrow is one about TMS, maybe there will be some news about that.

ad 5. There is now a new midmarket conductor for up to 50 calls, which will not be that expensive. For 2 MCUs and 2 TSes a Conductor would make sense to better use you the infrastructure. Or are there some reasons why you don't want to share resource, like different parts of the company own different infrastructure aso.


Regards, Paul
New Member

Re: CUCM not ready for Telepresence

I requested budget for a Conductor for next year but in the mean time I look like an idiot n front of my users. Look we just spend a hell lot of money on brand new video-conference systems and guess what you can't escalate ad-hoc meetings to multipoint on those new systems because we registered them on the CUCM as recommended ... We'll have to spend more money to do something we could have done should we have register the endpoints to VCS... but it works on the old stuff...

I am looking at moving all endpoints off CUCM onto the VCS until all Cisco pieces are ready but if I do that it generate problems on all conferences. See:

Again, I understand were Cisco is going and that integrating all those Tandberg and Cisco systems can not happen in a day but it has been years already and their documentation is recommending CUCM today.

CreatePlease login to create content