Users and participant avatars
You can configure user records to represent those participants/contacts and associate each user with an avatar URL that points to an external service (such as Gravatar) which can be used to retrieve that user's avatar/image.
User records can be created manually (Pexip's provisioning mechanism ( ). You must also set up and enable an Avatar policy ( ).), or they can be generated from directory information contained in an AD/LDAP server via
When viewing participants' avatars within a conference:
- For a participant's avatar to be requested and available for display, that participant's device must be registered to Pexip Infinity (any device type or protocol).
- If the participant joins as audio-only, their avatar is displayed to all of the video participants in the conference.
- Infinity Connect client users can see a participant's avatar via the participant list tab in the side panel and using the option.
When configuring end users and their associated avatars, there are two main attributes of each user record to consider:
- Email address: the user's Email address is used as the primary identifier of each user record. When attempting to retrieve a user's avatar, the system locates the relevant user record (and thus the user's avatar URL) by finding the user Email address that matches the Owner's email address associated with the device alias of the conference participant. We recommend using LDAP sync templates to provision the device and user records as this will ensure that a matching email address is used.
Avatar URL: this is the link to where the avatar can be requested:
- The avatar URL must be an unprotected resource (username and password credentials cannot be supplied with the request), and it must be reachable from Conferencing Nodes.
- The image retrieved from the avatar URL must be a JPEG.
- When a Conferencing Node sends an image request to the avatar URL, Pexip Infinity adds on extra URL parameters that specify the required dimensions, for example ?width=100&height=100&s=100 (the s is a size parameter used by Gravatar). Pexip Infinity only ever requests square images.
All JPEG images must use the RGB or RGBA color space (CMYK is not supported), and be of the requested size (width, height).
The following example diagram shows the relationship between participant aliases, device aliases and user records when obtaining an avatar URL:
To configure user records and avatar URLs:
- Set up a policy profile with local avatar configuration enabled:
- Go to and create a profile (or modify an existing profile).
- In the Avatar policy section, enable Use local avatar configuration.
- Save the policy profile.
- Assign the policy profile to your locations ( ).
- Configure user records and their associated avatar URLs:
Note that other user attributes can also be configured (such as names and contact numbers) but these are not currently used within Pexip Infinity.
To manually configure the user records, go to. The full set of options are:
|Email address||The email address of the user.|
|Description||The description of the user.|
|First name||The first name of the user.|
|Last name||The last name of the user.|
The display name of the user.
Note that the display name is not currently used in Pexip Infinity (for example, it does not affect participant name overlays and cannot be used when provisioning Infinity Connect clients).
|Telephone number||The telephone number of the user.|
|Mobile number||The mobile number of the user.|
|Title||The job title of the user.|
|Department||The department of the user.|
|Avatar URL||The avatar URL of the user.|
The unique identifier (UUID) of the user.
This field is required and must be unique for each user and must be in a UUID format. Therefore it is strongly recommended to use the generated default value.
|Exchange mailbox UUID||The unique identifier of the user's Exchange Mailbox. This field is not required but if included it must be in a UUID format and be unique for each user.|
|User origin||The name of the LDAP sync template used to create this user (it is blank if the user was created by manual input or via the API). This field is read-only.|