You are here: Infinity Connect > Installing and using Infinity Connect > Registering your client to receive calls

Registering your Infinity Connect client to receive calls

To receive calls on an Infinity Connect desktop client or Infinity Connect Mobile client for Android, it must be registered to a Pexip Infinity Conferencing Node.

Devices can only register to Pexip Infinity with a permitted alias and by supplying valid credentials (if authentication is required). Allowed aliases and their associated credentials can be configured manually, or they can be bulk provisioned from directory information contained in a Windows Active Directory LDAP server, or any other LDAP-accessible database (see Provisioning VMRs and devices from Active Directory via LDAP).

When an Infinity Connect client is registered, as well as being able to receive calls, the user can filter and lookup the contact details (phone book / directory) of other devices or VMRs that are set up on the Pexip Infinity platform, making it easier to call those devices or VMRs. For more information, see Directory (phone book) of devices and VMRs for registered Infinity Connect clients.

Note that you can also register SIP or H.323 endpoints to Pexip Infinity. They will be able to receive calls but will not be able to display phone book contact details of other registered devices.

Registration is optional. You do not need to register your device in order to make calls, just to receive them.

How to manually register your client

To register your Infinity Connect desktop client or Infinity Connect Mobile client for Android to receive calls (if this is supported in your deployment):

Go to the Settings screen (from the top right of the Infinity Connect home screen, select Settings ).
In the Registration section of the Settings screen, enter the Alias and Password provided to you by your administrator. Be aware that these fields are case-sensitive, and some devices will default to uppercase for the first character of the user name.
Select Remember password.
Select Register.

When you have successfully registered, the button will change to Unregister.

The notification icon for Infinity Connect will also have a green dot on it: . This dot will change to red if you become unregistered: .

Now, when someone calls your endpoint by dialing the Alias you have registered with, you will get an incoming call alert at the bottom right of your screen showing the name and address of the person or meeting room who is calling you:

For the Infinity Connect desktop client, you can disable the sound of the incoming call alert by going to Settings and selecting a Ringtone of None.

If you are registered, you can filter and lookup the contact details of other devices or VMRs that are set up on your Pexip Infinity platform, by typing in part of the address of the person or the name of the VMR you want to call.

Provisioning the Infinity Connect desktop and Android clients with registration details

As an administrator, you can provision individual users with their registration details and automatically apply those registration settings to their Infinity Connect desktop client or their Infinity Connect Mobile client for Android.

When the Infinity Connect client installs, it registers itself to the pexip-provision:// URI scheme. This means that you can then generate an individual URI that can be used to configure the client with personalized settings for each user.

The URI takes the same form for the desktop and Android clients, with the exception that the Desktop client uses Base64 encoding for the data blob. So the format is:

Desktop client:

pexip-provision://settings/?data=<Base64 encoded name-value pairs>

where data is set to a string of name-value pairs that has been Base64 encoded (to ensure that the data does not get modified by email clients). Note that the Base64 provisioning data blob is not encrypted.

Android client:

pexip-provision://settings/?data=<name-value pairs>

If you use Pexip Infinity to bulk provision device aliases and generate emails to each user (see Provisioning VMRs and devices from Active Directory via LDAP), you can use the provided template variables and custom Pexip filters to obtain the values for each data item and to generate the relevant URIs for each user/client.

The name-value pairs that can be provisioned and the suggested device provisioning template variables that can be used to populate those value are:

Name	Value	Suggested template variable
name	The name of the user as it will appear to other conference participants.	device_username
registrationHost	The address of the Conferencing Node at which the client should register, for example confnode.example.com.	There is no suitable variable for this, as it is not a user specific value.
registrationAlias	The alias of the device to register to Pexip Infinity.	device_alias
registrationUsername	The username associated with the device alias (registrationAlias).	device_username
registrationPassword	The password associated with the device alias (registrationAlias).	device_password

You do not have to provision every name-value pair. If you supply a subset of the data, the user will be able to manually enter the additional data if required.

Example device email template content

The following example content for a device provisioning email template shows how you can build the relevant URI with base64 encoded provisioning data (using device provisioning variables populated from LDAP) and provide a clickable link for the recipient of the email that will provision their client.

{%set provisiondata = "name=" + device_username|capitalize + "&registrationHost=confnode.example.com&registrationAlias=" + device_alias + "&registrationUsername=" + device_username + "&registrationPassword=" + device_password %}

<p>You can open <a href="pexip-provision://settings?data={{provisiondata|pex_base64}}"> this link</a> to automatically configure your client.</p>

The generated URI for "this link" will take the form pexip-provision://settings?data=bmFtZT1...etc...HVhcA==

User experience

When the end user clicks on the link, they will typically be asked that they want to confirm or authorize the launch of the Infinity Connect application (the exact nature of the request varies according to the platform and the method of launching the link) and then the Infinity Connect client will launch automatically and present the user with a Provisioning screen, containing their personalized configuration, for example:


Infinity Connect desktop client	Infinity Connect Mobile client for Android

Clicking Apply or OK will accept the settings and attempt to register the client to the specified server address, using the alias and user name / password credentials.

Note that some mail clients (such as gmail) disable embedded links. In these cases, those users will need to either cut and paste the link into their browser's address bar (either Internet Explorer, Microsoft Edge, Firefox or Safari, but not Chrome or Opera), or Windows users can also press [windows]+R and then paste the link into the Open field. Other mail clients (such as Outlook) may present users with a security notice warning that the hyperlink may be unsafe; users must chose to continue in order to launch the application.