Creating preconfigured links to launch conferences via Connect apps

You can construct URLs or hyperlinks that may be used to automatically launch the Connect app and take the user directly into a specific conference. These URLs can also pass in any additional information specific to that call, such as the caller's name or the PIN needed to enter the meeting.

The URLs are in two formats: one that can be used to launch the web app, and one for use with the desktop and mobile clients.

Alternatively, you can construct a URL that directs the user to a webpage on a Conferencing Node where the full set of join instructions for a specific VMR is shown. These join instructions can optionally include a QR code, which when scanned by a device with a supported Connect app installed (such as Pexip Connect for RealWear or the Connect mobile app) will open the meeting directly in the app. For more information, see Links to a join instructions page.

Security considerations

Although embedding information such as participant names and conference PINs into the URL can make it easier for participants to join conferences, note that these parameters are included in the URL in human-readable format. This means that if a user shares the URL — such as in a screen shot of their meeting invitation — and the URL includes the PIN, anyone with access to the URL can deduce the PIN and enter (and control, if it is a Host PIN) the meeting.

As of version 25 of Pexip Infinity, when a user follows a link to join a conference via the Connect web app, any join parameters, such as a conference PIN, are automatically removed from the URL that is displayed in the browser's address bar.

Links to the web app

Links to the home screen

To open an instance of the Connect web app in the user's default browser and take them to the home screen (not into a specific meeting), use the following link:

https://<address>/<path>

where:

<address> is the IP address or domain name of the Conferencing Node (or reverse proxy if, for example, it is being used to host a customized version of the web app).
<path>

is an optional parameter that specifies the branding path to be used. If no path is specified, users will be redirected to the default path for Webapp3.

For more information, see Default paths and default branding.

Links to a specific meeting with no additional parameters

To provide users with a URL that, when clicked, directs them to a specific meeting, but still requires them to enter any information such as their name and the PIN, and does not control their camera or mic mute, use the format:

https://<address>/<path>/m/<alias>

where:

<address> is the IP address or domain name of the Conferencing Node (or reverse proxy if, for example, it is being used to host a customized version of the web app).
<path>

specifies the branding path to be used.
<alias> is one of the aliases for the conference or service the user will join.

Links to a specific meeting with additional parameters included

To provide users with a URL that, when clicked, takes them straight into a specific conference and also determines in advance settings including their role, the PIN, their camera and mic mute state, construct a URL in the format:

https://<address>/<path>/#/?conference=<alias>&name=<name>&pin=<PIN>&role=<role>&muteMicrophone=<muteMicrophone>&muteCamera=<muteCamera>&callType=<callType>&callTag=<callTag>&extension=<extension>&bandwidth=<bandwidth>&join=<join>&lng=<lng>

where:

<address> is the IP address or domain name of the Conferencing Node (or reverse proxy if, for example, it is being used to host a customized version of the web app).
<path>

is an optional parameter that specifies the branding path to be used. If no path is specified, users will be redirected to the default path for Webapp3.

For more information, see Default paths and default branding.
<alias> is one of the aliases for the conference or service the user will join.
<name> is the name of the user who is joining the conference.
<PIN> is either the Host PIN or Guest PIN, if required (note the Security considerations if these are included).
<role>

For Connect Webapp3 participants, if role=guest is included in the URL, they will be offered an alternative join flow that takes them through the setup of their camera, microphone and speakers before they are able to Join the meeting. For more information, see Support for first-time and infrequent users.

For Connect Webapp2 participants, use role=guest if you want to allow Guests to automatically join a conference that allows Guests but has no Guest PIN. In all other cases, participants are asked to enter a PIN to join the conference (unless there is no Host PIN, or the URL already specifies a <PIN>); the PIN determines the participant's role and the <role> is ignored. Note that if role=host, participants are still prompted to enter the Host PIN to join the conference; this parameter cannot be used to bypass PIN entry requirements.
<muteMicrophone> is true to join without sending audio (the user will still receive audio, and send and receive video).
<muteCamera> is true to join without sending video (the user will still receive video, and send and receive audio).
<callType>

(Supported in Webapp2, and Webapp3 from Pexip Infinity v33)

is one of:

  • none to join as a presentation and control-only participant, i.e. the user will not send or receive any audio or video.
  • audioonly to join as an audio-only participant, i.e. send and receive audio but not send or receive video.
  • video (the default) to join as a full (send and receive) audio and video participant.

