After having installed the EasyConnect app, there’s still some configuration required.
If you plan on using the RCC API, Contacts API or webhooks, the first configuration step is the creation of a group using PBX Manager. All users that should be monitored, i.e. for whom you want to receive webhook events, should be a part of this group. Also, all users for whom you would like to use the RCC API need to be a part of this group. By making the EasyConnect app an active member of the group, we are able to monitor users and initiate calls.
Next, we have to configure the EasyConnect app. The EasyConnect configuration page consists of three sections: Webhook Configuration, API keys Configuration, and License information. The Webhook Configuration allows for the configuration of a webhook. The webhook will be used by EasyConnect to send events using the GET or POST HTTP method. The API keys Configuration allows you to configure the API keys required to authorize requests made to the EasyConnect APIs. The License information section allows you to upload your EasyConnect license and displays license information per API.
The EasyConnect group is required for webhooks and the RCC API to function. We create one via the PBX Manager and then we make the EasyConnect app an active member of this group.
To make the EasyConnect group, follow these steps:
Next, we add the EasyConnect app as an active member to this group.
This needs to be done manually via the PBX Admin-UI.
Before making any changes in the PBX Admin-UI via the Devices app, make sure you have closed the PBX Manager app.
To add the EasyConnect app as an active member of the group, follow these steps:
The EasyConnect app is now ready to monitor and make calls for any user that’s a member of the EasyConnect group.
The webhook allows the EasyConnect app to send events on monitored calls to your low-code solution or a REST API of your own making.
To configure the webhook, follow these steps:
You have now configured a webhook to be used for sending events of monitored calls to.
To make full advantage of EasyConnect’s Contacts API, we need to make sure EasyConnect has access with admin rights to the Contacts Directories for which you want to make Contact API requests. Any contact in innovaphone requires a link to a contacts directory.
Make sure you have created a group with the EasyConnect app as an active member (see “EasyConnect Group” above).
To grant EasyConnect access to a Contacts Directory, follow these steps:
The Contacts Directory can now be accessed through the Contacts API provided by EasyConnect. To learn more about the Contacts API, please have a look at the documentation provided in the EasyConnect app (see “REST APIs Documentation” on page Developing with EasyConnect).
The EasyConnect app’s APIs use an API key to authorize requests. After installation, we recommend changing the API keys. You can enter a custom value for your API key, or you can have a random string generated for you using the refresh button to the right of the API key form field.
To configure the API keys, follow these steps:
You have now configured the API keys to be used to authorize requests made to the EasyConnect APIs.
To use the EasyConnect app, a license is required. You can apply for this licence at info@xqting.be.
To upload your license, follow these steps:
You have now licensed your EasyConnect app and can start using the EasyConnect app as an integration with your low-code application or start implementing the EasyConnect REST APIs in your own apps (see “Developing with EasyConnect”).
The EasyConnect application needs to connect to a couple of innovaphone applications for it to function properly.
The required apps are: Contacts, Users Admin and Devices
If the hardware IDs for these applications are altered and thus not the default names given by innovaphone, you’ll need to specify the name of these applications as a key-value pair in the ‘config’ table of the EasyConnect application.
Important, the app needs to be restarted when changes are made to the config table.
Overview of inno apps' default hardware IDs and associated key:
App | Key | Default Value |
---|---|---|
Contacts | apps.contacts | contacts-admin |
Users Admin | apps.usersAdmin | users-admin |
Devices | apps.devices | devices-api |