Quobis wac settings to deploy Quobis collaborator

Related capabilities

Quobis collaborator runs on top of Quobis wac and uses its SDKs. Some of the behaviors of Quobis collaborator are tied to the capabilities configuration on the Quobis wac side.

Note

A capability is an specific modifier assigned to a user, domain or group that affect the behavior of the users and the exposed features of the system. Aside the configuration, the capabilities are also modified by the functional services running on the Quobis WAC.

These are the Quobis WAC capabilities that have impact on the Quobis collaborator behavior. For a complete description of each capability and how to configure them, please refer to the document Quobis wac administration guide.

This is the complete list of capabilities in alphabetical order:

alert-messages

When active, the “alert” section is shown and users are able to see, answer and send alert messages.

attended-transfer

Allows to transfer an on hold call to an already active call. To allow a user to make attended transfers, it is also required that the user includes the capability make-calls.

audio-call

When active, audio call button will be shown in the contact button. It is also required that the user includes the capability make-calls.

audio-video-call

When active, video call button will be shown in the contact button bar.

blind-transfer

Allows to transfer a call to a new destination without communicating with the new destination before. To allow a user to make attended transfers, it is also required that the user includes the capability make-calls.

call-from-chat

When active, allows to start calls from the chat window.

call-history

When active, call history tab is shown in drawer.

caller-extra-info

When active, the user will be able to see the contextual information on a call.

change-camera

Allows to change the camera being used inside a call.

chat

When active, the chat panel is shown, otherwise remains invisible.

contacts

When active, contact tab is shown in drawer.

create-contacts

When active, the user can create contacts to his contact list.

force-video-only-call

When active, video call button creates a call without sound.

forms

When active, forms button is shown in the chat toolbar.

hide-incoming-domain

When active, the phones which have the form ‘xxx@yyy’ will be replaced by ‘xxx’.

hold

When active, hold button will be shown in the active call view.

make-calls

When active, the user is able to create calls and request another user or external participant to join a conference. This capability also allows to display the buttons to make calls on the collaborator. It is mandatory to allow users to make transfers (attended or blind).

meetings

When active, meetings tab is shown in drawer.

presence-avatar-set

Allows to change the avatar.

screen-sharing

When active, screen-sharing button will be shown in the active call

start-chat

When active, users are able to start a chat. Otherwise, users can only answer to chat addressed to them. Available only on iOS app.

user-group

When active, group tab is shown in drawer.

user-select-group

Allows to select a group/subgroup.

video-call

When active, video call button will be shown in the contact button bar.

whiteboard

When active, a whiteboard button will be shown in the active call view.

Please note that, in order to active some configurations, more than one capability need to be active. For example, if none of the following capabilities are present, the dialpad tab will be hidden in the drawer:

• audio-call

• video-call

• audio-video-call

In the same way, if none of the following capabilities are present, the drawer will be hidden:

• chat

• contacts

• audio-call

• video-call

• audio-video-call

• call-history

• meetings

Regarding video calls, if none of the following capabilities are present, video calls can not be made:

• video-call

• audio-video-call

Aliases and personal URL configuration

A user’s “personal URL” is automatically composed of the base system URL (eg, https://collaborator.company.com) followed by the user alias, given as a result a pattern like:

https://collaborator.company.com/alias

Users are allowed to change their alias through the application in the “Profile section”, as long as the new alias does not conflict with other alias in the system.

On the other hand, even when the users can create new alias, there is another “Personal URL” that always works, cannot be changed and which is composed of the base URL followed by the username.

https://collaborator.company.com/username

Note

Depending on the type of user accessing the endpoint the system resolves the URL differently:

• If the user is logged in it will resolve it on the user’s domain

• For an anonymous user the default domain is used

• To call an specific user@domain, you’ll need to include both parameters. I.e.

https://collaborator.company.com/username@domain

When a user is created, if the system administrator does not provide an alias, then, the Quobis WAC will provide one according to the alias parameter as configured in the [user] section of wac.ini:

• When alias is set to true, then Quobis WAC copies the username into the alias field.

• When alias is set to false, then Quobis WAC copies the user’s UID into the alias field.

There is also another parameter in the same user configuration section that allows to create a blacklist of forbidden aliases. In summary, Quobis WAC will not allow to set aliases that:

• Conflict with another UUID

• Conflict with another username

• Conflict with another alias

• Belong to the alias blacklist

Example shown below of the wac.ini users section:

[users]
alias = true
forbiddenKeyWords = 'login,index'

Please note that the “personal URL” feature cannot be deactivated. A workaround to avoid unwanted calls that the end-user himself can do is to set the Personal URL to a long random string, so a potential attacker cannot guess it. Another way to deactivate this feature to every user is to block those specific URLs in the sippoas.reverse-proxy service.

On the other hand, please note that the “Personal URL” max string size on the application is set by the variable PROFILE_LINK_MAX_LENGTH at the conf.js file and defaults to 90 characters.

Phonebook system

The Quobis collaborator leverages the phonebook functionality of Quobis WAC in order to show contacts to specific user or group of users. If you want to use phonebooks in your deployment, please refer to the phonebook configuration

Simultaneous call support

In order to support or limit the multi-call support you can modify the QSS configuration to allow or reject calls when you are already on a call. This could be useful for some scenarios or for license limitation configuration for your customers. This limitation can be configured as explained here