Name: sample-provisioning
Owner: Vivocha
Description: null
Created: 2016-09-27 16:27:07.0
Updated: 2016-09-27 16:30:27.0
Pushed: 2016-09-27 18:02:54.0
Homepage: null
Size: 2
Language: JavaScript
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
This sample shows how to use the on-behalf-of login API to do the provisioning of the agents on Vivocha. See more on: On-behalf-of login
t clone [git-repo-url] sample-provisioning
sample-provisioning
m install
And then you can add/edit the users in the users.js module.
| Parameter | Required | Description | | ———- |:——–:| ———– | | id | YES | Agent user id on behalf of we want to login (if the agent does not exists in our database it will be created otherwise it will be updated) | | keep | NO | Keeps the values on the Vivocha database instead of the values (this value is ignored for the password property that is always updated) | | media | NO | Media allowed for the agent (chat,voip,video) | | nickname | NO | Nickname | | firstname | NO | First name | | surname | NO | Last name | | email | NO | Email | | tags | NO | Agent tags separated by commas (i.e. “tag1,tag2,tagx”), the tags are used to limit the service availability to the agents with the same set of tags | | password | NO | Agent password | | logout | NO | Url in which the agent will be redirected after the logout |
Example:
le.exports = [{
: "agent1",
dia: "chat",
ckname: "AgentOne",
rstname: "Name",
rname: "Surname",
ail: "agent1@example.com",
lang: "en",
gs: "one,two"
ovisioning -a <accountid> -u <userid> -p <password>
For a list of all available options run provisioning -h:
provisioning -h
age: provisioning [options]
tions:
-h, --help output usage information
-V, --version output the version number
-a, --account <account> Vivocha account
-u, --user <user> Vivocha user (must be an admin user)
-p, --password <password> Vivocha user password