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.

As an example, you can create rules that define that JOIN should do the following:

  1. Look for personal VMRs in invites from internal users.
  2. Look for Skype invites from all users.
  3. Create a one-time-VMR if neither 1 or 2 apply.

Configuring the General Rules

Configure the General Rules as follows:

Field Description
Internal email domains Specify a comma separated list of the email domains your organization uses. This list is used to determine whether a meeting room invitation is sent from an internal or external user. It is also used to determine which users are internal and external when sending out connection information emails. (e.g. synergysky.com, synergysky.eu, synergysky.us)

Creating the rules

First, select the type of rule you want to add from the Add Rule dropdown menu:

Rule type Description
Skype URI in Headers

This rule makes JOIN look for Skype invites in hidden text in the invite.

This will normally work for all Skype meetings when the invitation is sent internally in the organization. The information may however be lost if the email jumps multiple Exchange servers, or when the invite comes from someone outside the organization.

Skype URI in Body

This rule analyzes the Hyperlink in the body of the invitation to find the URI of the Skype meeting. This will work in most environments, both internally and externally, but is slower. It is therefore recommended to use this as a fallback rule with lower priority than the Skype URI in Headers rule.

NOTE: This function requires Synergy JOIN to have access over HTTPS to the Skype server where the meeting is hosted; either directly or via a proxy server.

Teams URI in Headers

This rule makes JOIN look for Teams invites in hidden text in the invite.

This will normally work for all Teams meetings when the invitation is sent internally in the organization. The information may however be lost if the email jumps multiple Exchange servers, or when the invite comes from someone outside the organization.

NOTE: The Teams rule should be added with a high priority than the Skype rules, since Teams invitations also contains an Skype invitation in the header

Teams URI in Body

This rule makes JOIN look for Teams invites in the meeting body via Regex rule. The rule can be adjusted according to the pattern in your Teams setup.

Regex Rule

This rule enables you to use Regex to define how you want JOIN to work. You can define your own pattern matches, and differentiate between invitations from internal and external organizers.

You can define both matching patterns and replace patterns to transform the URI when required.

This rule can be added multiple times.

Hangout Meet This rule enables JOIN to look for Google Hangout meetings in the Body of the Google Hangouts Meeting via Regex rule. This rule is prepopulated when you select it

Skype URI in Headers

Configure the remaining fields as follows:

Field Description
Priority

The priority defines the order in which the rules are applied. The lowest number gives the highest priority. (E.g. 1 is processed before 5).

Applies to

Internal invitations

Matching value

Not applicable

Replace value

Pexip:

S4B.(SkypeMeetingId).(SkypeUserId)@(UserDomain)

where:

  • SkypeMeetingId = alphanumeric meeting Id found in every Skype meeting invite
  • SkyperUserId = the userpart of the organizer’s Skype SIP URI
  • UserDomain = the domain in the organizer’s Skype SIP URI

NOTE: For Organizations with a Pexip Gateway hosted by a Service Provider, the recommended pattern would be:

S4B.(SkypeMeetingId).(SkypeUserId)_(UserDomain)@serviceProvidersDomain.com

This allows the Service Provider to strip away their domain and replace the underscore with @ before sending the call through the Pexip Gateway.

CMS:

(SkypeURL)@CompanyCMSDomain.local

where:

CompanyCMSDomain.local = the routing domain that ensures the call is routed to the CMS.

Note: This domain must also be added as a “Targets Lync Simplejoin” domain on the CMS under Configuration > Incoming Calls.

StarLeaf Cloud:

This field is disabled as the required value is automatically configured.

Skype URI in Body

Configure the remaining fields as follows:

Field Description
Priority

The priority defines the order in which the rules are applied. The lowest number gives the highest priority. (E.g. 1 is processed before 5).

Applies to

All invitations

Matching value

Not applicable

Replace value

Pexip:

Use the same format as for Skype URI in Headers.

CMS:

Use the same format as for Skype URI in Headers.

StarLeaf Cloud:

This field is disabled as the required value is automatically configured.

Teams URI in Headers

Configure the remaining fields as follows:

Field Description
Priority

The priority defines the order in which the rules are applied. The lowest number gives the highest priority. (E.g. 1 is processed before 5).

Applies to

Internal invitations

Matching value

Not applicable

Replace value

Pexip:

Teams.(TeamsMeetingId)@company.com

where:

  • TeamsMeetingId = alphanumeric meeting Id found in the Teams meeting invite

The URI needs to match the Teams gateway rule in the Pexip configuration. Please refer to the Pexip documentation for more details

Teams URI in Body

Configure the remaining fields as follows:

Field Description
Priority

The priority defines the order in which the rules are applied. The lowest number gives the highest priority. (E.g. 1 is processed before 5).

Applies to

All invitations

Matching value

Not applicable

Replace value

Pexip:

Use the same format as for Skype URI in Headers.

 

Hangout Meet

Configure the remaining fields as follows:

Field Description
Priority

The priority defines the order in which the rules are applied. The lowest number gives the highest priority. (E.g. 1 is processed before 5).

Applies to

All invitations

Matching value

This field defines the Regex rule for matching data . For example:

\d@company.com will match all URIs starting with a number and ending with @company.com)

This field is prepopulated to catch all hangout meetings

Replace value

This field defines how the matched data should be transformed before being sent to the endpoint.

This field is pre-populated to replace the matching value that has been identified.

Regex

Configure the remaining fields as follows:

Field Description
Priority

The priority defines the order in which the rules are applied. The lowest number gives the highest priority. (E.g. 1 is processed before 5).

Applies to

All invitations

Matching value

This field defines the Regex rule for matching data . For example:

\d@company.com will match all URIs starting with a number and ending with @company.com)

Replace value

This field defines how the matched data should be transformed before being sent to the endpoint.

Pexip:

The value \0 uses the entire matched value, while \1 matches the first pair of parenthesis and so on.

Example:

Matching Value: Id: (\d)

Replace Value: \1@video.company.com

Email body: Conference Id: 123456789

URI = 12346789@video.company.com

CMS:

If you have CMS for internal dual-home, you can use a regex rule to look for "conference id: 123456" from internal meeting organizers.

Testing, editing and deleting rules

Click the large Test button in the Add Rules area of the Matching Rules tab to launch the Regex Test Tool. The tool will help you identify any errors in your regex by testing a Matching Value and Replace Value towards a text field: