Instant WebAgent¶
WebAgent provides a full-featured softphone inside your browser. Leverage cutting edge web technologies, such as WebRTC, we are to provide impeccable voice quality and native-like user experience.
Installation¶
Server Installation¶
Note
You will need to have a strong technical knowledge in Linux system administration to follow these steps. Consider contaction our tech support team for help.
Setting up the WebRTC gateway¶
We will start from a fresh InstantVoice install, configure it as a WebRTC Gateway and replace all the needed software for it to work correctly. All configuration in this section will be done in localadmin.
Local/Database¶
Configure the database to point to your ACD or STANDALONE brick.
Local/Install Type¶
Set your brick type as a WebRTC Gateway.
Local/Licenses¶
The WebAgent module requires a specific, per channel, license. Activate your license code in this page before proceeding.
Configuring your ACD to work with the gateway¶
In your ACD’s localadmin interface, go to Local/Extensions and enable the WebAgent extension.
Now in your installation’s admin interface, go to Integration/WebAgent. The following parameters need to be correctly configured.
General
Field |
Description |
|---|---|
Integration Key |
Choose which key to use for the WebAgent to request information from the platform. |
Template |
Select the template to be used by the agents. |
Contact Button
Field |
Description |
|---|---|
SIP Peer |
Choose which SIP Peer should the gateway register to sendo inbound calls through. |
Destination Equipment |
Choose which brick should receive the contact button calls. This dropdown will list your Media Server in case of a distribute setup or your Standalone brick. |
Destination SLN |
This is the list of SLNs your WebRTC contact button will be allowed to reach. |
IVStomp
Field |
Description |
|---|---|
Address |
This will usually be the ip address or hostname of your active ACD. |
Port |
If you modified the web service’s port as described in the `Server Configuration`_, inform the same port here. |
Username |
The username to be used to connect to the STOMP message broker. |
Password |
The password to be used to connect to the STOMP message broker. |
IVWS
Field |
Description |
|---|---|
Address |
This will usually be the ip address or hostname of your active ACD. |
Port |
This is the port where IVWS is listening to requests. Most likely you will not need to change this. |
IVACD
Field |
Description |
|---|---|
Address |
This will usually be the ip address or hostname of your active ACD. |
Note
Make sure this is set to something all servers can resolve. This is particularly important in STANDALONE installations since this value will be localhost by default.
STAFF
Field |
Description |
|---|---|
Administrators |
Select here which agents will have access to WebAgent’s administration panel. |
Administration Interface¶
Accessible through http://<acd_hostname>/agents/admin, this is were you can configure the column layouts for the agent’s page. You can choose between a 1, 2 or 3 column layout and place any of the available modules on any of the columns. Simply defining the number of the desired column, or 0 to hide the module.
Installing all WebRTC GW extra software¶
Now connect to a terminal in the WebRTC Gateway and, as superuser, run the command:
python26 <(curl -s http://isos.instantvoice.net/rtc_installer)
Example Agent setup¶
First we create a SIP Extension of Type WebRTC. Define an extension and user (preferrably the same) and a password. Set Phone Type to WebRTC and leave everything else as default.
Now pick the agent you want to turn into a WebAgent and set the field Preferred Interface for the SIP extension create above. And now you can log into http://<acd_hostname>/agents with your regular agent and password.