- #MAC SKYPE FOR BUSINESS CONTACTS MENU GRAYED OUT REGISTRATION#
- #MAC SKYPE FOR BUSINESS CONTACTS MENU GRAYED OUT WINDOWS#
#MAC SKYPE FOR BUSINESS CONTACTS MENU GRAYED OUT REGISTRATION#
One of the unique aspects of the Group Series platform (which was carried over from the HDX) is that the configuration for SIP registration and calendaring registration is separate. For continuity all configuration steps outlined in this article use the web interface. Most configuration steps shown throughout this article can be accessed using the on-screen menu system and supplied remote control, or by using the Administration menu on a RealPresence Touch (RPT) control panel. The Group Series firmware contains an embedded web server which can be used to remotely administer the device, also similar to VVX and Trio phones. So, while both formats may work in a given environment the guidance seen throughout this (and all recent articles on this blog) focuses on using the UPN format throughout all examples. That being said it has long been a recommended practice to use the UPN format when possible as moving away from older methods help prepare for scenarios in which these methods no longer are applicable, as in dealing with a standard Office 365 tenancy. When dealing with on-premises Lync and Skype for Business deployments typically both the legacy NetBIOS format as well as the newer UPN format can be used. This is the single most common problem seen in the field with failures to successfully register anything to Lync or Skype for Business. But knowing and not just guessing the proper format to enter a set of user credentials is paramount. As more organizations move to Office 365 then the opportunities are reduced for scenarios where SMTP and SIP addresses do not match a User Principal Name (UPN).
#MAC SKYPE FOR BUSINESS CONTACTS MENU GRAYED OUT WINDOWS#
As explained in this previous article Windows user credentials can be used in different formats which do not always use the same names, depending on how the account was originally setup. One of the most important concepts to understand when dealing with solutions like the Group Series or VVX phones which support multiple different platforms is that entering information as basic as user credentials may not always be entirely straightforward. But when coming through an interoperability solution the VTC is only able to call into Skype Meetings, there is no presence or peer calling support as the VTCs are not able to actually register to the Skype for Business environment. When the Group Series system is leveraging the native support model it will register as a Skype for Business account and do most of the things one would expect a registered client to do: support presence states, peer calling, join Skype Meetings directly to the AVMCU, etc. Also keep an eye out for an upcoming article on the new interoperability service provided in Skype for Business Online known as RealConnect for Office 365, or more generically as Cloud Video Interop (CVI). Either natively, as this article discusses, or via an interoperability solution like RealConnect which was outlined in this article from a few years ago. It is important to understand that for Skype for Business Server environments the Group Series can be involved in one of two ways. The newer Group Series platform was supported originally on Lync Server 2010 and now with Lync Server 2013 and Skype for Business Server 2015. Specifically the older HDX models were originally supported with OCS 2007 all the way up to Lync Server 2013. While this is true of most legacy systems from manufacturers like Cisco/Tandberg, LifeSize, and even older Polycom units to name the most common of them, the more recent generations of Polycom VTCs also have supported direct, native registration to Microsoft’s SIP-based communications platforms like Office Communications Server, Lync Server, and most recently Skype for Business Server. Whatever they are called though the general idea is that the systems only work within other standards-based SIP and H.323 video conferencing platforms. Another common nickname is “codec” in reference to one of the unit’s primary functions as a media en coder/ decoder. These devices are commonly referred to by a host of various names, like “Standards-Based Video Systems” or “Endpoints”, or more simply a VTC ( Video Tele Confering systems). Backgroundįor anyone familiar with these devices or the previous generation HDX platform then much of the configuration outlined in this article may look familiar.
When support for direct registration to Skype for Business Online accounts in Office 365 is achieved then look for a newer article covering that simple configuration. Note that this does not yet include Skype for Business Online which is a separate qualification process that is nearing completion.
Earlier this year the Polycom RealPresence Group Series video conferencing platform received official qualification for use with on-premises Lync Server 2013 and Skype for Business Server 2015 deployments.
0 kommentar(er)
