Configuring Call Routing Rules

This is your fallback rule. It matches aliases that do not end in @example.com (i.e. calls to domains outside of your environment) and routes it out over SIP either via your local SIP proxy or via DNS.

Your fallback rule should ignore all of your domains that are serviced by your Pexip Infinity deployment (for example vc.example.com, vmr.example.com etc). To ignore multiple domains, you could use an expression formatted in the style:
(?!.*@(example\.com|another\.com|vc\.example\.com)$).*
which would ignore the example.com, another.com and vc.example.com domains.

Note that these example expressions do not produce any match groups and do not require a replace string (hence the dialed alias is passed on unchanged if the match is successful).

You could also tighten the match to only allow certain address formats for the external addresses such as name@domain i.e. (?!.*@example\.com$).+@.+

The name used to refer to this rule.

If you are using a Virtual Reception as an IVR gateway to capture a conference ID, and then using this Call Routing Rule to transfer the participant into an external conference such as Google Meet or a Microsoft Teams meeting, then the rule Name entered here is shown to conference participants as they are transferred into the meeting (it is overlaid onto the virtual_reception_connecting splash screen of the theme associated with the Virtual Reception that is transferring the call).

Assign a relative priority to this rule, from 1 to 200. Rules are checked in order of priority, starting with 1 and working down the list until a match is found.

Rule checking stops when a match is found, even if the call that is placed as a result of that match fails for any reason.

Applies this rule to incoming calls that have not been routed to a Virtual Meeting Room, Virtual Auditorium, Virtual Reception, scheduled conference, Media Playback Service, or Test Call Service, and thus should be routed via the Infinity Gateway.

Default: selected.

Applies this rule to outgoing calls placed from a conferencing service (e.g. when a participant is added to a Virtual Meeting Room) where Automatic routing has been selected.

Default: not selected.

Note that the same rule can be applied to both incoming and outgoing calls if required.

You can select a specific location, which means:

• for incoming calls, the rule is only applied if the call is being handled (for signaling purposes) by a Conferencing Node in the selected location.
• for outgoing calls, the rule is only applied if the call is being initiated from the selected location.

This allows you to restrict the types of calls that some users can make. For example, you may use a call control system that routes all calls into Pexip Infinity through Conferencing Nodes in an "internal/trusted" location, whereas calls received from devices in the public internet could all be routed to nodes in a different "public/untrusted" location. You can then, for example, use the Calls being handled in location option to allow only calls received in the "trusted" location to place calls via a PSTN gateway.

To apply the rule regardless of the location, select Any Location.

Default: Any Location.

Select this option if you want this rule to only apply to incoming calls from devices, videoconferencing endpoints, soft clients or Connect apps that are registered to Pexip Infinity. Note that:

• The incoming call must be received by the same Conferencing Node as to which the device is registered. This is the normal behavior for most endpoints, however you may need to ensure that the SIP Proxy and Registrar are both configured to resolve to the same node.
• The call must also match one of the selected protocols below.

Calls placed from non-registered clients or devices, or from the Connect web app will not be routed by this rule if it is enabled.

Default: disabled.

Match Infinity Connect (WebRTC/RTMP)

Match SIP

Match Lync / Skype for Business (MS-SIP)

Match H.323

Match Teams

Select the source / protocols of the incoming call to which the rule should apply. Note that matching Lync / Skype for Business (MS-SIP) and Teams calls options do not apply if Match incoming calls from registered devices only is selected.

Default: these options, except for Teams, are all enabled by default.

This setting is for advanced use cases and will not normally be required.

By default, Pexip Infinity matches against a parsed version of the destination alias, i.e. it ignores the URI scheme, any other parameters, and any host IP addresses. So, if the original alias received by Pexip Infinity is sip:alice@example.com;transport=tls for example, then by default the rule will match against alice@example.com.

Select this option to match against the full, unparsed alias instead.

You must select this option if you are using this rule to support your Skype for Business / Lync IVR gateway (where this rule is routing calls handled by a Virtual Reception into the relevant Skype for Business / Lync meeting).

The regular expression that the destination alias (the alias that was dialed) is checked against to see if this rule applies to this call.

Pexip Infinity supports case-insensitive Perl-style regular expression patterns. Note that the regex must match the entire alias — a partial match is treated as a non-match. See Regular expression (regex) reference for information about writing regular expressions.

The regular expression string used to transform the originally dialed alias (if a match was found).

If you do not want to change the alias, leave this field blank.

Enter a value in this field to limit the bandwidth of media being sent from Pexip Infinity to each individual participant dialed out from this rule. For more information see Managing and restricting call bandwidth.

When dialing out from a conference, the outbound call bandwidth limit is inherited from the VMR's bandwidth settings. In this case, the rule's outbound bandwidth setting configured here is not used.

Allows you to limit the media content of the call. The participant being called will not be able to escalate beyond the selected capability. For more information, see Controlling media capability.

Default: Main video + presentation.

Controls the maximum call quality for participants connecting to this service:

• Use global setting: use the global maximum call quality setting.
• SD: each participant is limited to SD quality.
• HD: each participant is limited to HD (720p) quality.
• Full HD (1080p): allows any endpoint capable of Full HD to send and receive its main video at 1080p.

Default: Use global setting

