Reference13r3:Concept Conference Meeting Invitations

Applies To

• innovaphone PBX from version 13r3

Overview

Conference meeting invitations is a new feature of the Conference Object. Meeting invitations are used to create temporary conference rooms.

Requirements

• CONF or SCNF interface with appropriate channel licensing
• Conference App license (App(innovaphone-pbx-conference)13), necessary to create meeting links and invitations.
• If announcements should be played, announcement files must be available. The file names are listed here.

Configuration

The configuration of the conference object remains as described in this wiki article.

In addition, two new options have been introduced:

Web Access allowed

Needs to be enabled to use the temporary meeting links

International Number

Needs to be set to add a phone number in the meeting invitations.

Features

The conference web access features are available.

• Dial-in with web access link
• Dial-in with a SIP uri.
• Dial-in with a number and an additional meeting id if this id is not used several times and the meeting room is created.

Usage

The conference doesn't save meeting links and so, it doesn't reserve any conference channel for them. The conference reserves channels if a meeting link is used and a meeting room is created.

Creating Meetings

A meeting is defined by a meeting id, the start and end of the date and time and the number of participants. The number of participants specifies how many channels will be allocated for this meeting.

A meeting HTTP link and a SIP uri can be generated in the conference app by clicking the invitation button, create link, which can be directly sent to participants via email. If the mail link button is used, a mail-to link is generated and opened, so the operation system opens an email client with a prefilled message subject and body.

In addition, a meeting can be scheduled. A calendar file (ICS) is created by clicking the open calendar button. It depends on the current browser configuration if the calendar file is saved to the client system or opened with a supported application.

The generated HTTP link can be used to take part in the meeting with a browser, the generated SIP uri can be used with a phone app, internal or with federation.

It is also possible to take part in the meeting with a dial-in number. The room number must be dialed followed by the meeting id with DTMF. This is possible not before someone else has used the HTTP link or the SIP uri.

Joining Meetings

A meeting link can be used between one hour before the defined starting time and the defined end time, or if the meeting is being on. If you call the meeting room one hour till five minutes before the meeting starts, a predefined announcement is played. No room is created and no conference channels are reserved at this time.

If you call or have a call to the meeting room five minutes or less before the meeting starts, a room is created, channels are reserved and the meeting room is listed in the conference app. The conference reserves as many channels as previously defined as number of participants. If not enough channels are available, the caller is announced and the call is disconnected.

Moderating Meetings

All current meetings of a room can be listed in the corresponding conference room app. If a meeting is chosen, the participants of this meeting room are shown. A meeting room only appears five minutes before the meeting starts.

Data Content

The base64 encoded data of the HTTP link or SIP uri includes following content:

• the version number, currently 0, 1 byte
• flags for optional content, currently 0, 1 byte
• the room number, 4 bytes
• the room number length, 1 byte
• start timestamp, 4 bytes
• end timestamp, 4 bytes
• number of reservations, 2 bytes
• creation timestamp, not used for the hash calculation, 4 bytes
• MD5 hash, 16 bytes

The hash is calculated with the content above followed by the meeting password of the conference room ("m-key" in the configuration).

Note that the '+' are replaced with '-' and the '/' with '_' after base64-encoded to be URL-compatible.

Troubleshooting

The same as for conference web access.