Poly Trio with Microsoft Teams

August 6, 2019 by · 111 Comments 

There are four primary configuration scenarios available for the Poly Trio which support Microsoft Teams and the ideal option for an organization can depend on several factors.  The most important distinction is whether the Trio is deployed standalone as simply a phone or if it is also paired with Visual + or Visual Pro componentry for enabling video conferencing capabilities.

These four scenarios can generally be categorized as:

  1. Native Mode
  2. Gateway Mode
  3. Hybrid Mode
  4. USB Mode

The first two scenarios are Audio Only where the Trio is deployed as a standalone phone.  The second two scenarios are applicable to Video-Enabled deployments of the Trio.

Note that in all but the USB scenario the Trio itself is the registered endpoint and the configuration is performed within the Unified Communications Software (UCS) firmware which runs on the Trio platform.  The Trio performs all call control and can be paired to a variety of supported audio and video components, leveraging one or more registration and meeting platforms.  Alternatively the USB mode simply turns the Trio into a USB audio device which is then connected to and controlled by a separate video-enabled endpoint like a Microsoft Teams Room.

The configuration steps in each of the following sections assumes that the Trio is in a factory-reset configuration state before starting, so some of these steps may not need to be performed on a currently deployed device.

Native Mode (Audio Only)

The first and newest option available is to simply place the Trio into the Microsoft Teams base profile which will automatically reconfigure the phone to launch and utilize the embedded Microsoft Team Android application designed for Teams-qualified IP phones.  This application only provides for audio capabilities with the Trio, so it should only be used with a stand-alone Trio which is used for audio conferencing.  (If any video devices are integrated with the Trio then any connected cameras and display monitors will not function in this mode.)

Configuration

Before attempting to use this option the Trio must first be upgraded to at least the 5.9.0 Rev AA firmware release which first introduced this supported capability.

  • Open the Settings menu on the Trio and navigate to Advanced > Administration Settings > Network Configuration > Base Profile and then select the Microsoft Teams option.  (The default password is ‘456’.)  Tap the back arrow and then select Save Config which will immediately reboot the phone.

image          image

  • After the phone reboots it will display the Microsoft Teams Sign In screen.

image

A Company Portal screen may be seen while the client software attempts to connect to the Microsoft Teams services.  When the Microsoft Sign In screen appears it will provide two different user authentication methods: one option to directly enter the credentials into the phone using the soft keyboard and another to utilize the Web Sign In process to enter the credentials in a web page on another computer.

image

If it is desired to enter the account credentials directly on the phone then follow this step, otherwise skip to the next step to alternatively use a web browser on another device to enter the account credentials for the phone.

  • Tap on the username field to bring up the on-screen keyboard and then type in the username for the desired Teams user account (e.g. trio@msteams.net) and select Next.

  • Enter the password for the provided account name and then select Sign In.

image          image

Alternatively this step can be used to sign into the phone by using a web browser on a computer or other mobile device.

  • Tap the “Sign in from another device” option

image     image

  • From a web browser on another device or computer go to https://microsoft.com/devicelogin and then enter the alphanumeric code  currently displayed on the Trio (e.g. e5s7p7alx) in the Enter Code field and then click Next.  (As demonstrated in this example the code is not case-sensitive.)

  • If the Pick an account window appears and the desired account appears in the list then select that account.  If not, then select the Use another account option.

image     image

  • If prompted to sign in then enter the username for the desired Teams user account (e.g. trio@msteams.net) and select Next.  Then enter the password and select Sign In.

image     image

Regardless of which sign-in approach was used the remainder of the process is the same, as are the resulting capabilities and experience.  The phone may briefly display the Company Portal page as the Microsoft 365 tenant is located and then the Teams client will appear once completed.

image          image

  • If prompted to select a login account type select Shared.  (This is the only mode that will be supported on the Trio, so while Personal can be selected it is not recommended, nor supported.)

image

Behavior

The Shared option is meant for common area use-cases like conference rooms where only scheduled meetings on the room’s calendar are displayed, along with the dial pad button used to place an outgoing PSTN call.  The magnifying glass icon in the upper right corner can also be used to search for other Teams users or devices to place outbound peer calls to.

image

In the example shown above there are both Teams and Skype for Business scheduled meetings on the Trio’s calendar.  Note that the action button on Teams meetings says ‘Join’ while the button on a Skype meeting (denoted by the Skype for Business logo) says ‘Dial’.  this is a very important distinction to understand as the Teams client does not have any native support for Skype for Business; it does not speak MS-SIP and cannot talk to a Skype for Business platform.  The only way this client can join a Skype meeting is if the meeting organizer is configured for Dial-In Conferencing or is licensed for Audio Conferencing and the meeting invitation includes the necessary PSTN dial-in number(s).  Also, the Teams user registered to the Trio must be enabled with Phone Calling using either Direct Routing or with a Microsoft Phone Calling Plan assigned to it.  In short, the Trio must be able place an outbound call to the PSTN via Microsoft Teams in order to connect to the Skype meeting via basic audio conferencing.

The Teams presence state for the account can manually be set directly on the phone by tapping the ‘hamburger’ menu in the upper-left corner of the client and selecting the desired presence state.

image 

For comparison the Personal option can be selected during sign in if prompted, but this mode is more resource-intensive and as previous stated is not supported on the current Trio models. This mode is intended for personal handsets like the upcoming Poly CCX devices and will not only show scheduled Meetings, but also provide additional capabilities in the client applicable to individual users like the history of Calls and Voicemail along with Search and Call Park retrieval options.  From the Calls screen the Make a Call button can be used to either search for other Teams users or bring up a dial pad to place a PSTN call.  The New event button on the Meetings screen allows the user to create a new Teams meeting directly from the phone and then invite other participants.

image     image     image

Gateway Mode (Audio Only)

This configuration uses a single registration into Skype for Business Online which inherently provides a limited set of core functionality into the Microsoft Teams environment.  This is provided by way of a SIP to Teams audio gateway which Microsoft has deployed and manages in their cloud.  The gateway is not something that devices point to directly as it is more of a set of backend connections between the Skype for Business Online and Microsoft Teams environments, allowing for mainly peer calling and meeting-join capabilities for 3PIP-qualified IP phones like the Polycom VVX, Trio, or other third-party qualified phones.  Thus, the simple act of registering the phone to Skype for Business Online provides some inherent connectivity into Microsoft Teams.

Also of importance is where PSTN connectivity comes from.  If the environment is currently using Enterprise Voice in Skype for Business then all PBX functionality and PSTN connectivity is retained via the registration to Skype for Business.  If (and when) that Enterprise Voice functionality is migrated to Teams, by way of establishing a Direct Route to Teams or utilizing Microsoft Phone Calling Plans, then the Trio (as any 3PIP-qualified phone) will continue to operate the same via the gateway services.  Thus, when moving all users in an environment to "Teams Only" mode and also migrating PSTN connectivity directly into Teams there is no impact to these phones which were already functioning; they simply stay in the same configuration and the gateway masks all of those changes.