See Setting and limiting call quality for more information.

Controls the media encryption requirements for participants connecting to this service.

• Use global setting: use the global media encryption setting.
• Best effort: each participant will use media encryption if their device supports it, otherwise the connection will be unencrypted.
• Required: all participants (including RTMP participants) must use media encryption.
• No encryption: all H.323, SIP and MS-SIP participants must use unencrypted media. (RTMP participants will use encryption if their device supports it, otherwise the connection will be unencrypted.)

Default: Use global setting

The theme to use for calls placed using this rule. See Themes used by Call Routing Rules (gateway calls) for more information.

Default: <use Default theme> (the global default theme is used).

The device or system to which the call is routed. The options are:

• Registered device or external system: route the call to a matching registered device if it is currently registered, otherwise attempt to route the call via an external system such as a SIP proxy, Skype for Business / Lync server, H.323 gatekeeper or other gateway/ITSP.
• Registered devices only: route the call to a matching registered device only (providing it is currently registered).
• Lync / Skype for Business meeting direct (Conference ID in dialed alias): route the call via a Skype for Business / Lync server to a Skype for Business / Lync meeting. Note that the destination alias must be transformed into just a Skype for Business / Lync Conference ID.
• Lync / Skype for Business clients, or meetings via a Virtual Reception: route the call via a Skype for Business / Lync server either to a SfB/Lync client, or — for calls that have come via a Virtual Reception — to a Skype for Business / Lync meeting. For Skype for Business / Lync meetings via Virtual Reception routing, ensure that Match against full alias URI is selected and that the Destination alias regex match ends with .*
• Google Meet meeting: routes the call to a Google Meet meeting. See Integrating Google Meet with Pexip Infinity for more information.
• Microsoft Teams meeting: routes the call to a Microsoft Teams meeting. See Integrating Microsoft Teams with Pexip Infinity for more information.
• Microsoft Teams Room: routes the call to a Microsoft Teams Room. See Integrating Microsoft Teams with Pexip Infinity for more information.
• Epic Telehealth Profile: used for telehealth calls. See Epic telehealth integration with Pexip Infinity for more information.

When calling an external system, this forces the outgoing call to be handled by a Conferencing Node in a specific location.

When calling a Skype for Business / Lync meeting, a Conferencing Node in this location will handle the outgoing call, and — for Lync / Skype for Business meeting direct targets — perform the Conference ID lookup on the SfB/Lync server.

Select Automatic to allow Pexip Infinity to automatically select the Conferencing Node to use to place the outgoing call (which will usually be the node that received the call).

The protocol used to place the outgoing call. Note that:

• If the call is to a registered device, Pexip Infinity will instead use the protocol that the device used to make the registration.
• RTMP (streaming) always routes to an external system.

Default: SIP.

You can optionally specify the SIP Proxy to use to place an outgoing SIP call.

Default: Use DNS.

You can optionally specify the H.323 Gatekeeper to use to place an outgoing H.323 call.

Default: Use DNS.

When calling an external system, this is the Skype for Business / Lync server to use for outbound SfB/Lync (MS-SIP) calls.

When calling a Skype for Business / Lync meeting, this is the SfB/Lync server to use for the Conference ID lookup and to place the call.

Default: Use DNS (note that a server must be selected when the Call target is Lync / Skype for Business meeting direct (Conference ID in dialed alias)).

You can optionally select the Teams Connector you want to handle the call. If you do not specify anything, the Teams Connector associated with the outgoing location is used.

Select the name of the access token to use to resolve Google Meet IDs. You should select either a trusted or untrusted type of token, depending on whether you want to enable the device to be automatically admitted into the Google Meet conference (subject to also being a trusted endpoint from Pexip Infinity's perspective i.e. if the rule also has Treat as trusted enabled).

Typically, you will use a trusted token if Treat as trusted is selected, and an untrusted token if Treat as trusted is not selected.

See Enabling access and admitting external participants into Google Meet conferences for more information.

This indicates that the target of this Call Routing Rule may treat the caller as part of the target organization for trust purposes. It can be applied to calls placed to:

• Microsoft Teams
• Google Meet
• SIP destinations and registered SIP devices (via a P-Asserted-Identity in the SIP header)

When enabled, participants using the Connect web app are given the option to turn on the live captions for conferences using this service.

• Use global live captions setting: as per global configuration setting.
• Yes: live captions may be enabled.
• No: live captions cannot be enabled.

Default: Use global live captions setting

This is a technology preview feature and can be enabled via Platform > Global settings > Tech preview features > Live captions, and then on a per VMR or per Call Routing Rule basis. See Global Settings for more information.

Applies to Microsoft Teams integrations only. This determines whether or not the Teams Connector requests from Exchange Online an avatar for each participant in the Teams conference.

• Use global setting: use the global external participant avatar lookup setting.
• Yes: request the participant avatar from Exchange Online via the Teams Connector.
• No: use default avatar behavior.

Default: Use global setting

Applies to Google Meet integrations only. Controls whether to remove background noise from audio streams as they pass through the infrastructure.

Some endpoints perform their own built-in denoising, in which case, to avoid performing denoising twice, you can configure via the theme's vendordata.json file a list of endpoints that perform their own denoising. See Rules and requirements for customized themes for more information.

Default: enabled.