Deploying Skype for Business Online phones. 3/18/2019.
Note: The Skype for Business phone should be used with Yealink original power adapter. Select Auto or Manual from the pull-down list of BToE Pairing Mode.
8 minutes to read. Contributors. Applies to: Skype for Business In this article This is deployment guide will help you deploy Skype for Business Online IP phones. In all types of businesses, having a phone number allows users to make and get voice calls, and it is an important requirement to do business. Users who have phone numbers will be able to make voice calls across all Skype for Business devices including IP phones, PCs, and mobile devices. You can learn more about Skype for Business IP phones by reading.
Deployment steps for IP phones Step 1 - Download the manufacturer's administrator guides and phone manuals Before you get started, it's a good idea to download the phone manufacturer's administration guides and phone user manuals. For Polycom phones, see the. For Yealink phones, see.
For AudioCodes phones, see the. Step 2 - Make sure you're purchasing or migrating a Skype for Business Supported IP phone and firmware A Skype for Business Online supported phone and firmware is compatible for Skype for Business Server as well, but the opposite isn't always true. To make sure you are buying or provisioning a supported phone and firmware, see. Step 3 - Checking that the right firmware is installed and update the firmware if required Check the firmware version on your phones. For:. Polycom VVX phones, go to Settings Status Platform Application Main.
Yealink phones, go to Status on the main phone screen. AudioCodes phones, go to Menu Device Status Firmware version from the start screen. Note Polycom firmware prior to 5.5.1.X had a manufacturer-specific device-lock mechanism that is replaced with a Skype for Business implementation 'Phone-Lock.' Upgrading a phone from 5.4.X.X that was secured with 'Device-Lock' to 5.5.1.X with 'Phone-Lock' won't inherit the PIN code from 'Device-Lock,' which can leave the phone unsecured. Users who have activated 'Device-Lock' need to enable the following Polycom Device Profile parameter to give users control of time of upgrade (lync.deviceUpdate.popUpSK.enabled=1). Firmware updates are managed by the Skype for Business Service. Every Skype for Business certified phone's firmware is uploaded to the Skype for Business Update server, and device update is enabled on all phones by default.
Depending on the inactivity time on the phone and polling intervals, phones will automatically download and install the latest certified builds. You can disable the device update settings by using the cmdlet and setting the EnableDeviceUpdate parameter to false. When a new firmware is available and ready for download and install, the phone will notify the user. Polycom phones will notify the user and provide them with an option to Update or Postpone. For a Polycom phone, you can update the firmware on the phone by selecting SwUpdate. You can also choose to manage firmware updates using a partner provisioning system.
For partner provisioning system management including advanced phone customization, refer to manufacturer administration guides. Caution Make sure to have a single device update authority (In-band device update or a third-party provisioning server) to avoid update loops. Step 5 - Configuration and infrastructure phone settings You can set up the most commonly used phone options and policies using Skype for Business In-band management Windows PowerShell cmdlets. See for details of those parameters and settings. For network infrastructure planning, see. Step 6 - Preparing for users to sign in To enable users to successfully sign in to a Skype for Business Online phone and make calls, you need to make sure users are assigned the correct licenses. At a minimum, you will need to assign a Phone System license and a Calling Plan.
For additional information, you can see. You can find out more about Calling Plans by reading. Sign-in options that are available for Online users are:. Users with Polycom VVX 5XX/6XX phones will see:. Users with Yealink T48G/T46G phones will see: For details on sign-in options supported by the manufacturer, see. User ID Using the phone's keypad or on-screen keyboard (if available), users can use their organization's user name and password to sign in to the phone. For example, they should use the UPN format like [email protected] for their user name.
Note Users are required to use their organization's user name and password to sign in to the phone. For example, they should use the UPN format like [email protected] for their user name.
Using a Web Sign-in: This is a new way for Online users to authenticate using a standard web browser. Users will be provided with a set of instructions to follow when they use a browser to sign in. Users with Polycom VVX 5XX/6XX phones will see:.
Users with Yealink T48G/T46G phones will see: The code that is generated will expire in 15 minutes. When it expires, the user will have to click Retry or OK to generate a new code, depending on the phone. Users with Polycom VVX 5XX/6XX phones will see:.
Users with Yealink T48G/T46G phones will see: Using a browser, navigate to the address displayed on the phone and enter your Skype for Business username. Enter the code shown on the phone.
Verify that the site shows 'Phone Manufacturer name Skype for Business Certified Phone,' and click Continue. Click the user's credentials or click Use another account: When the following page is displayed, it is safe to close the browser. Note LPE phones for Skype for Business Online support sign-in through USB tethering only. Supported deployments The table below shows the supported authentication types for the currently supported deployment models including Exchange Integration, Modern authentication with Multi-factor Authentication (MFA), and Skype for Business Online and on-premises.
In May 2013 (Snom, Polycom, Audiocodes) started mentioning future “enhanced better together support over ethernet” functionality. At the Microsoft World Wide Partner 2013 both and demonstrated this functionality. Interestingly snom is calling this functionality “Enhanced Better Together” (or EBT) and Polycom is calling it “Better Together over Ethernet (or BToE). The remaining question I’m hearing from Lync consultants, admins and partners: How will the Lync Client to IP pairing process work? This is a very valid question as the usability at scale and ongoing manageability of this feature will be key to its successful implementation.
(There are Lync Call Via IP Phone apps already. See and ) UPDATE 9/6/2013: Polycom Has Just Released a Detailed Step by Step How Their BToE Will Work. How Polycom better together pairing process works What Piece Technically Connects Lync Client and Lync Qualified IP Phones?
During about snom’s new Enhanced Better Together feature when I asked about the pairing process to share. To my question “Is there anything a user needs to do to pair?” Paul noted that. On Lync 2010 + snom Lync 2013 + polycom (photo via ) After seeing the Lync audio devices screenshots (above) from the snom & polycom Enhanced Better Together over Ethernet demo’s at WPC13, I highly suspected a USB to Ethernet driver was the piece bridging Lync and the IP phones. NOTE: No input from snom on this functionality at this time.
Will My Lync SDK Customizations Work With EBToE? I haven’t tested this new functionality yet, but from my own usage of the Lync SDK (Lync client sdk) and the fact that EBToE is using a device driver (just like all previous Lync audio devices) I think we can safely extrapolate that your Lync SDK apps will work with enhanced better together over Ethernet. There could be cases where a Lync Qualified device does not support (or does not yet support) some feature that the Lync SDK supports. This is already the case with the Lync Phone Edition “Aries” device: It does not support (the LPE “Areies” hardware' does not support) the ability to and so if you request a via the Lync SDK it will fallback to doing a normal transfer. I would expect we could expect possible similar “limitations” with EBToE devices. Hi Matt, I have tested the BToE functionality as well and was very happy with it.until I added video to the call.
Once you do this the audio call that is set up on the phone is stopped and a new audio+video call is setup to the PC. This all works perfectly, but as opposed to Lync Phone Edition (LPE) with BT, the audio is not transfered back to the phone. Instead a (as in not or not easily controllable) microphone and speaker attached to the PC are used. We use video a lot so it seems we have to stick to LPE or CX300 for the time being. Landis has various industry certifications: Microsoft Certified Systems Engineer, Microsoft Certified Database Administrator, Microsoft Office Certified Expert, Microsoft Certified Dynamics, Network+ and A+.
In 1995 Matt started Landis Computer which has been providing IT services to small businesses for 14 years and is now a 11 person Microsoft Gold Certified Partner. Matt has over 14 years of field experience implementing Windows Server, Microsoft & Dynamics ERP solutions in small business environments.
Matt is very active in the Windows based IP PBX community: He was a 3CX Valued Professional from 2008-2010 and has co-authored a book on Windows communication software '3CX IP PBX Tutorial'. He is pbxnsip Certified, he has contributed thousands of posts to the 3CX community forum and he writes the monthly Windows PBX Report e-newsletter for VARS and administrators. His company, Landis Computer, was the first company in the USA to be designated a 3CX Premium Partner. When not working and when a chance affords Matt likes to travel internationally with his wife Rosalyn and is very involved in his church.