Poly Trio on the PEXIP Service with OTJ using Synergy JOIN


This blog will cover how to register your Poly (Polycom) Trio to the Pexip Service and how to configure OTJ (One Touch Join) for the Trio. The reason we are using Synergy JOIN here is because we are making use of the multiple regex match rules. With the Trio you can only natively apply one regex rule per line, so you are very limited what what kind of meetings you can match.

The Trio will not need to be registered to Skype for Business. This will enable a Trio to register to the Pexip service with SIP, features included are:

  • Touch keyboard SIP URI dialling
  • Calendar invite to Pexip VMR invite from internal
  • Calendar invite to Skype for Business invite from internal
  • Calendar invite to Microsoft Teams invite from internal
  • Calendar invite to Google Hangouts Meet invite from internal
  • Calendar invite to Zoom, BlueJeans, WebEx meeting invites from internal

Optionally also all the above, OTJ from external and forwarded invites to the Endpoint resource account, by setting ProcessExternalMeetingMessages $TRUE when configuring the Endpoint Resource account.

NOTE: Enabling ProcessExternalMeetingMessages does not in any way expose the information of existing meetings to external users.

Registering the Trio to the Pexip Service with SIP

Prerequisites for the purpose of registration and OTJ compatibility with Synergy JOIN:

  • You have to be running Synergy JOIN build 3.2.163 or above
  • If running on the Trio you must upgrade to and set basic auth to enabled
  • You must use the EWS emulator in Synergy JOIN to enable the Poly Click To Join functionality on your Poly endpoints.

Provision the device within the Pexip Service as normal. Don't forget to add the Trio's serial number ( download the Trio configuration by clicking the Polycom Trio Manual Config button.


NOTE: It is highly recommended that you clear the Trio configuration before uploading the new configuration. Uploading a new configuration file to a Trio is an additive process and does not delete any existing configuration from the Trio, and your old configuration in conjunction with the new configuration may cause it to behave unexpectedly.

For more details on how to register your Trio to the Pexip Service, please see: https://support.pexip.com/hc/en-us/articles/360009650073-Registering-a-Polycom-Trio-

Here is a sample configuration. Make any necessary changes, e.g. displayName and then upload to the Trio.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>





The Trio should now register to the Pexip Service.


Configuring Synergy JOIN

Deploy Synergy JOIN as recommended in Synergy SKY's documentation: https://support.synergysky.com/join/synergyjoin/installation.htm

For OTJ to work, the Trio will need to connect to the Synergy EWS emulator instead of Exchange. 

The Polycom Exchange Web Service (EWS) Emulator in Synergy JOIN acts as an Exchange Web Server. This means Synergy JOIN will retrieve the calendar information from Exchange and populate the necessary information on the endpoint.

Within Synergy JOIN you have to enable the EWS Emulator from the Services tab.


You have to then configure your Trio as a Polycom endpoint. Once you do this, Synergy JOIN will know to send the Poly Click To Join token to it.

Configuring the Poly Trio endpoint

You have to meet the following requirements in order to start using the EWS Emulator with Poly Trio:

  • You have to be running Synergy JOIN build 3.2.163 or above
  • You have to tick the Enable Basic Authentication for EWS Emulator in the Services tab on the Synergy JOIN configuration interface
  • The Trio has to have a line registered as SIP
  • You have to have physical access to the touch panel to set a username and password
  • If you are running 5.9 firmware, AD Photo fetch needs to be disabled on the Trio
    • feature.contactPhotoIntegration.enabled = 0
    • More information about this can be found at: https://documents.polycom.com/bundle/trio-sfb-dg-5-9-0-AA/page/c3189620.html
  • If the Trio is running it must be upgraded to and basic auth set to enabled
    • feature.exchange.allowBasicAuth= “1”
    • More information about this can be found at: https://community.polycom.com/t5/VoIP-SIP-Phones/Software-Trio-UC-Software-5-9-1-11135-RevAC/m-p/107281


Setting a Polycom Profile

The following setup information has been taken from the Poly support website. Itis what is required in order for the EWS Emulator to work with the Trio.
The full Poly documentation can be found here: https://otd.plcm.vc/support/docs/devices/polycom-trio#configure-device-profile


Configure Device Profile

  1. Go to the management section of the device. You can get there by entering the IP address of the device into the browser address.
    : You must log in as an administrator.
  2. Select Simple Setup from the tab menu.
  3. Ensure Generic is selected for the Base Profile. The Trio will not function with One Touch Dial service using the other profile options.


Configure Device Calendaring

  1. Go to the management section of the device. You can get there by entering the IP address of the device into the browser address. Note: You must log in as an administrator.
    Example: https://<ip-address-of-trio>/
  2. Select Settings > Applications > Exchange Applications.
  3. Enter the following fields:
    • Enable: Exchange Calendar
    • Disable: AutoDiscover
    • Exchange Server URL: https://ipaddressofjoin/EWS/Exchange.asmx
      • NOTE: Exchange URL is case sensetive
  4. Click Save.


Configure Device Credentials

  1. Provide calendaring credentials. This must be done on the device itself.
  2. On the device touch panel go to Settings > Basic > Login Credentials.
  3. Enter the following fields:
    • Domain: Alias Domain - onpexip.com
    • Username: Example - trio-test@onpexip.com
      • This is the room alias as it is configured in JOIN
    • Password: Example F3kDFyu1bD
      • This is the JOIN EWS Emulator password

  4. Click Save. The Registration Status should display Registered and the calendar should appear in a few seconds.


MS PowerShell Exchange Service user and Room Resource account requirements

Add-MailboxPermission -Identity <roomAlias> -User <ServiceAccount> -AccessRights FullAccess
Set-CalendarProcessing <roomalias> -DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false -AddOrganizerToSubject $false -ProcessExternalMeetingMessages $true

The embedded test tool in the JOIN Configurator can be used to verify most of these properties, and suggests PowerShell commands to configure the rooms according to the JOIN recommendations.

Creating Matching Rules

After configuring the General Settings, you need to create matching rules.

The matching rules in JOIN allow you to define how calendar bookings should be processed.

  • The syntax being used to call into a Skype for Business meeting from a video system registered on the Pexip service is the following,
Skype URI in Body and in Header: Under replace value, no match required:

(note that there is a double underscore both before and after sfb)
  •  Configuring a matching rule for a Pexip VMR invitation:
Matching value: [a-z0-9._-]+vmr@pexip.com

Replace value: \0
  • Teams URI in Body "all invitations"

Replace with \4\2


More can be found here:




Now the device will be able to dial a SIP URI by clicking on the place a call icon; when it is invited to a meeting it will show a OTJ Join button.

The Device will show the Line 1 Registration as below.


Example Teams meeting JOIN button on the Trio.


OTJ on the Trio Screen:


Was this article helpful?
3 out of 3 found this helpful
Have more questions? Submit a request



Please sign in to leave a comment.