Vicidial With WebRTC

VICIDial is well known open source call center software. It has been in use by many small to large scaled contact centers for their business for many years. There are many evolutions made by the VoIP developers to improve the functional and operational module of VICIDial with the VICIDial customization services. One of the latest and in trend innovation in this field is integration of WebRTC and VICIDial. The WebRTC provides a communication tool to exchange voice, video and/or data in real time using a web browser. The integration of VICIDial and WebRTC has empowered many contact centers. How? Let’s unveil.

The WebRTC solution which is also known as WebRTC client or WebRTC based phone or WebRTC Phone works directly from a web browser and as it is integrated with the VICIDial solution, the agents can utilize both, WebRTC and VICIDial in a streamlined manner.

Top 3 benefits of WebRTC and VICIDial Solution Integration:

No IP Phones required for calling

In the contact center, one of the options agents use is IP Phones for inbound and outbound calling. The integration of WebRTC solution with VICIdial will eliminate the need of IP Phones. This would save capital and maintenance cost.

No Softphone required

The integration of WebRTC with VICIDial solution eliminates need of any softphone. This will save a lot of time from installing and configuring a softphone. Neither agent nor the server administrator need to configure different codecs, SIP accounts, natting ,etc. With the stated integration, agent just needs to open the web based WebRTC solution and start calling using it, no installation or configuration required at all.

All Calling features available remotely

The WebRTC phone can be accessed from anywhere with the valid credential using the WebRTC compatible web browsers. This is like plug and play, in fact, easier than that. The WebRTC phone will have all required calling features for an agent such as:

Conference call

Music on hold

Call transfer

Call mute/ unmute

And more

Now, agents can work from any system and if you support remote work model this model work amazingly well. Your agents can work remotely from anywhere without any concern of hardware or software installation and configuration because the WebRTC and VICIDial solution integration made all communication simpler and in real time by blending two advanced tools, WebRTC and VICIDial, with each other.

We, Wired To Technologies, has benefited our many customers belong to call center, customer care and customer support center industry with this solution. Would you like to know more, how can it benefit you? Contact Us NOW!

Call on 963 741 5650

Kamailio Quick Install Guide for v4.4.x – CentOS 7

This article will provide step-by-step instructions on how to install Kamailio 4.4.x on CentOS 7 using yum packages.

Setup YUM Repository

Install wget so we can pull down the rpm.
```
yum install wget
```

Let’s download the yum repo file for our CentOS version and update the system so yum is aware of the new repository.

cd /etc/yum.repos.d/
wget http://download.opensuse.org/repositories/home:/kamailio:/v4.4.x-rpms/CentOS_7/home:kamailio:v4.4.x-rpms.repo

Update system so yum is aware of the new repository.
```
yum update
```
You can look at the kamailio packages in the YUM repository by typing:
```
yum search kam
```

Install Kamailio and Required Database Modules

Install the following packages from the new repo.

yum install -y kamailio kamailio-mysql kamailio-debuginfo kamailio-unixodbc kamailio-utils gdb

Set kamailio to start at boot.
```
chkconfig kamailio on
```

The Kamailio configuration files will be owned by the root user, rather than the kamailio user created by the Kamailio package. We will need to change the ownership of these files.

chown -R kamailio:kamailio /var/run/kamailio
chown kamailio:kamailio /etc/default/kamailio
chown -R kamailio:kamailio /etc/kamailio/
echo "d /run/kamailio 0750 kamailio kamailio" > /etc/tmpfiles.d/kamailio.conf

Install MySQL

Since we plan on using MySQL, we will need to install the MySQL server as well as the client.
```
yum install -y mariadb-server mariadb
```
Next we need to start up MySQL:
```
systemctl start mariadb 
```
And enable mysqld at boot.
```
systemctl enable mariadb
```
Now we can set a root password for mysql:

You can hit yes to all the options. There is no root password as of yet, so the first question will be blank. Be sure to use a secure unique password for your root user.

[root@localhost yum.repos.d]# /usr/bin/mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MySQL to secure it, we'll need the current
password for the root user.  If you've just installed MySQL, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none):
OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MySQL
root user without the proper authorisation.

Set root password? [Y/n] Y
New password: (enter password)
Re-enter new password: (enter password)
Password updated successfully!
Reloading privilege tables..
 ... Success!


By default, a MySQL installation has an anonymous user, allowing anyone
to log into MySQL without having to have a user account created for
them.  This is intended only for testing, and to make the installation
go a bit smoother.  You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n] Y
 ... Success!

