We manage a relatively large number of organizations in the Public sector (Education, Governmental and non-profit etc) here in Wales (around 75+). We provide them with the necessary infrastructure to make a receive video calls, and we manage their internal video conferencing systems - the infrastructure essentially boils down to Cisco VCS devices that enable gatekeeper and SIP registrar functionality, dial planning, and firewall traversal. A third party provides external MCU and videoconferencing booking facilities for pretty much the whole of the UK Education (and some public sector) community.
Each organisation has a limited number of video system and as such their internal infrastructure does not really require anything such as the RMX or DMA solutions. All of these organisation are more concerned with inter-organisation videoconferencing, rather than internal videoconferencing and as such the system works reasonably well.
However, many organisations are now turning to Lync to enable their internal users desktop conferencing facilities. Obviously, with the HDX and Group Series systems, there is the option of a Lync Interoperability and multipoint licence (TIP is enablesd as well, although this is something we would not reequire), and as such we have acquired a loan unit (Group 700 running 4.2) to test its capabilities. The ability to call a VC device directly from Lync would be quite appealing, however, after setting up the unit and connecting it with our Lync 2013 deployment, there are a number of questions that spring to mind.
If anyone has thoughts or comments on this, I would appreciate it.
Hi Sumurai Jack,
Unfortunately, all the responses I have received so far are shown above (i.e., none!).
I saw you other post and I wish you better luck than I have had.
Regarding your 1st question
Even when Group Series is registered with Lync server, you would not be able to share content between Lync clients and the Group Series (whether point to point or via Lync AVMCU) because Group Series do not support RDP protocol.
To enable content sharing, you would need backend infrastructure (DMA7000, RMX bridge and Content Sharing Suite). In this scenario, there is no need for Group Series to register with Lync server anymore. It can register to the DMA7000 (H.323 or SIP).
Thanks for you response and indeed I eluded to this in the question. The problem we have from our point of view (and that of our customers) is that this does NOT make the Group Series "Interoperable" with Lync, at best is makes them compatible. Given what the Group Series is and the CPU resources available, you would have thought on on the fly trsancodeing or support for RDP would have been de rigours, and would then approach the statements made by your
welcome back to the Polycom Community.
Polycom has always been on the front of interoperability with other third party vendors and currently offers solutions to use LYNC with an existing Polycom infrastructure.
As already explained in my older reply to yourselves some features may be planned for future releases but due NDA cannot be discussed within the community.
I would suggest to work with your Polycom reseller and via them get in touch with a Polycom sales engineer so they can share the roadmap with yourself.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services
Indeed, we have trying to arrange a visit down to see Polycom UK HQ, but it hasn't come though as yet. Will keep trying. We used to visit all the major manufactures every year, but we havn't done this for a while.