Additional parameters available in Webapp3 only:

  • audiorecvonly to receive but not send audio, and not send or receive video.
  • audiosendonly to send but not receive audio, and not send or receive video.
  • videoonly to send and receive video, but not send or receive audio.
  • videorecvonly to receive but not send video, and not send or receive audio.
  • videosendonly to send but not receive video, and not send or receive audio.
  • audiovideosendonly to send audio and video, but not receive audio or video.
  • audiovideorecvonly to receive audio and video, but not send audio or video.

In all cases, the participant can still access the conference controls and chat, and send and receive presentations.
<callTag>

(Supported in Webapp2, and Webapp3 from Pexip Infinity v33)

Assigns a call tag for this participant, which is included in logs, policy requests, and participant lists. For more information, see Tracking usage via service and participant call tags.
<extension> is the Virtual Reception extension, or the Microsoft Skype for Business Conference ID.
<bandwidth> is the maximum bandwidth for the call, and the bandwidth at which the initial call attempt will be made, in kbps. It can be any number between 256 and 6144.

<join>

(Not supported in Webapp2)

is 1 if you want the participant to automatically join the conference, bypassing the option to check their devices.
<lng>

(Not supported in Webapp2)

is the code for one of the supported languages, in order to display Connect Webapp3 in that language. Note that this will override any of the user's own browser language settings.

The URL should always include the alias parameter. The remainder of the parameters are optional. If a parameter is not specified in the URL but is required when joining (i.e. name, and PIN if the conference uses PINs, or extension if one is requested), the participant will have to provide the information themselves before they can join the conference.

