This has been in the pipeline for a little while where I work, but so far we have been unsuccessful at making this happen. Although our attempt today was a pretty minimal there seems to be new security restrictions around OCS R2 that may make this a little more difficult than I would like. In particular we are looking to integrate the Tandberg VCS straight to OCS rather than registering Tandberg endpoints to OCS. I will post back when we have made some more progress but all I succeeded in doing today was breaking Exchange UM integration to OCS when messing with OCS settings. Lucky it was only in the lab.
For anyone interested here is the integration documentation.
Hi,
ReplyDeleteWe are trying to accomplish the same task here. Can you share more about the experience?
Thank you
samer
Hi Samer,
ReplyDeleteJust so happens we were actually working on this the last few days. I will take some time to write a small summary of how far we have come along in the next few days. At the moment we are still in the figuring out the exact setup but we have made a successfull call from a Tandberg endpoint to a OCS endpoint.I will put the rest of the details in my blog entry.
Cheers
Chris
Chris,
ReplyDeleteDo you think you will have time to blog about this anytime soon? I'm trying to get an MXP device to register with OCS 2007 R2 and I'm not having much luck. Any input would be greatly appreciated.
-Jamie
Hi Jamie,
ReplyDeleteHaving a device like the MXP directly register with OCS is not something I have had a lot of experience with other than one time. From memory it wasn't to complicated but with all these integrations having the right firmware image on your device is critical for success. I will look into it and get back to you soon all the same.
Cheers
Chris
any updates on this guys? thanks!
ReplyDeletevic
So I have had a recent job change so immediate access to the deployment I was working on is no longer available. Last testing was successful with a completed call between OCS and Tandberg via the Tanberg VCS . This was only completed with help from Tandberg due to some issues with SIP domains and turning off encryption at the endpoints. So it means allowing OC to accept an unencrypted call(media only) and turning off media encryption on the Tandberg endpoint. TLS works fine.
ReplyDeleteAs for registering Tandberg endpoints regeristering with OCS this is something I will put on the list for a blog entry. Been a bit slack on this point but it is something I am reviewing at the moment.
One of the outstanding issues is that you cannot make a cal through the Access Edge to VCC. MOC uses ICE to negotiate around IP and NAt issues and VCS does not support he Microsoft implementation of ICE.
ReplyDeleteWhich is a totally valid point. Tandberg doesnt support ICE and requires its own proxy. This is totally different than Polycom who do support ICE STUN and TURN and can take advantage of the Lync/OCS Edge. Tandberg on the other hand has decided that using their own proxy is a better solution. Since the aquisition by Cisco their willingness to do extended interop scenarios has lessened where as before they were one of the leading interop companies.
ReplyDelete