Skip to main content
Skip table of contents

How to provision a Yealink device using RPS


Yealink is one of the supported phones with Xelion. To be able to use these phone you need to provision them. This article will describe how to do this.


  • An active Xelion license;

  • A Yealink device;

  • An administrator account on your Xelion tenant.

Getting Started

This article is divided in 3 parts. The first part will explain how you can add a tenant to your/our RPS server. The second part will explain how to add Yealink device(s) to the configured RPS server. The third part will explain how you can configure settings on the Yealink device(s).

Adding a tenant to your/our Yealink RPS server.

  1. Go to Beheer → Provisioning → Provisioning instellingen → Yealink

  2. Fill in the credentials from your own Yealink RPS server. If you don’t have a Yealink RPS server ours can be used. Please contact support if you wish to use our Yealink RPS server.

  3. Type the name of the customer you wish to add to the Yealink RPS server. Please note this must be unique. If the name is already taken it will give you an error. ERROR: The server name has been used.

  4. Type the URL from the provisioning server you would like to use. This always should be the the URL from the Xelion server the tenant this is hosted on. Example:
    Note: Please change 02 to 03 if the tenant is active on the XEL03 environment.

Adding phones to the RPS server

  1. Go to Beheer → Telefoontoestellen → Nieuwe telefoon

  2. Fill in the following fields in the Algemeen tab

    1. Label = This is to recognize the name of the device

    2. Gebruikersnaam = Username of the device. Please note that “tenantID_” always will be added in front of the username.

    3. Gebruiker = Select a user this device should be added to.

  3. Fill in the following fields in the Provisioning tab

    1. Accountnaam = Name to recognize the provisioning device. This could be T46G Ben for example

    2. Displayname = Name to be displayed on the phone

  4. Click the account name to get redirected to the provisioning details.

  5. Fill in the MAC address from the device you wish to provision.

  6. Use the drop-down menu under Toesteltype to select the exact same model from the phone

  7. Check the Provisioning actief and the Gebruik redirection server checkbox.
    Note: Only check the Gebruik redirection server checkbox after you have filled in all the other fields.

  8. Factory reset the device

Configuring the device

  1. Go to Beheer → Telefoontoestellen and click the label of the device you wish to edit.

  2. Go to the Provisioning tab and click the account name

  3. Use the Extra provisioning opties and Functietoetsen fields to setup additional provisioning options

    1. Key index: Defines the order of the keys.

    2. Key type: Defines what kind of key.
      linkekey (key on default phone screen)
      expansionkey (key on an expansion from the phone)

    3. Type: Defines the type of function. See the table below for more information.
      BLF (Busy Lamp Field). Used to see the status from a device
      Speeddial (Shortcut). Used to quickly dial a user of number
      Account (Account). Used to change account defined in the ‘account’ tab.
      Nightmode (Nachstand) Used to activate nightmode for a certain callflow (aansluiting)

    4. Label: Defines the displayed text in the screen of the phone

    5. Waarde: Defines the value. This doesn’t use a drop-down menu.

    6. Toestel (BLF): Defines the device. This shows all the devices

    7. Aansluiting (BLF): Defines the callflow. This shows all the callflow

  4. Click Acties → Synchroniseer config voor dit toestel to activate the changes.

Table of types and functions

Note: Not all types support all fields. Please use below table to see what fields can be used.



Toestel (BLF)

Aansluiting (BLF)


✅ Device

✅ Callflow


✅ External number

✅ Device


✅ Account number


✅ Speeddial number

✅ Monitors the status

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.