Creating preconfigured links to conferences via Infinity Connect

Links to Infinity Connect Web App

You can provide conference participants with a URL that, when clicked, will open an instance of Infinity Connect in their default browser. You can format the URL with query string parameters so that it pre-fills some or all of the required fields and allows the participant to review these before joining, or you can format the URL so the participant is taken straight into the conference.

The URL is in the format:

https://<address>/webapp/?conference=<alias>&name=<name>&bw=<bandwidth>&pin=<PIN>&join=<join>&role=<role>&media=<media>&audioonly=<audioonly>&escalate=<escalate>&extension=<extension>

where:

• <address> is the IP address or domain name of the Conferencing Node or reverse proxy
• <alias> is one of the aliases for the Virtual Meeting Room or Virtual Auditorium the user will join
• <name> is the name of the user who is joining the conference
• <bandwidth> is the bandwidth in kbps, and can be any number between 256 and 1864
• <PIN> is either the Host or Guest PIN, if required
• <join> is 1 if you want the participant to automatically join the conference, otherwise it is not present
• <role> is either host or guest and is used when the URL does not contain a PIN (for example, to allow Guests to automatically join a conference that has no Guest PIN). However, if the URL already specifies a <PIN>, the PIN will determine the participant's role and the <role> will be ignored.
• <media> is 1 if you want to start your camera and microphone immediately after joining, or is left empty if you want to join in presentation and control mode.
• <audioonly> is 1 if you want to start an audio-only call.
• <escalate> is 1 if you want users to be offered the camera and microphone selection options immediately upon joining (only applies when the option to start media immediately has not been activated, i.e. in conjunction with media=.
• <extension> is the Virtual Reception extension, or the Lync / Skype for Business Conference ID.
• <forceguest> is 1 if you want to withhold Host-level controls (such as muting all guests) even if the participant joins as a Host.

The URL must always include https://<address>/webapp/?; the remainder of the fields are optional, as follows:

• If a field is not specified in the URL but is required when joining (i.e. alias, name, PIN if the conference uses PINs, or extension if one is requested), the participant will be required to provide the information themselves before they can join the conference.
• If the bandwidth is not specified in the URL and the participant has not previously selected a different value, the default of 576 will be used.

Examples

• If the domain name of your reverse proxy is conference.example.com, and there is a Virtual Meeting Room with the alias meet.alice, which has no PIN, the URL for Bob to join it directly would be:

  https://conference.example.com/webapp/?conference=meet.alice&name=Bob&join=1

• If we then gave the same Virtual Meeting Room a Host PIN of 1234 but no Guest PIN, the URL for Bob to join it directly as a Host would be:

  https://conference.example.com/webapp/?conference=meet.alice&name=Bob&pin=1234&join=1

  and the URL for Bob to join it directly as a guest would be:

  https://conference.example.com/webapp/?conference=meet.alice&name=Bob&join=1&role=guest

  and the URL for Bob to join it directly as an audio-only guest would be:

  https://conference.example.com/webapp/?conference=meet.alice&name=Bob&join=1&role=guest&media=1&audioonly=1

• If we wanted Bob to join directly as a guest with audio and video, but allow him to select and check his camera and microphone prior to joining, the URL would be:

  https://conference.example.com/webapp/?conference=meet.alice&name=Bob&join=1&role=guest&media=&escalate=1