Normally, root should only be allowed to connect from 'localhost'.  This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n] Y
 ... Success!

By default, MySQL comes with a database named 'test' that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n] Y
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n] Y
 ... Success!

Cleaning up...

All done!  If you've completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!

Configure Kamailio to use MySQL

By default, Kamailio does not use MySQL. To change this we need to edit one of Kamailio’s configuration files.

vi /etc/kamailio/kamctlrc

Uncomment the DBENGINE parameter by removing the pound symbol and make sure the value equals MYSQL. The parameter should look like this afterwards:
```
DBENGINE=MYSQL
```

To have the kamdbctl command create the mysql database with the correct permissions, we will want to set the databaseusers and passwords in kamctlrc

## database read/write user
DBRWUSER="kamailio"

## password for database read/write user
DBRWPW="kamailiorw"

## database read only user
DBROUSER="kamailioro"

## password for database read only user
DBROPW="kamailioro"

Create the Kamailio Database Schema

The Command will create all the users and tables needed by Kamailio. You will be prompted to put in the MySQL root password that you created in the Install MySQL section of this document. You will be asked if you want to install different tables – just say “yes” to all the questions.
```
/usr/sbin/kamdbctl create
```

Below are all the prompts you will be presented:

MySQL password for root: ''
Install presence related tables? (y/n): y
Install tables for imc cpl siptrace domainpolicy carrierroute userblacklist htable purple uac pipelimit mtree sca mohqueue rtpproxy?
(y/n): y
Install tables for uid_auth_db uid_avp_db uid_domain uid_gflags uid_uri_db? (y/n): y

The following MySQL users and passwords are created (please change these in a production environment).
kamailio – (With default password ‘kamailiorw’) – user which has full access rights to ‘kamailio’ database.
kamailioro – (with default password ‘kamailioro’) – user which has read-only access rights to ‘kamailio’ database.

Enable the mysql and auth modules.

Add the following to the beginning of the /etc/kamailio/kamailio.cfg after
#!KAMAILIO

#!define WITH_MYSQL

#!define WITH_AUTH

Update the DBURL line to match the username and password you set in kamctlrc before running kamdbctl.
The line looks like this by default:
#!define DBURL "mysql://kamailio:kamailioro@localhost/kamailio"
If you changed the username and password then the new user name and password would look like this
#!define DBURL "mysql://new_username:new_password@localhost/kamailio"
The new_username and new_password fields would be replaced with the values you entered in the /etc/kamailio/kamctlrcfile.

Start the Kamailio Server

service start kamailio
Note, the startup options for Kamailio is located at /etc/default/kamailio

Test Kamailio

In order to test that Kamailio is working correctly, I’m going to create a SIP user account and register that account using a softphone such as X-Lite, Linphone, or Zoiper.

Create SIP User Accounts

The following command will create a new SIP User. Note, that the domain portion has to be specified unless you export the SIP_DOMAIN environment variable.
```
kamctl add <extension@domain> <extension password>
```

Here is what I created

kamctl add 1001@dopensource.com opensourceisneat

Registering a SIP Softphone

configure whichever softphone you choose with the following options:
```
User ID: 1001
Domain:
Password: opensourceisneat
```

Once you are registered, you can view all the registered extensions in kamailio with the following command:

kamctl ul show

You will get something like this: Domain:: location table=1024 records=1 max_slot=1 AOR:: 1001 Contact:: sip:1001@192.168.1.140:40587;rinstance=636c6f6dedce9a2b;transport=UDP Q= Expires:: 3559 Callid:: OWNlYzg2YThmMmI1MGM1YjMyZTk3NjU2ZTdhMWFlN2E. Cseq:: 2 User-agent:: Z 3.3.21937 r21903 State:: CS_NEW Flags:: 0 Cflag:: 0 Socket:: udp:104.131.171.248:5060 Methods:: 5087 Ruid:: uloc-5a2f0176-36a3-1 Reg-Id:: 0 Last-Keepalive:: 1513030025 Last-Modified:: 1513030025

Make a Test Call

You can call yourself by entering 1001 into your softphone. If it rings then you have a basic Kamailio server installed and ready to be configured to provide load balancing, failover, accounting, etc. As an exercise, you should create another SIP user account and register that user using another softphone and try calling between the two SIP users.

References

Install And Maintain Kamailio v4.1.x From GIT – http://www.kamailio.org/wiki/install/4.4.x/git

Swanand

Monday 10 September 2018

Vicidial With WebRTC

Vicidial With WebRTC

Friday 31 August 2018