Cisco TANDBERG C90 Integration with Microsoft Lync 2010 *NEW*

This video demonstrates the video calling capability using the Cisco TANDBERG VCS (Video Communications Server) integration in the infrastructure to Microsoft's new Lync 2010 server. It is important to note that this works today with release software today on the VCS and the AMGW (Advanced Media Gateway). The VCS version is x5.2 and the AMGW version is 1.0. It is important to note that the AMGW transcodes the RTVideo codec from Microsoft into standards based H.264. The Presentation sharing in this video demonstrates desktop sharing from the C90 CODEC Profile TelePresence System

Category:

Science & Technology

Tags:

• Cisco
• TANDBERG
• CSeries
• Microsoft
• Lync
• Advanced
• Media
• Gateway
• AMGW
• Video
• Communications
• Server
• VCS
• TelePresence
• C90

[asmrani212]

Greeting all,

I did integration tandberg vcs with lync server . it's working fine.

My question when i do call from tandberg endpoints to lync lient the quality very good from tandberg endpoint side i can see the video from lync client very good. but the lync lient can hear me good and the video is freezing.

I'm not using AMG. The integration just between vcs controller & lync server.

Need your suggestions and experience.

Regards,

[mdrayton]

@asmrani212 You need to do a wireshark trace and work out where in the signalling and media stream something's not going to plan!

[emresumengen]

Is AMGW _required_ for sharing presentations, or only for HD video? I don't quite get it (sorry) :))

[mdrayton]

@emresumengen no the AMGW is not used for sharing presentations but when you do share a presentation from a video endpoint it will upscale from CIF quality to VGA or 720p. The AMGW is used for transcoding RTVideo into standards based H264 only. Note although you can share from a video endpoint (as the presentation becomes part of the video stream) - it won't work from MSFT to the open standard endpoint. This is because MSFT use CCCP which is not supported today by any open standards endpoint.

[lucky7521]

Is the VCS necessary for the SIP connection to take place or can you connect directly from your endpoint to a client?

[mdrayton]

@lucky7521 Also it's important to note to streamline management, scalability and the reliability of an enterprise wide solution VCS is critical. It is a single point of integration but it isn't a single point of failure as you can cluster the VCS. The SIP trunk is MTLS and the media is SRTP. As well as endpoint capabilities and presence being streamlined if you have other infrastructure products such as firewall traversal or video MCU's with this integration the MSFT client can also utilise :)

[cp444444]

@mdrayton So presence is supported for all C series codec? In order for presence to work with a C20 you will need to configure the FindMe function?

[mdrayton]

@lucky7521 Thanks for the question... Microsoft OCS or Lync can provide SIP registration as long as you understand "Microsoft's version of SIP" - so you can go down your local PC World or Best Buy and buy any SIP capable endpoint (voice or video) and register it directly, however in an Enterprise environment you may get strange and unexpected behaviour due to signalling incompatibilities. VCS provides integration in infrastructure so the user doesn't have to worry about the endpoint.

[lucky7521]

Is the VSC necessary for the SIP connection to take place?

[mdrayton]

yeah you can also configure presence. This is done by using the OCS relay function in conjunction with the FindMe software on the Video Communications Server. Apologies - I didn't configure it for this demo. When you configure this Cisco supports Online, Offline, Busy and In Call states for delivery to the Lync server.