Be aware that while this functionality does rely on Skype for Business Online it will not initially be impacted by the planned retirement of Skype for Business Online on July 31, 2021 as announced by Microsoft.  Microsoft intends to support 3PIP-qualified IP phones via the gateway services for an additional two years, through July 31, 2023 as stated in this FAQ.

Configuration

Before registering the phone the desired user account should be set to Teams Only mode for best functionality.  While this is not a requirement to leverage the gateway, but is recommended for proper functionality.  If the account is in a different Teams Upgrade mode, like Islands for example, then peer calling behavior may not function correctly.

  • Open the Microsoft Teams admin center (https://admin.teams.microsoft.com) and in the Users section select the desired account.

  • Click Edit on the Teams Upgrade section and change Coexistence Mode to Teams only and click Save.  (Ignore the setting to ‘Notify the Skype for Business user’ as this only applies to the Microsoft Skype for Business clients and is not relevant for using the account only with a 3PIP-qualified phone.)

image

  • On the Trio access the Settings menu and navigate to Advanced > Administration Settings > Network Configuration > Base Profile and then select the Skype for Business option.  (The default password is ‘456’.)  Tap the back arrow and then select Save Config which will immediately reboot the phone.

image          image

    • After the phone reboots tap the Sign In button and select the preferred option for registering to Skype for Business Online using the desired user account.

    image          image

    Behavior

    When the Trio is registered to an account which is homed in Skype for Business Online it will retain all currently supported Skype capabilities as it is still in the Skype Base Profile.  When a specific event occurs (like placing a call from the phone to another user in Teams Only mode) then Skype for Business Online knows to route that call through the gateway services into the Teams environment.  Understand that if a phone is registered with an account homed on a Skype for Business Server which is not part of a Hybrid deployment then this will not function as the gateway service is only accessible via Skype for Business Online connectivity.

    As pointed out above, this is an Audio Only experience with Microsoft Teams as the gateway only supports audio.  Thus, this configuration is also intended specifically for audio-only deployments and should be avoided with video-enabled configurations.  (There is a known issue where video sessions can erroneously be established through this gateway when joining a Teams meeting.  This may not be resolved by Microsoft as the gateway is essentially in a maintenance mode and will likely not have any future feature development.  Microsoft’s focus is the wholesale replacement of devices to new products which will run the native Microsoft Teams client.)

    To provide some insight into how the gateway works simply save a Teams meeting invitation in Outlook as an .html file then open it in any text editor or viewer.  Search for the text "focus:id" and the following OnlineMeetingConfLink section should be seen.

    image

    Note that this looks exactly like a Lync or Skype for Business conference URI, except for the additional teams:2:0!19: string.  The Trio does not look at the actual Teams meeting link embedded in the Join Microsoft Teams Meeting link at the top of the invitation, but will identify these invitations as a ‘Skype Meeting’ by recognizing the conference URI embedded in the message as shown above.

    A native Teams client would join this meeting using the native Teams meeting URL.

    https://teams.microsoft.com/l/meetup-join/19%3ameeting_NQG2ODNzMTItZTU5Yy95ZTFhLWFmYjgtYjk4MjQ1N2Q0ZmY4%40thread.v2/0?context=%7b%22Tid%22%3a%22bc7c5f16-c55e-417d-aac0-ff6bbfc27f76%22%2c%22Oid%22%3a%22aff3cdcc-4551-4de6-8bec-e7f9e07edf61%22%7d

    Yet the phone will leverage the ‘legacy’ Skype conference URI in the invitation which looks much different.

    conf:sip:jeff@msteams.net;gruu;opaque=app:conf:focus:id:teams:2:0!19: meeting_NQG2ODNzMTItZTU5Yy95ZTFhLWFmYjgtYjk4MjQ1N2Q0ZmY4-thread.v2! aff3cdcc45514de68bece7f9e07edf61!bc7c5f16c55e417daac0ff6bbfc27f76

    Note that both formats utilize the same unique identifier, indicating that this is the same meeting.  But since the phone registered to Skype for Business cannot leverage the first URL then continues to see this invitation as a Skype meeting and then attempts to connect to the conference URI above.  As far as the phone is concerned though it thinks it is talking to a Skype for Business MCU, but in reality it has been pointed to the gateway (focus:id:teams:2:0!19:) which then handles the rest of the connection to the actual Teams MCU and locates the correct meeting via the provided meeting ID (NQG2ODNz…).

    Hybrid Mode

    The mode is the only option which is supported by Microsoft for interoperability when the Trio is deployed as video-enabled when paired with a Poly Visual Plus (Visual+) or Visual Pro solution.  This is because the Trio will leverage the supported Cloud Video Interop (CVI) approach by joining Microsoft Teams meetings using the Poly RealConnect Service.

    The Hybrid name comes form the fact that the Trio can support multiple concurrent registrations to different SIP-based platforms and yet still join native Teams meetings with video and desktop sharing capabilities.  One basic configuration option is to have a single line registered natively to Skype for Business to retain any existing functionality as well as utilize Enterprise Voice in Skype for PSTN connectivity, but then leverage a second (unregistered) line to join Teams meetings by placing standards-based SIP calls directly into the Azure-based interop service.  Another common option comes into play when another common IP-PBX platform (e.g. Cisco or Avaya) is used in the environment and PSTN connectivity is not provided by Skype or Teams.  This configuration is a true ‘hybrid registration’ option as the Trio will sustain multiple concurrent SIP registrations: one to the PBX platform for voice calling and a second to Skype for Business.  The third line can be used for unregistered calls in to the CVI service or even be actively registered to any standards-based video proxy (e.g. Poly DMA/RPAD, Cisco VCS/VCS-E, etc.) for eventual routing into the video interop service (or alternatively the Poly Clariti-based configuration of RealConnect for Microsoft Teams interop.

    In short, the Hybrid approach is the most flexible as it can be used to connect into any number of IP-based voice platforms and/or meeting solutions.  It is not uncommon to see a Trio configured to support joining meetings scheduled on several different meeting services like Skype for Business, Microsoft Teams, Cisco WebEx, Zoom, etc. all in the same room.

    Configuration

    The example configuration in this article will address a single use-case, showing how register the Trio to Skype for Business and also configure it so that RealConnect will be used to join Teams meetings.  This approach still retains existing Skype for Business functionality, only leveraging the interop service for joining Teams meetings

    Before configuring the Trio itself a set of UCS parameters will need to be prepared to import into the phone.  This is accomplished by creating a custom configuration text file and saving it with a .cfg file extension.  There are several applicable parameters, most of which are required to successfully  place calls into the RealConnect Service from the Trio.  Only a few of the parameters need to be customized, while some of the parameters can be omitted depending on the desired capabilities.

    At minimum the following parameters are required to allow the Trio to place a SIP call into RealConnect by using an additional, unregistered line.  As mentioned above this specific example will configure the Trio to use Line 2 to place these calls, but for a Trio using a different configuration with potentially more than 2 registrations then simply alter the following example to use an available line number.

    Attribute Value
    call.autoOffHook.2.contact 680450644@t.plcm.vc
    call.autoOffHook.2.enabled 1
    call.teluri.showPrompt 0
    dialplan.2.applyToDirectoryDial 1
    dialplan.2.digitmap ^.+@t\.plcm\.vc$
    dialplan.2.digitmap.mode regex
    dialplan.2.digitmap.timeOut 4
    dialplan.digitmap.lineSwitching.enable 1
    exchange.meeting.realConnectProcessing.outboundRegistration 2
    exchange.meeting.realConnectProcessing.skype.enabled 0
    exchange.meeting.realConnectProcessing.teams.enabled 1
    reg.2.address trio
    reg.2.keepalive.sessionTimers 1
    reg.2.label Teams Meeting
    reg.2.server.1.address t.plcm.vc
    reg.2.server.1.register 0
    reg.2.server.1.transport TCPpreferred
    reg.2.srtp.offer 1
    reg.limit 2

    The three highlighted parameter values above must be customized as explained below.

    1. Most important is the specific Tenant Key (e.g 680450644) assigned to the Office 365 tenant where the RealConnect Service is used, as this controls which tenant entry queue is called when simply tapping the new line key which will appear on the phone.
    2. Also enter the preferred name used to identify the phone in SIP calls (e.g. trio); this name can be pretty much anything unique to the specific device except for the SIP URI of the account already registered to Skype for Business as that would cause a conflict.
    3. Finally select the desired label name which will appear under the new Line key button on the Trio’s home screen (e.g. Teams Meeting).
    • The following text can be copied into a new file and then saved as with a .cfg file extension for importing into the phone in a later step.

    <?xml version="1.0" encoding="utf-8" standalone="yes"?>
    < !–Description: Template for configuring a Trio to connect and dial into Teams RealConnect via an unregistered Line 2.  The Lobby will be autodialed when Line Key is selected.–>
    < PHONE_CONFIG>
       <ALL reg.limit="2" dialplan.digitmap.lineSwitching.enable="1" call.autoOffHook.2.contact="680450644@t.plcm.vc" call.autoOffHook.2.enabled="1" dialplan.2.applyToDirectoryDial="1" dialplan.2.digitmap="^.+@t\.plcm\.vc$" dialplan.2.digitmap.timeOut="4" dialplan.2.digitmap.mode="regex" reg.2.address="trio" reg.2.keepalive.sessionTimers="1" reg.2.label="Teams Meeting" reg.2.server.1.address="t.plcm.vc" reg.2.server.1.register="0" reg.2.server.1.transport="TCPpreferred" reg.2.srtp.offer="1" exchange.meeting.realConnectProcessing.teams.enabled="1" exchange.meeting.realConnectProcessing.outboundRegistration="2" call.teluri.showPrompt="0" />
    < /PHONE_CONFIG>

    (Note that is configuration is identical to the "Trio-Teams-RealConnect-Line2-unregistered-Template" provided in the Polycom Device Management Service (PDMS).)

    As mentioned above this specific example will configure the Trio to use Line 2 to call the RealConnect Service to join a Teams meeting.  If it is preferred to move this functionality to a different line number for phones with more than a single registration then simply update each call.autoOffHook, dialplan, and reg parameter to change the .2. to the desired line number (e.g. 3).  Also change the the exchange.meeting.realConnectProcessing.outboundRegistration parameter to match the same line number (e.g. 3) and finally set reg.limit parameter value from 2 to match the highest line number in the phone’s specific configuration.

    • On the Trio access the Settings menu and navigate to Advanced > Administration Settings > Network Configuration > Base Profile and then select the Skype for Business option.  Tap the back arrow and then select Save Config which will immediately reboot the phone.

    image          image

    • After the phone reboots tap the Sign In button and select the preferred option for registering to Skype for Business using the desired user account.

    image          image

    The next step is to apply the configuration file to the Trio which can be accomplished in one of several ways.  If using a provisioning server solution with the Trio then that is the preferred approach, but for the purposes of this article the file will be manually imported into a single phone using the local web management administration interface.  The web management interface is not available by default when the Trio is set to the Skype for Business profile, so it may need to manually be enabled.  If it is already enabled on the Trio then skip this step.

    • On the Trio access the Settings menu and navigate to Advanced > Administration Settings > Web Server Configuration, enable Web Server, and then select the desired Web Config Mode (e.g. HTTP/HTTPS).  Tap the back arrow and then select Save Config which will immediately reboot the phone.

    image

    • After the phone has rebooted tap the hamburger menu in the top left corner and look for the device’s IP address as displayed in the menu (e.g. 192.168.1.167).

    image

    • Open a web browser on a workstation and connect to the IP address using either HTTP or HTTPS, based on the previously-configured option(s) (e.g. https://192.168.1.167) and then sign in using the Admin account.  (The default password is ‘456’.)

    image

    • Go to the Utilities > Import & Export Configuration menu and then click Choose File under the Import Configuration section.

    • Select the previously created configuration file (e.g. Trio_RealConnect.cfg) and then click Import which should immediately trigger the Trio to reboot.

    image

    Behavior

      After the phone reboots the additional line button (e.g. “Teams Meeting”) should appear on the home screen indicating that the new parameters were successfully imported.  The new "Teams Meeting" line key can be used to simple call directly into the RealConnect Service’s entry queue which will prompt for the specific meeting’s video conferencing ID.  The Meetings button on the home screen will provide a Join button which can be used to connect directly into a scheduled Teams meeting.

    image     image

    USB Mode

    This mode simply turns the Trio into a USB-only audio device for when it will be physically connected to any supported Microsoft system like the Microsoft Teams Room or a Surface Hub.  The Trio no longer performs any registration and is turned into an accessory to perform as a microphone and speaker.

    Configuration

    • On the Trio access the Settings menu and navigate to Advanced > Administration Settings > Network Configuration > Base Profile and then select the Microsoft USB Optimized option.  Tap the back arrow and then select Save Config which will immediately reboot the phone.

    image          image

    Behavior

    Once the phone reboots a very simple interface will appear.  When the connected room system is not in an active call the display is relegated to only showing the Date and Time.  When the connected room system is in a call then the Trio will display a call timer along with Mute and End Call buttons.

    image          image

    About Jeff Schertz
    Site Administrator

    Comments

    111 Responses to “Poly Trio with Microsoft Teams”
    1. Jens Schneider says:

      Thank you, Jeff! Very valuable article. Easy to understand for every IT Manager / Admin.
      Jens

    2. John says:

      Hi Jeff, thanks for the great guide. Is there a way of retaining the Trio 8800 generic home screen but also unlock Teams functionality? It seems like once you configure the device for Teams it loses the dialer and other “generic” options such as Bluetooth etc and have not found a way to get around this.

      • Jeff Schertz says:

        No, once the device is in Teams mode it’s only able to do what Microsoft provides in their application. The rest of the Trio’s inherent capabilities are essentially blocked. The Dial button is available in the Teams app only if the registered account has a Phone System license and is configured accordingly for Enterprise Voice in Teams.

        • Jamie says:

          Hi Jeff. This is immensely frustrating to discover as we bought this device for Teams and Bluetooth calls from mobiles. The Teams page on Poly’s website actually specifically spells out in the BYOD section that this is possible:

          “Polycom Trio expands your collaboration choices. Need to make the occasional call from a smartphone or another cloud service? Your meeting room visitors can easily pair their mobile devices or laptops to Trio using USB or Bluetooth.”

          Do you suggest I take this up with Poly or MS? Or both?

          • Jeff Schertz says:

            Jamie, I would suggest talking to both. Technically the Teams application can not leverage the Bluetooth chipset in that way and the running application prevents the Trio from using BT as well. Can you provide a link to where you are seeing that information? I’ll see if I can get it fixed.

    3. Dan Ferguson says:

      Another great article Jeff! Always a great resource to turn to for any new learning!

    4. Milos says:

      Hi Jeff,

      As always very informative article. One question tho…

      When in Skype for Business mode and trying out for Hybrid registration is it possible to not have any registration on the SfB line and still utilize the 2nd line for CVI dial-in as you described? Testing this and it seems the 2nd line to dial in to CVI is not showing unless there is at least one registered line (be that Line1 to SfB or in my case Line2 with CUCM – that would make CVI dial-in the 3rd line).

      It seems like the CVI dial in is just a local contact which does not show up if there is no registered lines?

    5. Jason says:

      Hi Jeff

      We have successfully setup a Trio in Native Mode running in Teams Mode.
      We can successfully join Teams meetings, and make outbound PSTN calls to mobile phones.

      We have an issue when trying to join a Skype meeting via PSTN dialin.
      The meeting invite includes the Dial-in conference number in E.164 format (e.g. +617 1122 3344)
      But when we try to join the Skype meeting, it strips out the “+” and tries to dial 61711223344 which fails since we don’t cater for this silly number format.
      (dialing +61711223344 manually works perfectly)

      Is this something you’ve seen, or will we have to add a transformation to the TenantDialPlan to add back the “+” ?

      Cheers
      Jason

    6. Elton says:

      Good Morming Jeff…
      My Trio not show video in call RC Teams, some settings ?
      Tks
      Elton

    7. Tyrone says:

      Hi Jeff

      Always love reading your articles on Polycom.

      Keep up the good work.

      Kind regards

    8. Joel Harris says:

      Great article Jeff.
      An issue we are seeing is that the Trio is being blocked by Intune as it is showing as an unknown Android device.
      Any ideas on this?

      • Jeff Schertz says:

        You likely have a customized Intune policy defined blocking older Android versions (I’ve seen this in a few enterprises). Microsoft is aware of this issue and have plans to allow Intune to differentiate between standard Android devices (e.g. personal phones) and Teams-certified Phones so prevent this issue. (The root of the current issues is that the few existing Teams phones today are running on older Android 4.x/5.x builds, while the new Teams phones coming out (like the Poly CCX) will be running on Android 9.x)

        • Kazzan says:

          Hi, does someone test the latest firmware 5.9.1 AC?

          We update couple of Trio to this build and Teams do not ask if the enroll in Shared or Personal mode and seems that Personal is the default one. Unfortunately, sign-out and sign-in does not trigger change of mode. Is there some other option to change it?

          And with the Intune policies, if you also enable Mobile Application Policies which aim to Skype for Business or Teams mobile application, you will get prompt that Trio is installed as rooted devices which lowering the nice numbers in Intune portal for protection policies applied. Even the exclude does not help right now.

    9. Martin C says:

      Hi Jeff,

      Allways great articles, thanks for this one too.

      In the Hybrid mode, you mention the Tenant key – Is this the tenant of the Azure for the particular company or a generic one for the Polycom RealConnect clound service in Polycom Azure cloud

      Martin Corydon

      • Jeff Schertz says:

        Throughout my articles I use “Tenant ID” to refer to the UUID provided by Microsoft to a specific tenant (also called the Azure Directory ID), and “Tenant Key” to refer to the globally unique prefix provided by a CVI partner (via Microsoft) which is used in the VTC dial string (e.g. “12345678@t.plcm.vc).

    10. Mary says:

      Hi Jeff,
      Our O365 tenant is configured with conditional access, which prevents Android from authenticating unless allowed based other criteria. This could be IP, member of a group, etc. Conditional access works with Intune. Is there something we need to do configure the Trio’s to work with Intune? Also, if we can, will they still work with RPRM too?

      Thanks for you help, you always have the answer 🙂

      • Jeff Schertz says:

        The phone’s’ will still communicate with RPRM as the base OS handles that, regardless of which base profile that UCS is set to. I haven’t played around with Intune management much yet as Microsoft is still rolling out and tweaking how this will work with the Teams IP phone client. I do know that they plan to address these issues at some point by allowing Intune to differentiate between a ‘regular’ Android device (e.g. personal phones) and qualified Teams phones.

    11. Amster says:

      Hey Jeff,

      Does the Trio register to the real-connect service and use that as a SIP registrar, such that you can also dial into zoom (meeting@zoomcrc.com) and/or BlueJeans (meet@bjn.vc) or does it require a seperate registration to a DMA or some sort of SIP gateway?

      With thanks.

      • Jeff Schertz says:

        The RealConnect Service does not currently support, not require registration. The Trio configuration provided in this article is simply an active, unregistered SIP line used to place outbound calls into the service. The same approach can be used for other platforms as well.

    12. Joe says:

      Hi Jeff,

      Another great article. Can I ask how do I go about changing the Teams meeting icon? I am not exactly sure how to do it.

      Thanks,

    13. Hi Jeff!

      Great article, especially from battling the Trio in the earlier releases. Few questions/issues if you could help.

      1.) My Teams user on the Trio always logs/signs out after a few days. This causes my ‘real’ users to log back in with the phone password. Have you ever experienced this?

      2.) Which license do you recommend assigning the user for an audio-only team setup (basic conference room)?

      Thanks!

      • Jeff Schertz says:

        I have noticed that if I leave a phone powered off for several days will the Teams client prompt me to provide the user’s password again. In my testing I’m constantly signing in and out of devices so haven’t let any sit powered on for several days with the same account yet though.

        Regarding licenses, Microsoft is still making changes to the phone client’s behavior and adding new policies/settings so it’s not yet clear what the correct guidance is. I’m using Common Area Phone and Meeting Room licenses on my devices (Trio, CCX phones), which are sufficient. Once these details are finalized by Microsoft I’ll post an article explaining everything. The general guidance I can give right now is that Enterprise licenses are overkill, but if one must be used an E1 is more than enough; don’t burn an E3/E5 which includes with Office software installation rights.

    14. Kenneth Barnett says:

      Jeff it looks like Poly and Microsoft have removed the VVX phones from the Cett list for Teams. Does that mean that the only options desk phones is going be yealink (i Chinese based company?

      • Jeff Schertz says:

        No. All previous 3PIP-qualified phones are still supported with Teams (via the gateway), but are not ‘Certified for Teams’. Only new devices which can run the Android IP phone client will be labeled as such. The new Poly CCX phones models are coming to address that.

    15. Joel says:

      Hi Jeff,

      Can you do an article for how to configure Group Series 500 with Realconnect Microsoft Teams, this article was very helpful for me getting our trio fleet ready. but I don’t have a clue where to start getting our group series ready for Realconnect teams.

      Thanks,

    16. Jeremy says:

      Hi Jeff. I have a Trio 8800 w/ Visual+ setup in Hybrid mode. Line 1 is registered to SfB. Line 2 is unregistered but setup to direct dial into the “Teams Meeting” using the RealConnect service which is working as expected.

      Is it possible for the “Join” button that is presented in the calendar to automatically connect to the Teams Meeting using Line 2 if a VTC Conference ID is detected in the invite? I don’t want users to have to go to another device to find the VTC Conference ID to type in each time.

      Thanks

      • Jeff Schertz says:

        That’s exactly how it should work, the Join button on the calendar entry will connect directly to the meeting. Check your configuration against the example in this article, as users should not need to be entering the conference ID manually.

        • David says:

          Hi Jeff,

          I have this same issue as Jeremy when using your above configuration on Trio 8800s. Users can see the join button but it joins via line 1 / SfB each time.

          I’ve been through the config a few times and cant see anything thats different from the above. Any suggestions?

          Running 5.9.2

          PS fantastic blog, thank youi!

          • Jeff Schertz says:

            My suggestion when this happens is to before a factory reset of the phone, remove any provisioning server information or move the phone to a network that does not have a provisioning server in the DHCP settings. Then add only the required parameters to accomplish the thing that is not working; often this resolves the issue. Then slowly start to add you own custom configuration back in until the problematic or conflicting setting is found.

    17. Mango says:

      Thanks for the article Jeff. The hybrid mode config worked like a charm and helped my company further develop a strategy for switching from SfB to Teams

    18. Vadim Dich says:

      Hi Jeff,

      Provided that there’s Trio registered to SfBO, and having the 2nd line configured for Teams Interop, how is it going to transform when SfBO gets closed? Should it be registered in Teams after that?

      We basically don’t need that 1st line for anything, but I’m not sure how Trio will behave if not registered at all. There should be at least Exchange connection to read the calendar.

    19. TJ Cornish says:

      It seems clear that BToe is not being carried forward. We are in the early stages of planning the Teams migration and it seems like BToE still works even in Teams Only mode. Is this because of the Skype client still being present? Knowing that this is unlikely to be supported for the long term, can we use this for a while until the Teams Phones and/or whatever solution MS may eventually come up with to hand off and/or join calls from multiple devices is more baked?

      Thanks

      • Jeff Schertz says:

        Correct, the BToE approach only functions with the Skype for Business client. If the user switches to using Teams then there will not be any Better Together integration with the VVX. Better Together functionality will come later in native Teams phones, but not for any previously Skype for Business qualified phones like the VVX.

        • TJ Cornish says:

          Thanks for your message – I’m glad to know that something is coming in the future.

          Just to reiterate my question, BToE is currently working in Teams with VVX phones because the Skype client is still present, even in Teams Only mode. I’m curious what future action will break this – will MS kill the Skype client at some point? When the last user is migrated to Teams Only? We’re looking for a stopgap until Teams native phones are available and I want to know the odds that my current situation of BToE on VVX with Teams via the Skype client will last until new functionality replaces it.

          Thanks

          • Jeff Schertz says:

            I don’t know exactly what will happen in July 2021, but I assume that Skype client’s will no longer be able to register to SfB Online, even though supported phones will still be able to do so for an additional 2 years. So, nothing should change for the next 2 years.

    20. Dustin Miller says:

      Jeff,

      If we have a Trio with SfB firmware that can be invited to a Teams meeting and participate in video (no RealConnect in play), that is expected but it is considered a bug?

      “There is a known issue where video sessions can erroneously be established through this gateway when joining a Teams meeting.”

      Thanks,

      Dustin

      • Jeff Schertz says:

        Correct. Microsoft is not blocking video in the SDP through the gateway so 3PIP phones which support video (like the Trio) will incorrectly be allowed to establish a video session. It’s unsupported and the video experience is quite bad. RealConnect should be used in this case, or the Trio can be configured to disable video on Teams meetings.

    21. Chris Tobler says:

      Great job! Everything worked as expected.

    22. Chris Tobler says:

      For some reason in my configuration I had to add this line:
      reg.3.server.1.port=”5060″

      Is this expected?

    23. TD says:

      Hi Jeff,

      I have a Trio 8800 w/ Visual+ setup in Hybrid mode where Line 1 is registered to SfB, Line 2 is SIP, and I’ve successfully set up Line 3 to dial to the RealConnect Service following your guide.

      The Teams meeting “Join” button does not show up on the calendar entry however. Skype meetings still show with a “Join” button. Is it normal for only one to work with One Touch Dial?

      Thanks

      • Jeff Schertz says:

        Is the Trio using the One Touch Dial Service (pointing to otd.plcm.vc)? Using the configuration in this article does not required OTD and the Trio should be pointing directly to the Exchange (unless you need to support non-English meeting Teams invites until that is fixed in a future Trio firmware. In that case, then OTD should be used as it can parse invites from all languages.)

    24. Carl Mudryk says:

      Very nice article! I’ve been trying to setup a Trio 8800 with a Visual+ to work with Teams with RealConnect. I’m trying to setup the Hybrid model, but I cannot get the phone to accept the .cfg file that I’ve created based on the one above. When I specify the file in the web browser for the phone, it just hangs on “Uploading File”. I tried using the USB, but it just says Update failed.

      Any idea what I could try next?

      • Jeff Schertz says:

        Try starting with a fresh .txt file with a single parameter in it, and then work your way up by adding more to it. Sometimes the file (or formatting) can contain something the phone does not like and will trigger odd errors during importing.

    25. BrettG says:

      Great article Jeff. We are currently setting up a number of Yealink Teams phones and finding that the Teams client on the phone does not present a dial pad. We’ve tried updating firmware, we’ve ensured that devices are set to Teams Only in the Office 365 portal without any success. The phones work successfully in the sense that they can receive calls (and if they have a manual keypad we can force the phone to dial out) but the software only interface of the CP960 phones don’t provide any sort of workaround. The phones are licensed with Common Area Phone licenses. Have you seen this issue or have any suggestions on why this happens?

      Thanks in advance.

      • Jeff Schertz says:

        You need to make sure that (a) the licensing includes Phone System (which Common Area Phone does), (b) that the accounts are Enterprise Voice-enabled, and (c) they are either assigned a Phone Calling plan or area assigned to a VouceRoutingPolicy (for Direct Routing) (Grant-CsOnlineVoiceRoutingPolicy).

    26. Andre says:

      Thanks for a great article!

      I have managed to get the configuration working with SfB on Line 1, SIP on Line 2 and Teams on Line 3 but am experiencing a slight issue when in a Teams meeting.

      We are using Trio 8800s with Visual+ devices. On sharing content from a Teams client in a Teams meeting the video / screen sharing “crashes” and the Trio room can no longer see anything. It just goes back to the normal home screen. Audio continues to work as does video sent from the room (USB camera in the Visual+).

      Anyone got any suggestions on if this is a bug / known issue? I haven’t been able to find anything about it and guessing my next step is to log it with Poly.

    27. Nadeem Shah says:

      Great article Jeff! I have a question regarding Trio, Teams and Zoom. can they exist in hybrid mode? Where it is registered to teams as you described in hybrid mode but has the option of dialing out to a zoom meeting? Or vice versa where it is registered as a zoom room and can dial into a teams meeting?

      • Jeff Schertz says:

        No, Hybrid ‘mode’ is actually just using the Skype Base Profile with multiple line registrations/configurations. When you put the Trio in either Zoom Room or Microsoft Teams mode then the Trio can only work with the selected platform. Meaning if the Trio is in Teams mode it cannot also SIP-register to anything else.

    28. Brandon H says:

      As always, more informative than any of the official documentation, thanks! One question, I noticed that OWA, Outlook Mobile, and Outlook for MAC aren’t including the Skype conference join URI when creating a Teams meeting invitation. Meaning that a Trio in gateway mode doesn’t get the join button for Teams meetings. Is there any workaround for this until MS fixes the issue? I know I can use the parseall option and the Trio will find the dial in number for the meeting and create a join button using that, though the user still has to enter the meeting ID manually. I’m hoping there’s something better.

    29. Pascal Saint-Germain says:

      Amazing Article
      Thx Jeff

    30. Vadim Dich says:

      Hi Jeff,

      I’m struggling with the dial plan for the 2nd line on my Trio 8800 while preparing it for hybrid mode, hopefully you can help me.

      1. No matter what I have specified as a digitmap, Trio takes only digital part of the URI, and tries to dial it like a phone number. Initially there was the digimap from your sample config, but then I tried a lot of different options, including exact match to the tenant’s URI – no luck at all. I saved a backup, and read through it, but didn’t find anything looking suspicious. Any ideas what could be wrong? Trio is updated to the latest software version.

      2. We have customized the domain name like you described in another article. Obviously digitmap should be changed accordingly, but what about reg.2.server.1.address? What’s the purpose of it, and should it be changed as well?

      • Jeff Schertz says:

        The “reg.2.server.1.address” contains the destination server hostname for calls placed on that line. you can leave the “t.plcm.vc” address unless you’ve customized your domain name for using RealConnect for Clariti and your hostname actually points to your own RPAD IP address. But if you’ve just changed the domain name for vanity-purposes then you can put in either as both should still resolve to the RealConnect Service in Azure. I would start by leaving it set as instructed.

    31. Stijn Wauters says:

      Hi Jeff,

      Very informative article.

      Maybe something you can add to this article, a new experimental feature that has been added wich could be a viable option.

      USB-Passtrough mode:
      https://support.polycom.com/content/dam/polycom-support/products/voice/realpresence-trio/release-notes/en/trio-release-notes-5-9-1-aa.pdf
      https://community.polycom.com/t5/VoIP-SIP-Phones/Software-Trio-UC-Software-5-9-1-10419-released/td-p/106334

      This way, the trio can be connected with visual+ and camera to a windows 10 system, and used in a teams call.

      • Jeff Schertz says:

        The USB pass-through mode requires that a computer be connected which is running the desired client software (like the Teams Windows or Mac client), so while this is a great feature it’s still a ‘Bring Your Own Device’ model. This article focuses on the Trio as an endpoint itself, not just a USB device.

    32. Rob says:

      Great article Jeff!
      I’ve deployed a Trio 8500 with latest firmware and found as you’ve mentioned above that you’re directed to Company Portal. Since we have proxy servers and only select Office 365 services allowed to bypass proxy through firewall, the Company Portal doesn’t display correctly. Loads for a while then get a blank screen.
      Any advice on which Office 365 endpoints Trio’s connect for this process to work so we can update our firewall accordingly? Company Portal in my experience is an Intune thing but our firewall logs show IP’s that aren’t in any Microsoft published lists.

    33. Ollie Wright says:

      Thanks Jeff!

      We have an issue where our 8800’s in Teams mode (on the latest firmware) requires re-authentication every so often. This isn’t a great experience for the end-users. Any ideas?

    34. JC says:

      Great article…do you know of a way to lock the Polycom Trio 8800 (on Teams Native Mode)?

      We worry about non-authorized folks to be able to walking into a private office or area where these are stage and make calls or listen into voicemails of active conference phones.

      • Jeff Schertz says:

        Device Lock is not appear to be available in the Trio when running Teams. Currently the Device Lock feature is not provided by the client when the signed-in user is assigned to a Meeting Room policy, and is the only user mode supported on the Trio. (It’s possible this could change though as the phone client is rapidly being updated by Microsoft.)

    35. Chris Tobler says:

      Hi Jeff, I have a trio configured in Hybrid Mode. Line 1 SFB Registration (account used is set to “Teams only”). Line 2 UCCM and Line3 Teams Meeting through Real connect. Everything works as expected, but not the Skype Call. I’m testing this config, as we are moving company wide to Teams only soon. I want to be able and call another user in Teams from a Trio using Skype. Shouldn’t this go through the “SIP to Teams audio gateway” which Microsoft has deployed? I can see the missed call in Teams, and it rings on the Trio, but I do not see the call popping up in my Teams client. Am I understanding this correctly?

      • Jeff Schertz says:

        Make sure that the user account on the Trio is set to “Teams Only” migration mode in the Teams Admin Center. If it is in “Islands” mode then this exact behavior can occur.

    36. Adam says:

      Hi Jeff. This article really explains how the Trio lives in different eco-systems. If I owned a bunch of Trios – this would be my guide. However, I haven’t purchased them yet – and my new understanding of them is causing me to ask if they are the right solution.

      In our use-case – we’re going to create huddle rooms that maybe 3-4 people can meet.

      We wanted a single device on the table that would do double duty as a SIP phone for regular voice calls – as well as a Teams Device with a camera over or under the TV for Teams Calls – with screen sharing via the USB option.

      It would appear that the correct way to do this is to place the Trio into Hybrid mode (not Teams mode) so that Line1 can be a SIP Line and Line 2 can be a RealConnect bridge. Using RealConnect (which we are using now with our Group Series) and One Touch Dial will give you a Teams-like Join environment on the Trio interface without losing your SIP/Plain Phone capabilities.

      However, it appears that when the Trio is in Hybrid Mode – you lose the ability to screen share via the USB connection – because that’s an entirely different mode requiring a reboot of the Trio. What is the easiest way to screen share in this scenario?

      Finally – if you were building a huddle room and you wanted a “starfish” type device on the table for basic phone calls and also a Teams experience in the room – does the introduction of the Studio line change all of this? Appreciate your suggestion for a room that’s yet to be built.

      • Jeff Schertz says:

        Adam, your understanding is correct. When the Trio is running in Teams base profile then it can only use the native Teams Android application and the SIP capabilities of the phone are completely unavailable. The Teams mode is best for environments which will only use Teams for meetings and voice. If you need to join meetings from several conferencing platforms (Skype, Teams, WebEx, Zoom, etc.) and/or need to register to any SIP-based platform for PBX/PSTN voice capabilities (Skype, Cisco, Avaya, etc.) then the Hybrid approach is best.

        Regarding the Studio series there are two options which will be coming. First a Trio/Visual+ deployment can be connected to a Studio but it would make more sense to use the new EagleEye Cube USB camera as that is essentially the optics of the Studio USB device without the speaker/mic. Secondly the new Studio X series devices can be paired with a Trio which will function as the control panel for the X30 or X50. That configuration still has some behaviors to iron out so it might be a but early to head down that road. I would suggest discussing this with your sales team so you can get a clear picture of what’s coming to plan out our room deployments.

    37. Eric Watkins says:

      HI Jeff,

      As always, your info is amazing. We have a full clarity deployment right now, using Skype for Business Online and Cloud Relay. We have some Trio’s setup with the VIsualPro addon, they are setup using generic sip profile, with line1 registered to our CIsco PBX for audio conferencing, and line2 registered to our Poly DMA.

      I am hoping that adding the realconnect for clariti teams support for the trio will be as simple as adding the t.plcm.vc domain to the dialplan on line2, since that already routes to the dma, which will have dial rules to send it to the realconnect services?

      • Jeff Schertz says:

        Yes, you don’t need to add an additional line on the Trio for Teams meetings when it’s registered to the DMA; in fact depending on your dial plan you might not have to do anything to the Trio. As long as you route those calls to the DMA then it’ll take care of the routing, based on having the correct configuration on the core.

    38. Adam Kuhn says:

      If the trio is in teams mode is there a way that it can operate as a regular phone? Do you have to give it an e-5 license? Where would the newer meeting room license provided with dial out capabilities? I asked this since the teams mode, as you say, turns off the sip capabilities.

    39. Przemek says:

      Hi Jeff
      so the situation is as follows
      line 1 Sfb
      line 2 teams
      line 3 SIP – VOICE.
      I’m setting up the teams meating and
      the popup from callendar apears corectly
      clicking join and im getting beep beep beep display show tenatnid.confnumber
      and there is no connection
      when I use the line 2 button and enter the confnumber it works prefectly.
      any advice ?

    40. David says:

      Fantastic article Jeff!

      I have configured the hybrid set-up on my Trio 8800s, I can launch calls and the quality is excellent. However OTD is only using SfB and wont route OTD calls through line2 / RealConnect.

      Im running the 5.9.2 firmware (I also tried rolling back to 5.9.1 but same issue). Settings on the device have all been factory reset and only changes are admin passcode, web access, and those imported in config files below.

      I dont have OTD enabled in the Poly cloud as based on this artcile the Trio doesnt need it.

      Config file I imported is below. When I export the config, it is exactly as I imported it however two lines are missing. If I set the Skype line to ‘1’ it shows on the export, making me think the only reason it doesnrt return on the export is because ‘0’ is the default value.

      Missing config from export after my import:
      exchange.meeting.realConnectProcessing.skype.enabled=”0″
      exchange.meeting.realConnectProcessing.outboundRegistration=”2″

      Imported config:

      • Jeff Schertz says:

        Yes, those two parameters won’t appear in an export as they are at the default values already. If you want to join Skype meetings using RealConnect instead of the native native Skype registration (on Line 1) then you need to set exchange.meeting.realConnectProcessing.skype.enabled=”1″. The default value of zero means that Skype meetings will be joined using the native Conference URI embedded in the invite. Setting it to “1” will make the Trio use the line defined for outbound RC call processing (default=2).

        • David says:

          Thanks Jeff!

          We only use Skype for Business for PSTN.

          Will the same setting make Teams meetings join with OTD? Thats the piece I need to solve.

          • Jeff Schertz says:

            The parameter “exchange.meeting.realConnectProcessing.teams.enabled” controls the behavior when joining a Teams meeting. The default value is “1” meaning that RealConnect will be used. If this is changed to “0” then the SfB line registration would be used to join the Teams meeting via the Gateway model (SfB<>GW<>Teams). If you only want the SfB registration on the Trio for Enterprise Voice then you want both “exchange.meeting.realConnectProcessing.skype .enabled” and “exchange.meeting.realConnectProcessing.team.enabled” set to “1”.

    41. Luis says:

      Hello. Great blog and great article. I have tried the Hybrid Mode and everything works almost fine. Where I fund an issue is when clicking on the Join button of a Teams meeting: the call starts but to an incomplete SIP URI, it calls to XXXXXXXX.XXXXXXXX@, just that, it doesn’t add the t.plcm.vc part of it. Any idea on what could be happening here?

      • Jeff Schertz says:

        Luis, most likely there is some exiting configuration in the phone conflicting with the parameters covered in this article. I’d check any dial plan related settings you may have on the phone which might be causing the problem. Better yet start with a factory reset phone, define the parameters for RealConnect and then systematically customize further from there.

        • Luis says:

          Hi Jeff, thanks for answering. That’s what I did: factory reset, no-update file uploaded, login into Skype, Realconnect file uploaded (just changing my realconnectID), testing. Skype works fine but when click the Join button from a Teams meeting, it only dials meetingID.realconnectID@, nothing after the @.

        • Luis says:

          Hi Jeff, thanks for the answer. I changed the language of my Temas app (from Spanish to English) and now it works. Is there a way for this to work in Spanish? Thanks.

          • Jeff Schertz says:

            There were some issues with the Trio processing invites in a languages other than English. The Trio 5.9.2AA firmware was recently updated to support all languages, but there is a bug that can prevent it from working as designed based on the environment configuration. A fix for that is planned in the 5.9.2AB release, but if you need a workaround today contact Poly support for more details.

    42. Ryan W says:

      Hi Jeff and co,

      Can anyone give any information on why Gateway Trio user should be in Teams Only as suggested in the article please?

      “Before registering the phone the desired user account should be set to Teams Only mode for best functionality. While this is not a requirement to leverage the gateway, but is recommended for proper functionality. If the account is in a different Teams Upgrade mode, like Islands for example, then peer calling behavior may not function correctly.”

      Thanks, Ryan.

      • Jeff Schertz says:

        If the account is in Island Mode, as explained then peer calling will be broken. Calls from one side will go to voicemail on the other side. The account must be set to ‘Teams Only’ migration mode. (This does not refer to the base profile that Trio is in, it’s the migration mode of the user account as defined in the Teams Admin Center.

    43. B says:

      Great article Jeff

      When using the hybrid mode with Poly Real Connect, how does the presence work? We have setup this up successfully, but now all our Trios show offline in Teams. At the device itself and from S4B the presence reflects the true status at that time. So for example you can’t invite the trio to a meeting directly in Teams because it shows as offline.

      • Jeff Schertz says:

        The Trio is not registering into Teams, but if you are using SfB Online/Hybrid then the presence should sync from Skype to Teams, with the accuracy depending on the account’s migration mode (Islands vs Teams Only, for example).

    44. brad says:

      Hi Jeff great article.

      Can you clarify what mode to put the TRIO in order to facilitate Teams meetings with the visual+ when the organization is in Teams only mode and also has the Real Connect service? We want to be able to put video or content on the screen? Do we keep the trio and the accouunt on the trio in S4B mode and use the RC or put the user account and the trio Teams Mode and utilize RC?

      Thanks!

      • Jeff Schertz says:

        As explained int he Hybrid section here you keep the Trio in Skype mode and then configure the parameters needed to allow unregistered SIP calls to RealConnect for Teams meeting on a second line.

        • Brad says:

          Thanks Jeff we have this working, my only issue is my Trio always show offline? To all all my users, so it doesn’t seem to be respecting presence with in my tenant. My tenant is in Island mode.

    45. Scott F says:

      Hi Jeff,

      Great articles as always thanks! In our environment, we have 250+ Trio 8800 devices of which 50 or so are paired with Visual+ boxes for an audio and video setup. All are currently Skype profiled and have been running well for a number of years.

      All our Trios are logged in with Room type accounts, not personal User accounts.

      We are transitioning to MS Teams but not yet discarding Skype which is still relevant as it is our telephony replacement.

      Currently we are in the process of implementing the hybrid model leveraging RealConnect for the video capability in MS Teams and will be applying a cfg file to the devices (by way of Resource Manager) to open up use of the secondary line.

      My question is around the Trio devices that will remain as audio only devices. If they are invited to an MS Teams meeting, will it simply appear in the Meetings section of the device with a Join button? How can you (albeit audio only) join an MS Teams meeting directly from the device if a ‘Teams Meeting’ button is not present? Following on the from last question, even if the Trio is audio only do we still need to apply the cfg file for the’Teams Meeting’ button to be present?

      Hope this makes sense?

      Thanks Scott

      • Jeff Schertz says:

        If the audio-only Trios are put into native Teams mode then the calendar will automatically show a Join button on all Teams meetings which will connect directly to the meeting. Skype meetings will have a ‘Call’ button which will connect to the Skype meeting by automatically dialing the Audio Conferencing PSTN number provided in the meeting invitation. The Teams client does not support SIP and this cannot natively connect to a Skype meeting. If the Skype meeting does not include Audio Conferencing dial-in information then the Trio cannot join that meeting when running the native Team client.

    46. Emilio says:

      Good day Jeff,

      Poly Trio in Hybrid mode.

      I would like to know how do I add additional line for SIP.

      line 1 SFB
      line 2 Teams

    47. Kareem says:

      Hey Jeff – great article. We use 8×8 for VoIP service and want to use Microsoft Teams on the Trio8800 for video conferencing as well. Is the hybrid solution what we’d be looking for to utilize both of these? Am I correct in thinking this is even possible?

    48. Ted says:

      Heya Jeff – in the doc you reference the “tenant key” in the config file. Is this the same as the O365 “tenant ID”? If not, where is it or how do I find it?

      Thanks

      • Jeff Schertz says:

        The “Tenant Key” is the numeric identifier (typically 8 to 9 digits long) given to a tenant when a Cloud Video Interop provider is setup and is used as the prefix for VTC dialstrings. The “Tenant ID” is a refernece to the Microsoft Office 365 directory ID as explained here. You can find it on your RealConnect-enabled meeting invites (e.g.

          123456789

        @t.plcm.vc) or in the RealConnect admin portal.

    49. Joerg says:

      Hey Jeff,

      We used your instructions for setting up the hybrid mode on our Trio.
      However we have issues with the invitations in Outlook. Our Trio tries to join the meetings with a wrong url:

      0218110509|app1 |5|00|[cccpScheduledMeetingJoin] Input Link(sip:xxx;gruu;opaque=app:conf:focus:id:teams:2:0!19:meeting_XXXXXXXXXXXXXXXXXXXXXXXXX-thread.v2!YYYYYYYYYYYYYYYYYYYYYYYYYYY;) Output Url(sip:xxx;gruu;opaque=app:conf:focus:id:teams:2:0!19:meeting_XXXXXXXXXXXXXXXXXXXXXXX.v2!YYYYYYYYYYYYYYYYYYYYYYYYYYY;) isCallLogRejoin(0) Subject Exist(1)

      The invitation also has the url xxxxx@t.plcm(dot)vc as alternative URL for VTC-conferences.

      Do you know if our Polycom tries to join with line1 instead of line2 or is it an issue with resolving the URLs?

      Best regards
      Jörg

    Trackbacks

    Check out what others are saying about this post...
    1. […] Poly Trio with Microsoft Teams | Jeff Schertz’s Blog — Read on blog.schertz.name/2019/08/poly-trio-with-microsoft-teams/ […]

    2. […] Teams meetings.  While several different options, both native and interoperable, were recently outlined for the Poly Trio the Group Series approach is much simpler.  This is due to the facts that (a) there are no […]



    Speak Your Mind

    Tell us what you're thinking...
    and oh, if you want a pic to show with your comment, go get a gravatar!