When a user receives a meeting invite from someone internal or external to their organization and wants to join the meeting from a video-enabled endpoint/meeting-room, JOIN allows the user to forward the invitation to an endpoint/ meeting room.
JOIN understands how to process the meeting from the contents of the invite email. JOIN then forwards the appropriate dial string to the meeting-room as the One Button to Push (Cisco OBTP) or Click to Join (Polycom CTJ) message
These meeting invitations are processed based on regex rules in Synergy JOIN.
To find out what a regex rule is and how they work with Synergy JOIN click here
Below we have listed all of the various meeting types,matching rules and the replace values for forwarding Skype for Business meetings using different MCUs.
All of the Regex matching rules require the Rule Type
- Skype URI in Headers
- Skype URI in Body
Microsoft Skype for Business Meeting via Pexip Gateway
Matching value
- None
Replace value
- S4B.(SkypeMeetingId).(SkypeUserId)@(UserDomain)
Applies to
- Internal Invitations
- All Invitations
Microsoft Skype for Business Meeting via Cisco CMS
Matching value
- None
Replace value
- (SkypeURL)@CompanyCMSDomain.local
Applies to
- Internal Invitations
- All Invitations
Microsoft Skype for Business Meeting via Cisco CMS (Internal invitations Only)
Matching value
- None
Replace value
- (SkypeURL)@CompanyCMSDomain.local
Applies to
- Internal Invitations
Microsoft Skype for Business Meeting via Videxio
Matching value
- None
Replace value
- __sfb__.(SkypeMeetingId).(SkypeUserId)@(UserDomain)
Applies to
- Internal Invitations
Microsoft Skype for Business Meeting via Videonor
Matching value
- None
Replace value
- S4B.(SkypeMeetingId).(SkypeUserId)@(UserDomain)
Applies to
- Internal Invitations
- All Invitations
Microsoft Skype for Business Meeting via StarLeaf Cloud
- No matching rule configuration required