This URL structure will not work on version 24 or earlier of Pexip Infinity, but any URLs using the previously recommended structure (https://<address>/webapp/conference/<alias>?<parameters>) will still work on v25 and later, and the join parameters (but not the alias) will be removed from the browser's address bar.

Examples

Assuming the domain name of your Conferencing Node is vc.pexample.com, and there is a Virtual Meeting Room with the alias meet.alice, which has no PIN:

  • the basic URL for someone to join the VMR directly would be:

    https://vc.pexample.com/webapp/#/?conference=meet.alice

  • to set the display name for a participant e.g. "Bob", the URL would be:

    https://vc.pexample.com/webapp/#/?conference=meet.alice&name=Bob

    (Note that if you shared this same link with many participants, they would all join with their display name set to "Bob".)

If we then gave the same Virtual Meeting Room a Host PIN of 1234, and allowed Guests to join without a PIN:

  • the URL for Bob to join it directly as a Host would be:

    https://vc.pexample.com/webapp/#/?conference=meet.alice&name=Bob&pin=1234

  • the URL for Bob to join it directly as a Guest would be:

    https://vc.pexample.com/webapp/#/?conference=meet.alice&name=Bob&role=guest

Alternative structure to join with an invitation card

(Supported in Webapp2 only)

You can use an alternative URL structure in the format:

https://<address>/webapp/home?conference=<alias>

In this case the web app will launch with an invitation to join the nominated <alias>, and it gives the user an opportunity to modify their settings (such as camera, mic and so on) before joining the conference, and they can select whether they want to join with video, voice, or content and control only.

This can be useful in scenarios where a user has previously set their camera to None, and are unable to modify their device settings if they have been taken directly into a conference.

Links to the desktop and mobile clients

You can create a URL that, when clicked, opens the Connect app on that device and provides an invitation to join the nominated conference. The same URL can be used for the desktop client and mobile clients for Android and iOS. This URL can be included in web pages, instant messages or emails (but note that some email clients such as Gmail will strip them out for security reasons).

The Connect app desktop or mobile client must already be installed on the device.

The URL is in the format:

pexip://<alias>?host=<domain>&name=<name>&pin=<PIN>&role=<role>&muteMicrophone=<muteMicrophone>&muteCamera=<muteCamera>&extension=<extension>&bandwidth=<bandwidth>

where:

<alias> is one of the aliases for the conference or service the user is invited to join.
<domain> is the IP address or domain name of the Conferencing Node (or reverse proxy if, for example, it is being used to host a customized version of the web app) the client should connect to in order to place the call. Note that this is ignored if the client is registered and Route calls via registrar is enabled.
<name> is the name of the user who is joining the conference.
<PIN> is either the Host PIN or Guest PIN, if required (note the Security considerations if these are included).
<role> is guest if you want to allow Guests to join a conference without having to enter a PIN (providing the conference allows Guests and has no Guest PIN). In all other cases, participants are asked to enter a PIN to join the conference (unless there is no Host PIN, or the URL already specifies a <PIN>); the PIN determines the participant's role and the <role> is ignored. Note that if role=host, participants are still prompted to enter the Host PIN to join the conference; this parameter cannot be used to bypass PIN entry requirements.
<muteMicrophone> is true to join without sending audio (the user will still receive audio, and send and receive video).
<muteCamera> is true to join without sending video (the user will still receive video, and send and receive audio).
<extension> is the Virtual Reception extension, or the Microsoft Skype for Business Conference ID.
<bandwidth> is the maximum bandwidth for the call, and the bandwidth at which the initial call attempt will be made, in kbps. It can be any number between 256 and 6144.

The URL must always include pexip://<alias>. The remainder of the parameters are optional. If a parameter is not specified in the URL but is required when joining (i.e. name, and PIN if the conference uses PINs, or extension if one is requested), the participant will have to provide the information themselves before they can join the conference.

Example - email footer

For example, Alice's personal meeting room has the alias meet.alice@pexample.com so she includes the following text in her email footer:

  • Video: <a href="pexip://meet.alice@pexample.com">meet.alice@pexample.com</a>

which displays as:

  • Video: meet.alice@pexample.com

Now, when someone who has a Connect app installed on their device clicks on the link in Alice's email, their client will open automatically with an invitation to join meet.alice@pexample.com, and all they need to do is select whether they want to join with video, voice, or content and control only:

Example - Guest PIN

Alice's personal meeting room has a Guest PIN of 1234. When Alice is chatting with a colleague using an instant messaging client and she wants to move the conversation to video, she sends them the message pexip://meet.alice@pexample.com?pin=1234, which automatically appears as a hyperlink. Her colleague clicks on the link and is invited to join Alice's personal meeting room as a Guest.

Example - always join with microphone muted

If you want the participant to join a meeting with a PIN of 1234, and you want their microphone to be muted on joining, the URL would be: pexip://meet.alice@pexample.com?pin=1234&muteMicrophone=true

Links to a join instructions page

You can generate a URL to a webpage on a Conferencing Node where the full set of join instructions for a specific VMR is shown. These join instructions can optionally include a QR code, which when scanned by a device with a supported Connect app installed (such as Pexip Connect for RealWear or the Connect mobile app) will open the meeting directly in the app.

The format of the link is described below.

Formatting the URL

The URL takes the format:

https://<node_address>/teams/join.html?conf=<alias>&d=<domain>&test=<test_call_alias>&w&qrcode

where <node_address> is an FQDN that resolves to your Pexip Conferencing Nodes (it can also be the FQDN or IP address of an individual Conferencing Node). Note that:

  • To view this webpage, the client application used to view the invitation must be able to access the specified Conferencing Nodes (or alternative server) on HTTPS 443/TCP.
  • You must ensure that the FQDN used here is resolvable by any internal or external client applications that may be used to view the invitation i.e. that they can access the webpage on the nodes referenced by the FQDN. This means that if these nodes have private addresses, then depending on your internal network routing, you may need appropriate local DNS resolution for the <node_address> FQDN for internally-based clients, in addition to external DNS resolution for that FQDN for externally-based clients.

The other parameters are:

Parameter Mandatory Description
conf Yes An alias that can be used to join the meeting.
d Yes The domain name of your Pexip Infinity platform e.g. pexample.com. This is used as the domain for all of the URI-style addresses that are displayed on the webpage.
test No

Includes a "Test call" option on the webpage, where the value of this parameter is the name part of the alias to dial e.g. test_call. Do not include the domain — this is the d parameter above.

This uses Pexip Infinity's inbuilt Test Call Service; therefore you must ensure that <test@d>, e.g. test_call@pexample.com, matches the name of the alias configured in Pexip Infinity for the test call service.
w No

Displays the "From a browser" access details on the webpage.

There is no value associated with this parameter.
qrcode No

Includes a QR code on the webpage, which when scanned by a device with a supported Connect app installed (such as Pexip Connect for RealWear or one of the Connect mobile apps) will open the meeting directly in that app.

There is no value associated with this parameter.

An example URL value could be: https://px.vc.pexample.com/teams/join.html?conf=meet.alice&d=pexample.com&test=test_call&w&qrcode

and that would produce the following webpage:

Alternate VTC dialing instructions page

Links to the legacy Connect apps

For information on creating links to legacy clients, see the v17 documentation.