How Synergy JOIN works

All features of JOIN listed below are available for all Microsoft Exchange & Google Calendar integrations:

  • Cisco One Button To Push(Cisco OBTP)
  • Polycom One Touch Dial (Polycom OTD)
  • Scheduling of Personal VMRs
  • Scheduling of One-time/Dynamic VMRs
  • In-body updates of invites for One-time/Dynamic VMRs

Feature overview

JOIN supports the following feature set:

  • Booking Skype4B, MS Teams, WebEx, Zoom or Google Hangouts meetings using Outlook or your current Calendaring system. JOIN creates a URI for the meeting that is sent as Cisco One Button To Push (Cisco OBTP) or Polycom One Touch Dial (Polycom OTD) to all video endpoints scheduled in the same meeting.
  • Booking Dynamic VMRs (Cisco and Pexip only):
    • Endpoints receive the URI as Cisco OBTP or Polycom OTD
    • End users receive the URI as a Webrtc link in their calendar
  • JOIN can identify patterns in meeting room invitations so that the endpoint can be populated with Cisco OBTP or Polycom OTD information for personal VMRs (e.g. meet.js@example.org).
  • JOIN can be configured to dial out to booked endpoints that don't support Cisco OBTP or Polycom OTD at the meeting start time.
  • Emails containing the dial-in information for the meeting can automatically be sent to the meeting participants (both internal and external participants).

Overall process from install to end user

  1. After installation, video admins add the following information into the JOIN configuration tool:
    • Exchange or Google server connection settings.
    • MCU details (Pexip, Cisco Meeting Server (CMS) Videonor, StarLeaf Cloud [or left blank if no supported MCU]).
    • Exchange Meeting-room resources or Google Hangouts meeting resources.
    • Video endpoint information (Room IP Address, User name and Password are required for Cisco OBTP)

  2. Users book a video meeting from Outlook, inviting one or more video-enabled meeting-room resources.
    • Users book a Google meeting from their Google Calendar, inviting one or more video enabled meeting-room resources.

  3. JOIN monitors the meeting-room resource at various intervals to check if a meeting invitation has been received.
  4.  In the below example a Skype4B meeting has been scheduled with a Pexip MCU:
    • Skype invitations sent to meeting-room resources include a URI in this format: sip:js@example.org;gruu;hhsbcghdfnopaque=app:conf:focus:id:ABC123456
    • JOIN rewrites to a URI the meeting-room endpoint can call eg: S4B.ABC123456.js@example.org

    The Below example examples are for Dynamic or Ad-Hoc Meetings

    • For Ad-Hoc meetings, a numeric 5 or 6 digit number is populated based on a number pool that is configured by the administrator
    • For personal VMR meetings, the URI in the invite body is identified as the URI.

  5. The URI is sent to the endpoint as Cisco OBTP or Polycom OTD ready for attendees to start the meeting. The user receives a click-able WebRTC link to join the meeting from their computer

  6. The call is routed through the gateway and all attendees turn up in the same virtual meeting room, irespective of the medium used to join the meeting