Archives 2022

How to – enable and use password encryption in ViciDial

Password Encryption

How to – enable and use password encryption in ViciDial

    This article is going to go over how to enable and use password encryption in ViciDial. By default passwords are displayed in plain text in the ViciDial Admin GUI, this will show you how to encrypt those.

  Step 1: Installing the Bcrypt perl module

   Using the CPAN console install the Bcrypt, run the below command

cpan
install Crypt::Eksblowfish::Bcrypt

install Bcrypt with cpan

  Step 2: Enabling the Password Encryption

    By default the Password encryption is disabled in Vicidial and we need to enable it by using a perl script via the Linux command line as show below:

/usr/share/astguiclient/ADMIN_bcrypt_convert.pl –debugX –test

If no errors received run the same script without –test flag as shown below

/usr/share/astguiclient/ADMIN_bcrypt_convert.pl –debugX 

Now navigate to ADMIN > SYSTEM SETTINGS > PASSWORD ENCRYPTION
and you’ll see the Password Encryption is now enabled. Now all new users added to the system will automatically be encrypted.

  Step 3: Encrypting Plain Text Password

    All the users passwords which are created before enabling the Password encryption, will remain as clear plain text ,to encrypt the existing plain text passwords either manually edit them and update or run the below command to convert all the plain text to encrypted text.

/usr/share/astguiclient/ADMIN_bcrypt_convert.pl –clear-plaintext-pass
or
/usr/share/astguiclient/ADMIN_bcrypt_convert.pl –debugX –update-override –clear-plaintext-pass


  How to Reset the Forgotten Password

    If you have forget the admin password , you need to update the password under mysql/mariadb with the hashed password, for non-admin users either you can update the password from admin login or follow the below procedure.

  Step 1: Generate the Hash Password

    Run the below command from SSH console with the password which you want to set of a user
for example for admin user 6666 i need to set a password as admin123

/srv/www/htdocs/agc/bp.pl –pass=admin123

The above command will output the HASHED value of admin123 ,copy that proceed to step 2

  Step 2: Updating the Mysql user table

    once hash password generated run the below mysql command with the password generated in step 1

mysql -p
use asterisk;
UPDATE vicidial_users set pass_hash=’kfYvywV959fn09rSZML70wHjjxsaYjm’ where user=’6666′;

Now you can login to the vicidial admin or agent portal with the new password.

I hope this helps some of you who need to have tighter security for your systems.

-Chris aka carpenox

How to – Remove the water drop/bloop sound from ViciDial

Confbridge Update

How to – Remove the water drop/bloop sound from ViciDial

Ok, so as most of you probably know already, Asterisk is not going to be using meetMe anymore and they have set it to “End of life” so it will no longer get any updates. So what does this mean for Vicidial which uses MeetMe channels for all its sounds and communications? Well, there is another module called confbridge which can also handle these jobs and actually can do so better and has room for some more advanced features over time I’m sure. Ok so let’s start with the main issue a lot of people are going to have, really because they are scared more than anything, is confbridge needs at least Asterisk 16 to work so our first step is going to be to update Asterisk from 13 to 16. The good news is once you do this, you can remove the water drop sound from the customer side of the calls you make so they no longer know you are calling from a call center and hangup before you even get a chance to say hi. Before getting to step 1, make sure you are at the latest SVN which at the time of this article is 3636 by following this article.

Step 1 – Upgrade to Asterisk 16

ok so lets go ahead and install Asterisk 16 by following the steps from the article below:

How to – Patch Asterisk 16 or 18 for ViciDial

We had to fix the Asterisk 16 install over Asterisk 13 by running “make uninstall” and then reinstalling as shown here:

Fixing Asterisk 16 install
Fixing Asterisk 16 install

Now we need to stop the current Asterisk 13 from running and start back up the new Asterisk 16.

asterisk -r
core restart now
/usr/share/astguiclient/start_asterisk_boot.pl
asterisk -r (make sure the version you see is 16)

Step 2 – Add new confbridge extensions

We need to edit extensions.conf and add some new conferences for confbridge to use so lets start by going into the asterisk directory:

cd /etc/asterisk
nano extensions.conf
paste the following under the [default] section:

; --------------------------
; ConfBridge Extensions
; --------------------------

; use to send a agent channel into the conference
exten => _9600XXX,1,Answer()
exten => _9600XXX,n,Playback(sip-silence)
exten => _9600XXX,n,ConfBridge(${EXTEN},vici_agent_bridge,vici_customer_user)
exten => _9600XXX,n,Hangup()

;; used to send an customer channel into the conference
exten => _29600XXX,1,Answer()
exten => _29600XXX,n,Playback(sip-silence)
exten => _29600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_agent_user)
exten => _29600XXX,n,Hangup()

;; used by an admin to enter the confernece
exten => _39600XXX,1,Answer()
exten => _39600XXX,n,Playback(sip-silence)
exten => _39600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_admin_user)
exten => _39600XXX,n,Hangup()

;; used to monitor a conference
exten => _49600XXX,1,Answer()
exten => _49600XXX,n,Playback(sip-silence)
exten => _49600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_monitor_user)
exten => _49600XXX,n,Hangup()

;; used to record into a conference
exten => _59600XXX,1,Answer()
exten => _59600XXX,n,Playback(sip-silence)
exten => _59600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_recording_user)
exten => _59600XXX,n,Hangup()

;; used to barge a conference
exten => _69600XXX,1,Answer()
exten => _69600XXX,n,Playback(sip-silence)
exten => _69600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_barge_user)
exten => _69600XXX,n,Hangup()

;; used to trigger DTMF tones in a conference
exten => _79600XXX,1,Answer()
exten => _79600XXX,n,Playback(sip-silence)
exten => _79600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_dtmf_user)
exten => _79600XXX,n,Hangup()

;; used to play an audio file to a conference
exten => _89600XXX,1,Answer()
exten => _89600XXX,n,Playback(sip-silence)
exten => _89600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_audio_user)
exten => _89600XXX,n,Hangup()

;; used to kick all channels from a conference
exten => _99600XXX,1,ConfKick(${EXTEN:1},all)
exten => _99600XXX,2,Hangup()
exten => _55559600XXX,1,ConfKick(${EXTEN:4},all)
exten => _55559600XXX,2,Hangup()

Save and exit

Step 3 – Add additional code for confbridge to work correctly

We have to edit a couple files so first lets do:

nano /etc/asterisk/confbridge.conf and paste this at the bottom:
#include confbridge-vicidial.conf

Now create a new file called confbridge-vicidial.conf and add the following lines:

; Bridge Profile for agent conferences
[vici_agent_bridge]
type=bridge
max_members=10
record_conference=no
internal_sample_rate=8000
mixing_interval=40
video_mode=none
sound_join=enter
sound_leave=leave
sound_has_joined=sip-silence
sound_has_left=sip-silence
sound_kicked=sip-silence
sound_muted=sip-silence
sound_unmuted=sip-silence
sound_only_person=confbridge-only-participant
sound_only_one=sip-silence
sound_there_are=sip-silence
sound_other_in_party=sip-silence
sound_begin=sip-silence
sound_wait_for_leader=sip-silence
sound_leader_has_left=sip-silence
sound_get_pin=sip-silence
sound_invalid_pin=sip-silence
sound_locked=sip-silence
sound_locked_now=sip-silence
sound_unlocked_now=sip-silence
sound_error_menu=sip-silence
sound_participants_muted=sip-silence


; User Profile for agent channels
[vici_agent_user]
type=user
admin=no
quiet=no
startmuted=no
marked=yes
dtmf_passthrough=yes
hear_own_join_sound=yes
dsp_drop_silence=yes

; User Profile for admin channels
[vici_admin_user]
type=user
admin=yes
quiet=no
startmuted=no
marked=yes
dtmf_passthrough=yes
dsp_drop_silence=yes

; User Profile for monitoring
[vici_monitor_user]
type=user
admin=no
quiet=no
startmuted=yes
marked=no
dtmf_passthrough=no
dsp_drop_silence=yes

; User Profile for barging
[vici_barge_user]
type=user
admin=no
quiet=no
startmuted=no
marked=no
dtmf_passthrough=yes
dsp_drop_silence=yes

; User Profile for customers channels
[vici_customer_user]
type=user
admin=no
quiet=no
startmuted=no
marked=yes
dtmf_passthrough=yes
hear_own_join_sound=no
dsp_drop_silence=yes

; User Profile for call recording channels
[vici_recording_user]
type=user
admin=no
quiet=yes
startmuted=yes
marked=no
dtmf_passthrough=no
dsp_drop_silence=yes

; User Profile for audio playback channels
[vici_audio_user]
type=user
admin=no
quiet=yes
startmuted=yes
marked=no
dtmf_passthrough=no
dsp_drop_silence=yes

; User Profile for triggering DTMF
[vici_dtmf_user]
type=user
admin=no
quiet=yes
startmuted=yes
marked=no
dtmf_passthrough=yes
dsp_drop_silence=yes

Step 4 – Add ConfBridge Conferences to Database

Go into mysql and add the conferences to the vicidial_confbridges table by pasting the following commands:

mysql -A asterisk
INSERT INTO `vicidial_confbridges` VALUES 
(9600000,'10.10.10.17','','0',NULL),
(9600001,'10.10.10.17','','0',NULL),
(9600002,'10.10.10.17','','0',NULL),
(9600003,'10.10.10.17','','0',NULL),
(9600004,'10.10.10.17','','0',NULL),
(9600005,'10.10.10.17','','0',NULL),
(9600006,'10.10.10.17','','0',NULL),
(9600007,'10.10.10.17','','0',NULL),
(9600008,'10.10.10.17','','0',NULL),
(9600009,'10.10.10.17','','0',NULL),
(9600010,'10.10.10.17','','0',NULL),
(9600011,'10.10.10.17','','0',NULL),
(9600012,'10.10.10.17','','0',NULL),
(9600013,'10.10.10.17','','0',NULL),
(9600014,'10.10.10.17','','0',NULL),
(9600015,'10.10.10.17','','0',NULL),
(9600016,'10.10.10.17','','0',NULL),
(9600017,'10.10.10.17','','0',NULL),
(9600018,'10.10.10.17','','0',NULL),
(9600019,'10.10.10.17','','0',NULL),
(9600020,'10.10.10.17','','0',NULL),
(9600021,'10.10.10.17','','0',NULL),
(9600022,'10.10.10.17','','0',NULL),
(9600023,'10.10.10.17','','0',NULL),
(9600024,'10.10.10.17','','0',NULL),
(9600025,'10.10.10.17','','0',NULL),
(9600026,'10.10.10.17','','0',NULL),
(9600027,'10.10.10.17','','0',NULL),
(9600028,'10.10.10.17','','0',NULL),
(9600029,'10.10.10.17','','0',NULL),
(9600030,'10.10.10.17','','0',NULL),
(9600031,'10.10.10.17','','0',NULL),
(9600032,'10.10.10.17','','0',NULL),
(9600033,'10.10.10.17','','0',NULL),
(9600034,'10.10.10.17','','0',NULL),
(9600035,'10.10.10.17','','0',NULL),
(9600036,'10.10.10.17','','0',NULL),
(9600037,'10.10.10.17','','0',NULL),
(9600038,'10.10.10.17','','0',NULL),
(9600039,'10.10.10.17','','0',NULL),
(9600040,'10.10.10.17','','0',NULL),
(9600041,'10.10.10.17','','0',NULL),
(9600042,'10.10.10.17','','0',NULL),
(9600043,'10.10.10.17','','0',NULL),
(9600044,'10.10.10.17','','0',NULL),
(9600045,'10.10.10.17','','0',NULL),
(9600046,'10.10.10.17','','0',NULL),
(9600047,'10.10.10.17','','0',NULL),
(9600048,'10.10.10.17','','0',NULL),
(9600049,'10.10.10.17','','0',NULL),
(9600050,'10.10.10.17','','0',NULL),
(9600051,'10.10.10.17','','0',NULL),
(9600052,'10.10.10.17','','0',NULL),
(9600053,'10.10.10.17','','0',NULL),
(9600054,'10.10.10.17','','0',NULL),
(9600055,'10.10.10.17','','0',NULL),
(9600056,'10.10.10.17','','0',NULL),
(9600057,'10.10.10.17','','0',NULL),
(9600058,'10.10.10.17','','0',NULL),
(9600059,'10.10.10.17','','0',NULL),
(9600060,'10.10.10.17','','0',NULL),
(9600061,'10.10.10.17','','0',NULL),
(9600062,'10.10.10.17','','0',NULL),
(9600063,'10.10.10.17','','0',NULL),
(9600064,'10.10.10.17','','0',NULL),
(9600065,'10.10.10.17','','0',NULL),
(9600066,'10.10.10.17','','0',NULL),
(9600067,'10.10.10.17','','0',NULL),
(9600068,'10.10.10.17','','0',NULL),
(9600069,'10.10.10.17','','0',NULL),
(9600070,'10.10.10.17','','0',NULL),
(9600071,'10.10.10.17','','0',NULL),
(9600072,'10.10.10.17','','0',NULL),
(9600073,'10.10.10.17','','0',NULL),
(9600074,'10.10.10.17','','0',NULL),
(9600075,'10.10.10.17','','0',NULL),
(9600076,'10.10.10.17','','0',NULL),
(9600077,'10.10.10.17','','0',NULL),
(9600078,'10.10.10.17','','0',NULL),
(9600079,'10.10.10.17','','0',NULL),
(9600080,'10.10.10.17','','0',NULL),
(9600081,'10.10.10.17','','0',NULL),
(9600082,'10.10.10.17','','0',NULL),
(9600083,'10.10.10.17','','0',NULL),
(9600084,'10.10.10.17','','0',NULL),
(9600085,'10.10.10.17','','0',NULL),
(9600086,'10.10.10.17','','0',NULL),
(9600087,'10.10.10.17','','0',NULL),
(9600088,'10.10.10.17','','0',NULL),
(9600089,'10.10.10.17','','0',NULL),
(9600090,'10.10.10.17','','0',NULL),
(9600091,'10.10.10.17','','0',NULL),
(9600092,'10.10.10.17','','0',NULL),
(9600093,'10.10.10.17','','0',NULL),
(9600094,'10.10.10.17','','0',NULL),
(9600095,'10.10.10.17','','0',NULL),
(9600096,'10.10.10.17','','0',NULL),
(9600097,'10.10.10.17','','0',NULL),
(9600098,'10.10.10.17','','0',NULL),
(9600099,'10.10.10.17','','0',NULL),
(9600100,'10.10.10.17','','0',NULL),
(9600101,'10.10.10.17','','0',NULL),
(9600102,'10.10.10.17','','0',NULL),
(9600103,'10.10.10.17','','0',NULL),
(9600104,'10.10.10.17','','0',NULL),
(9600105,'10.10.10.17','','0',NULL),
(9600106,'10.10.10.17','','0',NULL),
(9600107,'10.10.10.17','','0',NULL),
(9600108,'10.10.10.17','','0',NULL),
(9600109,'10.10.10.17','','0',NULL),
(9600110,'10.10.10.17','','0',NULL),
(9600111,'10.10.10.17','','0',NULL),
(9600112,'10.10.10.17','','0',NULL),
(9600113,'10.10.10.17','','0',NULL),
(9600114,'10.10.10.17','','0',NULL),
(9600115,'10.10.10.17','','0',NULL),
(9600116,'10.10.10.17','','0',NULL),
(9600117,'10.10.10.17','','0',NULL),
(9600118,'10.10.10.17','','0',NULL),
(9600119,'10.10.10.17','','0',NULL),
(9600120,'10.10.10.17','','0',NULL),
(9600121,'10.10.10.17','','0',NULL),
(9600122,'10.10.10.17','','0',NULL),
(9600123,'10.10.10.17','','0',NULL),
(9600124,'10.10.10.17','','0',NULL),
(9600125,'10.10.10.17','','0',NULL),
(9600126,'10.10.10.17','','0',NULL),
(9600127,'10.10.10.17','','0',NULL),
(9600128,'10.10.10.17','','0',NULL),
(9600129,'10.10.10.17','','0',NULL),
(9600130,'10.10.10.17','','0',NULL),
(9600131,'10.10.10.17','','0',NULL),
(9600132,'10.10.10.17','','0',NULL),
(9600133,'10.10.10.17','','0',NULL),
(9600134,'10.10.10.17','','0',NULL),
(9600135,'10.10.10.17','','0',NULL),
(9600136,'10.10.10.17','','0',NULL),
(9600137,'10.10.10.17','','0',NULL),
(9600138,'10.10.10.17','','0',NULL),
(9600139,'10.10.10.17','','0',NULL),
(9600140,'10.10.10.17','','0',NULL),
(9600141,'10.10.10.17','','0',NULL),
(9600142,'10.10.10.17','','0',NULL),
(9600143,'10.10.10.17','','0',NULL),
(9600144,'10.10.10.17','','0',NULL),
(9600145,'10.10.10.17','','0',NULL),
(9600146,'10.10.10.17','','0',NULL),
(9600147,'10.10.10.17','','0',NULL),
(9600148,'10.10.10.17','','0',NULL),
(9600149,'10.10.10.17','','0',NULL),
(9600150,'10.10.10.17','','0',NULL),
(9600151,'10.10.10.17','','0',NULL),
(9600152,'10.10.10.17','','0',NULL),
(9600153,'10.10.10.17','','0',NULL),
(9600154,'10.10.10.17','','0',NULL),
(9600155,'10.10.10.17','','0',NULL),
(9600156,'10.10.10.17','','0',NULL),
(9600157,'10.10.10.17','','0',NULL),
(9600158,'10.10.10.17','','0',NULL),
(9600159,'10.10.10.17','','0',NULL),
(9600160,'10.10.10.17','','0',NULL),
(9600161,'10.10.10.17','','0',NULL),
(9600162,'10.10.10.17','','0',NULL),
(9600163,'10.10.10.17','','0',NULL),
(9600164,'10.10.10.17','','0',NULL),
(9600165,'10.10.10.17','','0',NULL),
(9600166,'10.10.10.17','','0',NULL),
(9600167,'10.10.10.17','','0',NULL),
(9600168,'10.10.10.17','','0',NULL),
(9600169,'10.10.10.17','','0',NULL),
(9600170,'10.10.10.17','','0',NULL),
(9600171,'10.10.10.17','','0',NULL),
(9600172,'10.10.10.17','','0',NULL),
(9600173,'10.10.10.17','','0',NULL),
(9600174,'10.10.10.17','','0',NULL),
(9600175,'10.10.10.17','','0',NULL),
(9600176,'10.10.10.17','','0',NULL),
(9600177,'10.10.10.17','','0',NULL),
(9600178,'10.10.10.17','','0',NULL),
(9600179,'10.10.10.17','','0',NULL),
(9600180,'10.10.10.17','','0',NULL),
(9600181,'10.10.10.17','','0',NULL),
(9600182,'10.10.10.17','','0',NULL),
(9600183,'10.10.10.17','','0',NULL),
(9600184,'10.10.10.17','','0',NULL),
(9600185,'10.10.10.17','','0',NULL),
(9600186,'10.10.10.17','','0',NULL),
(9600187,'10.10.10.17','','0',NULL),
(9600188,'10.10.10.17','','0',NULL),
(9600189,'10.10.10.17','','0',NULL),
(9600190,'10.10.10.17','','0',NULL),
(9600191,'10.10.10.17','','0',NULL),
(9600192,'10.10.10.17','','0',NULL),
(9600193,'10.10.10.17','','0',NULL),
(9600194,'10.10.10.17','','0',NULL),
(9600195,'10.10.10.17','','0',NULL),
(9600196,'10.10.10.17','','0',NULL),
(9600197,'10.10.10.17','','0',NULL),
(9600198,'10.10.10.17','','0',NULL),
(9600199,'10.10.10.17','','0',NULL),
(9600200,'10.10.10.17','','0',NULL),
(9600201,'10.10.10.17','','0',NULL),
(9600202,'10.10.10.17','','0',NULL),
(9600203,'10.10.10.17','','0',NULL),
(9600204,'10.10.10.17','','0',NULL),
(9600205,'10.10.10.17','','0',NULL),
(9600206,'10.10.10.17','','0',NULL),
(9600207,'10.10.10.17','','0',NULL),
(9600208,'10.10.10.17','','0',NULL),
(9600209,'10.10.10.17','','0',NULL),
(9600210,'10.10.10.17','','0',NULL),
(9600211,'10.10.10.17','','0',NULL),
(9600212,'10.10.10.17','','0',NULL),
(9600213,'10.10.10.17','','0',NULL),
(9600214,'10.10.10.17','','0',NULL),
(9600215,'10.10.10.17','','0',NULL),
(9600216,'10.10.10.17','','0',NULL),
(9600217,'10.10.10.17','','0',NULL),
(9600218,'10.10.10.17','','0',NULL),
(9600219,'10.10.10.17','','0',NULL),
(9600220,'10.10.10.17','','0',NULL),
(9600221,'10.10.10.17','','0',NULL),
(9600222,'10.10.10.17','','0',NULL),
(9600223,'10.10.10.17','','0',NULL),
(9600224,'10.10.10.17','','0',NULL),
(9600225,'10.10.10.17','','0',NULL),
(9600226,'10.10.10.17','','0',NULL),
(9600227,'10.10.10.17','','0',NULL),
(9600228,'10.10.10.17','','0',NULL),
(9600229,'10.10.10.17','','0',NULL),
(9600230,'10.10.10.17','','0',NULL),
(9600231,'10.10.10.17','','0',NULL),
(9600232,'10.10.10.17','','0',NULL),
(9600233,'10.10.10.17','','0',NULL),
(9600234,'10.10.10.17','','0',NULL),
(9600235,'10.10.10.17','','0',NULL),
(9600236,'10.10.10.17','','0',NULL),
(9600237,'10.10.10.17','','0',NULL),
(9600238,'10.10.10.17','','0',NULL),
(9600239,'10.10.10.17','','0',NULL),
(9600240,'10.10.10.17','','0',NULL),
(9600241,'10.10.10.17','','0',NULL),
(9600242,'10.10.10.17','','0',NULL),
(9600243,'10.10.10.17','','0',NULL),
(9600244,'10.10.10.17','','0',NULL),
(9600245,'10.10.10.17','','0',NULL),
(9600246,'10.10.10.17','','0',NULL),
(9600247,'10.10.10.17','','0',NULL),
(9600248,'10.10.10.17','','0',NULL),
(9600249,'10.10.10.17','','0',NULL),
(9600250,'10.10.10.17','','0',NULL),
(9600251,'10.10.10.17','','0',NULL),
(9600252,'10.10.10.17','','0',NULL),
(9600253,'10.10.10.17','','0',NULL),
(9600254,'10.10.10.17','','0',NULL),
(9600255,'10.10.10.17','','0',NULL),
(9600256,'10.10.10.17','','0',NULL),
(9600257,'10.10.10.17','','0',NULL),
(9600258,'10.10.10.17','','0',NULL),
(9600259,'10.10.10.17','','0',NULL),
(9600260,'10.10.10.17','','0',NULL),
(9600261,'10.10.10.17','','0',NULL),
(9600262,'10.10.10.17','','0',NULL),
(9600263,'10.10.10.17','','0',NULL),
(9600264,'10.10.10.17','','0',NULL),
(9600265,'10.10.10.17','','0',NULL),
(9600266,'10.10.10.17','','0',NULL),
(9600267,'10.10.10.17','','0',NULL),
(9600268,'10.10.10.17','','0',NULL),
(9600269,'10.10.10.17','','0',NULL),
(9600270,'10.10.10.17','','0',NULL),
(9600271,'10.10.10.17','','0',NULL),
(9600272,'10.10.10.17','','0',NULL),
(9600273,'10.10.10.17','','0',NULL),
(9600274,'10.10.10.17','','0',NULL),
(9600275,'10.10.10.17','','0',NULL),
(9600276,'10.10.10.17','','0',NULL),
(9600277,'10.10.10.17','','0',NULL),
(9600278,'10.10.10.17','','0',NULL),
(9600279,'10.10.10.17','','0',NULL),
(9600280,'10.10.10.17','','0',NULL),
(9600281,'10.10.10.17','','0',NULL),
(9600282,'10.10.10.17','','0',NULL),
(9600283,'10.10.10.17','','0',NULL),
(9600284,'10.10.10.17','','0',NULL),
(9600285,'10.10.10.17','','0',NULL),
(9600286,'10.10.10.17','','0',NULL),
(9600287,'10.10.10.17','','0',NULL),
(9600288,'10.10.10.17','','0',NULL),
(9600289,'10.10.10.17','','0',NULL),
(9600290,'10.10.10.17','','0',NULL),
(9600291,'10.10.10.17','','0',NULL),
(9600292,'10.10.10.17','','0',NULL),
(9600293,'10.10.10.17','','0',NULL),
(9600294,'10.10.10.17','','0',NULL),
(9600295,'10.10.10.17','','0',NULL),
(9600296,'10.10.10.17','','0',NULL),
(9600297,'10.10.10.17','','0',NULL),
(9600298,'10.10.10.17','','0',NULL),
(9600299,'10.10.10.17','','0',NULL);
exit

Update the IP to your server IP by running the following command:

/usr/share/astguiclient/ADMIN_update_server_ip.pl --old-server_ip=10.10.10.17

(Click Enter for Y)
Next enter your server IP and press enter twice to chaneg it in the DB as show below:

updating server IP
Update Server IP

Step 5 – Code changes to ViciDial files

There are some files now that have to be patched in order to include the changes needed for confbrides to work. They are in the “extras/ConfBridge/” directory of the svn/trunk codebase. Lets copy the files over to where they are needed, this will depend on if you are using a single server or a cluster to where the files go. Here is a list of where they go:

Dialers:
/usr/share/astguiclient/ - 
- ADMIN_keepalive_ALL.pl.diff
- ADMIN_update_server_ip.pl.diff
- AST_DB_optimize.pl.diff
- AST_reset_mysql_vars.pl.diff
- AST_VDremote_agents.pl.diff
- AST_conf_update_screen.pl

Webservers:
/srv/www/htdocs/agc/ - 
- vicidial.php.diff
- vdc_db_query.php.diff
- manager_send.php.diff
/srv/www/htdocs/vicidial/ - 
- non_agent_api.php.diff

You can copy and paste the entire code below to get it all done
cd /usr/src/astguiclient/trunk/extras/ConfBridge/
cp * /usr/share/astguiclient/
cd /usr/share/astguiclient/
mv manager_send.php.diff vdc_db_query.php.diff vicidial.php.diff /var/www/html/agc/
patch -p0 < ADMIN_keepalive_ALL.pl.diff
patch -p0 < ADMIN_update_server_ip.pl.diff
patch -p0 < AST_DB_optimize.pl.diff
chmod +x AST_conf_update_screen.pl
patch -p0 < AST_reset_mysql_vars.pl.diff
cd /var/www/html/agc/
patch -p0 < manager_send.php.diff
patch -p0 < vdc_db_query.php.diff
patch -p0 < vicidial.php.diff

Step 6 – Add the confbridge keepalive and turn off the conf_update keepalive in crontab

A new screen session has been added called 'AST_conf_update_screen.pl'. This screen session replaces both the AST_conf_update.pl and AST_conf_update_3way.pl scripts. It checks both MeetMe and ConfBridge conferences for unnecessary channels and removes them. For instance if an agent does a Leave 3way and a few minutes later one of the remaining channels hangs up. This script will remove the remaining channel and free the conference for use by Vicidial. This screen session is optional for use with MeetMe but is required to be used with ConfBridge.
Add C to VARactive_keepalives
Add C to VARactive_keepalives
To enable this screen session you need to add a 'C' to the 'VARactive_keepalives' variable in the '/etc/astguiclient.conf' on your dialers, and comment out the following line from your crontab:

                ### updater for conference validator
                #* * * * * /usr/share/astguiclient/AST_conf_update.pl

You can configure the refresh interval for how often the screen session checks for unnecessary channels by changing "Conf Update Interval" in Admin -> Servers.

Step 7- Make the needed changes in ViciDial GUI

Login to the ViciDial Admin GUI and go to Admin > Servers and click on the server(s) that are dialers and change the conferencing engine to “CONFBRIDGE” as shown below:

Change conferencing Engine to CONFBRIDGE
Change conferencing Engine to CONFBRIDGE

Step 8 – Add confbridge to manager.conf

nano /etc/asterisk/manager.conf
Go to the bottom and paste:

[confcron]
secret = 1234
read = command,reporting
write = command,reporting

eventfilter=Event: Meetme
eventfilter=Event: Confbridge

Thats a lot to get through but now that its done your customers will no longer hear the “Water drop” or “bloop” sound that they do now and you’re ready for the future of Asterisk now that meetme has been deprecated. Thats it for now, you’re all done. Hopefully this helps those of you who are a little intimidated to try the change and like always, if you have any problems, feel free to visit our Skype live support with almost 200 Vicidial experts from around the world.

-Chris aka carpenox

How to – Switch ViciDial from meetme to confbridge

Confbridge Update

How to – Switch ViciDial from meetme to confbridge

Ok, so as most of you probably know already, Asterisk is not going to be using meetMe anymore and they have set it to “End of life” so it will no longer get any updates. So what does this mean for Vicidial which uses MeetMe channels for all its sounds and communications? Well, there is another module called confbridge which can also handle these jobs and actually can do so better and has room for some more advanced features over time I’m sure. Ok so let’s start with the main issue a lot of people are going to have, really because they are scared more than anything, is confbridge needs at least Asterisk 16 to work so our first step is going to be to update Asterisk from 13 to 16. Make sure you are at the latest SVN which at the time of this article is 3636 by following this article.

Step 1 – Upgrade to Asterisk 16

ok so lets go ahead and install Asterisk 16 by following the steps below:

First you will need to follow this article on how to download, patch and compile Asterisk 16 or you can use the compile commands below:

./configure --libdir=/usr/lib64 --with-pjproject-bundled --with-jansson-bundled
rm -rf menuselect.makeopts
make menuselect*
**** Go down one to applications and hit enter, go down until you find the "meetme" app and press space bar, then hit "X" ****
make && make install
make uninstall
make install

We had to fix the Asterisk 16 install over Asterisk 13 by running “make uninstall” and then reinstalling as shown here:

Fixing Asterisk 16 install
Fixing Asterisk 16 install

Now we need to stop the current Asterisk 13 from running and start back up the new Asterisk 16.

asterisk -r
core restart now
/usr/share/astguiclient/start_asterisk_boot.pl
asterisk -r (make sure the version you see is 16)

Step 2 – Add new confbridge extensions

We need to edit extensions.conf and add some new conferences for confbridge to use so lets start by going into the asterisk directory:

cd /etc/asterisk
nano extensions.conf
paste the following at the bottom:

; --------------------------
; ConfBridge Extensions
; --------------------------

; use to send a agent channel into the conference
exten => _9600XXX,1,Answer()
exten => _9600XXX,n,Playback(sip-silence)
exten => _9600XXX,n,ConfBridge(${EXTEN},vici_agent_bridge,vici_customer_user)
exten => _9600XXX,n,Hangup()

;; used to send an customer channel into the conference
exten => _29600XXX,1,Answer()
exten => _29600XXX,n,Playback(sip-silence)
exten => _29600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_agent_user)
exten => _29600XXX,n,Hangup()

;; used by an admin to enter the confernece
exten => _39600XXX,1,Answer()
exten => _39600XXX,n,Playback(sip-silence)
exten => _39600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_admin_user)
exten => _39600XXX,n,Hangup()

;; used to monitor a conference
exten => _49600XXX,1,Answer()
exten => _49600XXX,n,Playback(sip-silence)
exten => _49600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_monitor_user)
exten => _49600XXX,n,Hangup()

;; used to record into a conference
exten => _59600XXX,1,Answer()
exten => _59600XXX,n,Playback(sip-silence)
exten => _59600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_recording_user)
exten => _59600XXX,n,Hangup()

;; used to barge a conference
exten => _69600XXX,1,Answer()
exten => _69600XXX,n,Playback(sip-silence)
exten => _69600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_barge_user)
exten => _69600XXX,n,Hangup()

;; used to trigger DTMF tones in a conference
exten => _79600XXX,1,Answer()
exten => _79600XXX,n,Playback(sip-silence)
exten => _79600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_dtmf_user)
exten => _79600XXX,n,Hangup()

;; used to play an audio file to a conference
exten => _89600XXX,1,Answer()
exten => _89600XXX,n,Playback(sip-silence)
exten => _89600XXX,n,ConfBridge(${EXTEN:1},vici_agent_bridge,vici_audio_user)
exten => _89600XXX,n,Hangup()

;; used to kick all channels from a conference
exten => _99600XXX,1,ConfKick(${EXTEN:1},all)
exten => _99600XXX,2,Hangup()
exten => _55559600XXX,1,ConfKick(${EXTEN:4},all)
exten => _55559600XXX,2,Hangup()

Save and exit

Step 3 – Add additional code for confbridge to work correctly

We have to edit a couple files so first lets do:

nano /etc/asterisk/confbridge.conf and paste this at the bottom:
#include confbridge-vicidial.conf

Now create a new file called confbridge-vicidial.conf and add the following lines:

; Bridge Profile for agent conferences
[vici_agent_bridge]
type=bridge
max_members=10
record_conference=no
internal_sample_rate=8000
mixing_interval=40
video_mode=none
sound_join=enter
sound_leave=leave
sound_has_joined=sip-silence
sound_has_left=sip-silence
sound_kicked=sip-silence
sound_muted=sip-silence
sound_unmuted=sip-silence
sound_only_person=confbridge-only-participant
sound_only_one=sip-silence
sound_there_are=sip-silence
sound_other_in_party=sip-silence
sound_begin=sip-silence
sound_wait_for_leader=sip-silence
sound_leader_has_left=sip-silence
sound_get_pin=sip-silence
sound_invalid_pin=sip-silence
sound_locked=sip-silence
sound_locked_now=sip-silence
sound_unlocked_now=sip-silence
sound_error_menu=sip-silence
sound_participants_muted=sip-silence


; User Profile for agent channels
[vici_agent_user]
type=user
admin=no
quiet=no
startmuted=no
marked=yes
dtmf_passthrough=yes
hear_own_join_sound=yes
dsp_drop_silence=yes

; User Profile for admin channels
[vici_admin_user]
type=user
admin=yes
quiet=no
startmuted=no
marked=yes
dtmf_passthrough=yes
dsp_drop_silence=yes

; User Profile for monitoring
[vici_monitor_user]
type=user
admin=no
quiet=no
startmuted=yes
marked=no
dtmf_passthrough=no
dsp_drop_silence=yes

; User Profile for barging
[vici_barge_user]
type=user
admin=no
quiet=no
startmuted=no
marked=no
dtmf_passthrough=yes
dsp_drop_silence=yes

; User Profile for customers channels
[vici_customer_user]
type=user
admin=no
quiet=no
startmuted=no
marked=yes
dtmf_passthrough=yes
hear_own_join_sound=no
dsp_drop_silence=yes

; User Profile for call recording channels
[vici_recording_user]
type=user
admin=no
quiet=yes
startmuted=yes
marked=no
dtmf_passthrough=no
dsp_drop_silence=yes

; User Profile for audio playback channels
[vici_audio_user]
type=user
admin=no
quiet=yes
startmuted=yes
marked=no
dtmf_passthrough=no
dsp_drop_silence=yes

; User Profile for triggering DTMF
[vici_dtmf_user]
type=user
admin=no
quiet=yes
startmuted=yes
marked=no
dtmf_passthrough=yes
dsp_drop_silence=yes

Step 4 – Add ConfBridge Conferences to Database

Go into mysql and add the conferences to the vicidial_confbridges table by pasting the following commands:

mysql -A asterisk
INSERT INTO `vicidial_confbridges` VALUES 
(9600000,'10.10.10.17','','0',NULL),
(9600001,'10.10.10.17','','0',NULL),
(9600002,'10.10.10.17','','0',NULL),
(9600003,'10.10.10.17','','0',NULL),
(9600004,'10.10.10.17','','0',NULL),
(9600005,'10.10.10.17','','0',NULL),
(9600006,'10.10.10.17','','0',NULL),
(9600007,'10.10.10.17','','0',NULL),
(9600008,'10.10.10.17','','0',NULL),
(9600009,'10.10.10.17','','0',NULL),
(9600010,'10.10.10.17','','0',NULL),
(9600011,'10.10.10.17','','0',NULL),
(9600012,'10.10.10.17','','0',NULL),
(9600013,'10.10.10.17','','0',NULL),
(9600014,'10.10.10.17','','0',NULL),
(9600015,'10.10.10.17','','0',NULL),
(9600016,'10.10.10.17','','0',NULL),
(9600017,'10.10.10.17','','0',NULL),
(9600018,'10.10.10.17','','0',NULL),
(9600019,'10.10.10.17','','0',NULL),
(9600020,'10.10.10.17','','0',NULL),
(9600021,'10.10.10.17','','0',NULL),
(9600022,'10.10.10.17','','0',NULL),
(9600023,'10.10.10.17','','0',NULL),
(9600024,'10.10.10.17','','0',NULL),
(9600025,'10.10.10.17','','0',NULL),
(9600026,'10.10.10.17','','0',NULL),
(9600027,'10.10.10.17','','0',NULL),
(9600028,'10.10.10.17','','0',NULL),
(9600029,'10.10.10.17','','0',NULL),
(9600030,'10.10.10.17','','0',NULL),
(9600031,'10.10.10.17','','0',NULL),
(9600032,'10.10.10.17','','0',NULL),
(9600033,'10.10.10.17','','0',NULL),
(9600034,'10.10.10.17','','0',NULL),
(9600035,'10.10.10.17','','0',NULL),
(9600036,'10.10.10.17','','0',NULL),
(9600037,'10.10.10.17','','0',NULL),
(9600038,'10.10.10.17','','0',NULL),
(9600039,'10.10.10.17','','0',NULL),
(9600040,'10.10.10.17','','0',NULL),
(9600041,'10.10.10.17','','0',NULL),
(9600042,'10.10.10.17','','0',NULL),
(9600043,'10.10.10.17','','0',NULL),
(9600044,'10.10.10.17','','0',NULL),
(9600045,'10.10.10.17','','0',NULL),
(9600046,'10.10.10.17','','0',NULL),
(9600047,'10.10.10.17','','0',NULL),
(9600048,'10.10.10.17','','0',NULL),
(9600049,'10.10.10.17','','0',NULL),
(9600050,'10.10.10.17','','0',NULL),
(9600051,'10.10.10.17','','0',NULL),
(9600052,'10.10.10.17','','0',NULL),
(9600053,'10.10.10.17','','0',NULL),
(9600054,'10.10.10.17','','0',NULL),
(9600055,'10.10.10.17','','0',NULL),
(9600056,'10.10.10.17','','0',NULL),
(9600057,'10.10.10.17','','0',NULL),
(9600058,'10.10.10.17','','0',NULL),
(9600059,'10.10.10.17','','0',NULL),
(9600060,'10.10.10.17','','0',NULL),
(9600061,'10.10.10.17','','0',NULL),
(9600062,'10.10.10.17','','0',NULL),
(9600063,'10.10.10.17','','0',NULL),
(9600064,'10.10.10.17','','0',NULL),
(9600065,'10.10.10.17','','0',NULL),
(9600066,'10.10.10.17','','0',NULL),
(9600067,'10.10.10.17','','0',NULL),
(9600068,'10.10.10.17','','0',NULL),
(9600069,'10.10.10.17','','0',NULL),
(9600070,'10.10.10.17','','0',NULL),
(9600071,'10.10.10.17','','0',NULL),
(9600072,'10.10.10.17','','0',NULL),
(9600073,'10.10.10.17','','0',NULL),
(9600074,'10.10.10.17','','0',NULL),
(9600075,'10.10.10.17','','0',NULL),
(9600076,'10.10.10.17','','0',NULL),
(9600077,'10.10.10.17','','0',NULL),
(9600078,'10.10.10.17','','0',NULL),
(9600079,'10.10.10.17','','0',NULL),
(9600080,'10.10.10.17','','0',NULL),
(9600081,'10.10.10.17','','0',NULL),
(9600082,'10.10.10.17','','0',NULL),
(9600083,'10.10.10.17','','0',NULL),
(9600084,'10.10.10.17','','0',NULL),
(9600085,'10.10.10.17','','0',NULL),
(9600086,'10.10.10.17','','0',NULL),
(9600087,'10.10.10.17','','0',NULL),
(9600088,'10.10.10.17','','0',NULL),
(9600089,'10.10.10.17','','0',NULL),
(9600090,'10.10.10.17','','0',NULL),
(9600091,'10.10.10.17','','0',NULL),
(9600092,'10.10.10.17','','0',NULL),
(9600093,'10.10.10.17','','0',NULL),
(9600094,'10.10.10.17','','0',NULL),
(9600095,'10.10.10.17','','0',NULL),
(9600096,'10.10.10.17','','0',NULL),
(9600097,'10.10.10.17','','0',NULL),
(9600098,'10.10.10.17','','0',NULL),
(9600099,'10.10.10.17','','0',NULL),
(9600100,'10.10.10.17','','0',NULL),
(9600101,'10.10.10.17','','0',NULL),
(9600102,'10.10.10.17','','0',NULL),
(9600103,'10.10.10.17','','0',NULL),
(9600104,'10.10.10.17','','0',NULL),
(9600105,'10.10.10.17','','0',NULL),
(9600106,'10.10.10.17','','0',NULL),
(9600107,'10.10.10.17','','0',NULL),
(9600108,'10.10.10.17','','0',NULL),
(9600109,'10.10.10.17','','0',NULL),
(9600110,'10.10.10.17','','0',NULL),
(9600111,'10.10.10.17','','0',NULL),
(9600112,'10.10.10.17','','0',NULL),
(9600113,'10.10.10.17','','0',NULL),
(9600114,'10.10.10.17','','0',NULL),
(9600115,'10.10.10.17','','0',NULL),
(9600116,'10.10.10.17','','0',NULL),
(9600117,'10.10.10.17','','0',NULL),
(9600118,'10.10.10.17','','0',NULL),
(9600119,'10.10.10.17','','0',NULL),
(9600120,'10.10.10.17','','0',NULL),
(9600121,'10.10.10.17','','0',NULL),
(9600122,'10.10.10.17','','0',NULL),
(9600123,'10.10.10.17','','0',NULL),
(9600124,'10.10.10.17','','0',NULL),
(9600125,'10.10.10.17','','0',NULL),
(9600126,'10.10.10.17','','0',NULL),
(9600127,'10.10.10.17','','0',NULL),
(9600128,'10.10.10.17','','0',NULL),
(9600129,'10.10.10.17','','0',NULL),
(9600130,'10.10.10.17','','0',NULL),
(9600131,'10.10.10.17','','0',NULL),
(9600132,'10.10.10.17','','0',NULL),
(9600133,'10.10.10.17','','0',NULL),
(9600134,'10.10.10.17','','0',NULL),
(9600135,'10.10.10.17','','0',NULL),
(9600136,'10.10.10.17','','0',NULL),
(9600137,'10.10.10.17','','0',NULL),
(9600138,'10.10.10.17','','0',NULL),
(9600139,'10.10.10.17','','0',NULL),
(9600140,'10.10.10.17','','0',NULL),
(9600141,'10.10.10.17','','0',NULL),
(9600142,'10.10.10.17','','0',NULL),
(9600143,'10.10.10.17','','0',NULL),
(9600144,'10.10.10.17','','0',NULL),
(9600145,'10.10.10.17','','0',NULL),
(9600146,'10.10.10.17','','0',NULL),
(9600147,'10.10.10.17','','0',NULL),
(9600148,'10.10.10.17','','0',NULL),
(9600149,'10.10.10.17','','0',NULL),
(9600150,'10.10.10.17','','0',NULL),
(9600151,'10.10.10.17','','0',NULL),
(9600152,'10.10.10.17','','0',NULL),
(9600153,'10.10.10.17','','0',NULL),
(9600154,'10.10.10.17','','0',NULL),
(9600155,'10.10.10.17','','0',NULL),
(9600156,'10.10.10.17','','0',NULL),
(9600157,'10.10.10.17','','0',NULL),
(9600158,'10.10.10.17','','0',NULL),
(9600159,'10.10.10.17','','0',NULL),
(9600160,'10.10.10.17','','0',NULL),
(9600161,'10.10.10.17','','0',NULL),
(9600162,'10.10.10.17','','0',NULL),
(9600163,'10.10.10.17','','0',NULL),
(9600164,'10.10.10.17','','0',NULL),
(9600165,'10.10.10.17','','0',NULL),
(9600166,'10.10.10.17','','0',NULL),
(9600167,'10.10.10.17','','0',NULL),
(9600168,'10.10.10.17','','0',NULL),
(9600169,'10.10.10.17','','0',NULL),
(9600170,'10.10.10.17','','0',NULL),
(9600171,'10.10.10.17','','0',NULL),
(9600172,'10.10.10.17','','0',NULL),
(9600173,'10.10.10.17','','0',NULL),
(9600174,'10.10.10.17','','0',NULL),
(9600175,'10.10.10.17','','0',NULL),
(9600176,'10.10.10.17','','0',NULL),
(9600177,'10.10.10.17','','0',NULL),
(9600178,'10.10.10.17','','0',NULL),
(9600179,'10.10.10.17','','0',NULL),
(9600180,'10.10.10.17','','0',NULL),
(9600181,'10.10.10.17','','0',NULL),
(9600182,'10.10.10.17','','0',NULL),
(9600183,'10.10.10.17','','0',NULL),
(9600184,'10.10.10.17','','0',NULL),
(9600185,'10.10.10.17','','0',NULL),
(9600186,'10.10.10.17','','0',NULL),
(9600187,'10.10.10.17','','0',NULL),
(9600188,'10.10.10.17','','0',NULL),
(9600189,'10.10.10.17','','0',NULL),
(9600190,'10.10.10.17','','0',NULL),
(9600191,'10.10.10.17','','0',NULL),
(9600192,'10.10.10.17','','0',NULL),
(9600193,'10.10.10.17','','0',NULL),
(9600194,'10.10.10.17','','0',NULL),
(9600195,'10.10.10.17','','0',NULL),
(9600196,'10.10.10.17','','0',NULL),
(9600197,'10.10.10.17','','0',NULL),
(9600198,'10.10.10.17','','0',NULL),
(9600199,'10.10.10.17','','0',NULL),
(9600200,'10.10.10.17','','0',NULL),
(9600201,'10.10.10.17','','0',NULL),
(9600202,'10.10.10.17','','0',NULL),
(9600203,'10.10.10.17','','0',NULL),
(9600204,'10.10.10.17','','0',NULL),
(9600205,'10.10.10.17','','0',NULL),
(9600206,'10.10.10.17','','0',NULL),
(9600207,'10.10.10.17','','0',NULL),
(9600208,'10.10.10.17','','0',NULL),
(9600209,'10.10.10.17','','0',NULL),
(9600210,'10.10.10.17','','0',NULL),
(9600211,'10.10.10.17','','0',NULL),
(9600212,'10.10.10.17','','0',NULL),
(9600213,'10.10.10.17','','0',NULL),
(9600214,'10.10.10.17','','0',NULL),
(9600215,'10.10.10.17','','0',NULL),
(9600216,'10.10.10.17','','0',NULL),
(9600217,'10.10.10.17','','0',NULL),
(9600218,'10.10.10.17','','0',NULL),
(9600219,'10.10.10.17','','0',NULL),
(9600220,'10.10.10.17','','0',NULL),
(9600221,'10.10.10.17','','0',NULL),
(9600222,'10.10.10.17','','0',NULL),
(9600223,'10.10.10.17','','0',NULL),
(9600224,'10.10.10.17','','0',NULL),
(9600225,'10.10.10.17','','0',NULL),
(9600226,'10.10.10.17','','0',NULL),
(9600227,'10.10.10.17','','0',NULL),
(9600228,'10.10.10.17','','0',NULL),
(9600229,'10.10.10.17','','0',NULL),
(9600230,'10.10.10.17','','0',NULL),
(9600231,'10.10.10.17','','0',NULL),
(9600232,'10.10.10.17','','0',NULL),
(9600233,'10.10.10.17','','0',NULL),
(9600234,'10.10.10.17','','0',NULL),
(9600235,'10.10.10.17','','0',NULL),
(9600236,'10.10.10.17','','0',NULL),
(9600237,'10.10.10.17','','0',NULL),
(9600238,'10.10.10.17','','0',NULL),
(9600239,'10.10.10.17','','0',NULL),
(9600240,'10.10.10.17','','0',NULL),
(9600241,'10.10.10.17','','0',NULL),
(9600242,'10.10.10.17','','0',NULL),
(9600243,'10.10.10.17','','0',NULL),
(9600244,'10.10.10.17','','0',NULL),
(9600245,'10.10.10.17','','0',NULL),
(9600246,'10.10.10.17','','0',NULL),
(9600247,'10.10.10.17','','0',NULL),
(9600248,'10.10.10.17','','0',NULL),
(9600249,'10.10.10.17','','0',NULL),
(9600250,'10.10.10.17','','0',NULL),
(9600251,'10.10.10.17','','0',NULL),
(9600252,'10.10.10.17','','0',NULL),
(9600253,'10.10.10.17','','0',NULL),
(9600254,'10.10.10.17','','0',NULL),
(9600255,'10.10.10.17','','0',NULL),
(9600256,'10.10.10.17','','0',NULL),
(9600257,'10.10.10.17','','0',NULL),
(9600258,'10.10.10.17','','0',NULL),
(9600259,'10.10.10.17','','0',NULL),
(9600260,'10.10.10.17','','0',NULL),
(9600261,'10.10.10.17','','0',NULL),
(9600262,'10.10.10.17','','0',NULL),
(9600263,'10.10.10.17','','0',NULL),
(9600264,'10.10.10.17','','0',NULL),
(9600265,'10.10.10.17','','0',NULL),
(9600266,'10.10.10.17','','0',NULL),
(9600267,'10.10.10.17','','0',NULL),
(9600268,'10.10.10.17','','0',NULL),
(9600269,'10.10.10.17','','0',NULL),
(9600270,'10.10.10.17','','0',NULL),
(9600271,'10.10.10.17','','0',NULL),
(9600272,'10.10.10.17','','0',NULL),
(9600273,'10.10.10.17','','0',NULL),
(9600274,'10.10.10.17','','0',NULL),
(9600275,'10.10.10.17','','0',NULL),
(9600276,'10.10.10.17','','0',NULL),
(9600277,'10.10.10.17','','0',NULL),
(9600278,'10.10.10.17','','0',NULL),
(9600279,'10.10.10.17','','0',NULL),
(9600280,'10.10.10.17','','0',NULL),
(9600281,'10.10.10.17','','0',NULL),
(9600282,'10.10.10.17','','0',NULL),
(9600283,'10.10.10.17','','0',NULL),
(9600284,'10.10.10.17','','0',NULL),
(9600285,'10.10.10.17','','0',NULL),
(9600286,'10.10.10.17','','0',NULL),
(9600287,'10.10.10.17','','0',NULL),
(9600288,'10.10.10.17','','0',NULL),
(9600289,'10.10.10.17','','0',NULL),
(9600290,'10.10.10.17','','0',NULL),
(9600291,'10.10.10.17','','0',NULL),
(9600292,'10.10.10.17','','0',NULL),
(9600293,'10.10.10.17','','0',NULL),
(9600294,'10.10.10.17','','0',NULL),
(9600295,'10.10.10.17','','0',NULL),
(9600296,'10.10.10.17','','0',NULL),
(9600297,'10.10.10.17','','0',NULL),
(9600298,'10.10.10.17','','0',NULL),
(9600299,'10.10.10.17','','0',NULL);
exit

Update the IP to your server IP by running the following command:

/usr/share/astguiclient/ADMIN_update_server_ip.pl –old-server_ip=10.10.10.17 (Click Enter for Y)
Next enter your server IP and press enter twice to chaneg it in the DB as show below:

updating server IP
Update Server IP

Step 5 – Code changes to ViciDial files

There are some files now that have to be patched in order to include the changes needed for confbrides to work. They are in the “extras/ConfBridge/” directory of the svn/trunk codebase. Lets copy the files over to where they are needed, this will depend on if you are using a single server or a cluster to where the files go. Here is a list of where they go:

Dialers:
/usr/share/astguiclient/ - 
- ADMIN_keepalive_ALL.pl.diff
- ADMIN_update_server_ip.pl.diff
- AST_DB_optimize.pl.diff
- AST_reset_mysql_vars.pl.diff
- AST_VDremote_agents.pl.diff
- AST_conf_update_screen.pl

Webservers:
/srv/www/htdocs/agc/ - 
- vicidial.php.diff
- vdc_db_query.php.diff
- manager_send.php.diff
/srv/www/htdocs/vicidial/ - 
- non_agent_api.php.diff

You can copy and paste the entire code below to get it all done
cd /usr/src/astguiclient/trunk/extras/ConfBridge/
cp * /usr/share/astguiclient/
cd /usr/share/astguiclient/
mv manager_send.php.diff vdc_db_query.php.diff vicidial.php.diff /var/www/html/agc/
patch -p0 < ADMIN_keepalive_ALL.pl.diff
patch -p0 < ADMIN_update_server_ip.pl.diff
patch -p0 < AST_DB_optimize.pl.diff
chmod +x AST_conf_update_screen.pl
patch -p0 < AST_reset_mysql_vars.pl.diff
cd /var/www/html/agc/
patch -p0 < manager_send.php.diff
patch -p0 < vdc_db_query.php.diff
patch -p0 < vicidial.php.diff

Step 6 – Add the confbridge keepalive and turn off the conf_update keepalive in crontab

A new screen session has been added called 'AST_conf_update_screen.pl'. This screen session replaces both the AST_conf_update.pl and AST_conf_update_3way.pl scripts. It checks both MeetMe and ConfBridge conferences for unnecessary channels and removes them. For instance if an agent does a Leave 3way and a few minutes later one of the remaining channels hangs up. This script will remove the remaining channel and free the conference for use by Vicidial. This screen session is optional for use with MeetMe but is required to be used with ConfBridge.
Add C to VARactive_keepalives
Add C to VARactive_keepalives
To enable this screen session you need to add a 'C' to the 'VARactive_keepalives' variable in the '/etc/astguiclient.conf' on your dialers, and comment out the following line from your crontab:

                ### updater for conference validator
                #* * * * * /usr/share/astguiclient/AST_conf_update.pl

You can configure the refresh interval for how often the screen session checks for unnecessary channels by changing "Conf Update Interval" in Admin -> Servers.

Step 7- Make the needed changes in ViciDial GUI

Login to the ViciDial Admin GUI and go to Admin > Servers and click on the server(s) that are dialers and change the conferencing engine to “CONFBRIDGE” as shown below:

Change conferencing Engine to CONFBRIDGE
Change conferencing Engine to CONFBRIDGE

Thats a lot to get through but now that its done your customers will no longer hear the “Water drop” or “bloop” sound that they do now and you’re ready for the future of Asterisk now that meetme has been deprecated. Thats it for now, you’re all done. Hopefully this helps those of you who are a little intimidated to try the change and like always, if you have any problems, feel free to visit our Skype live support with almost 200 Vicidial experts from around the world.

-Chris aka carpenox

How to – Use Firewalld via command line

Robots trying to hack in

How to – use Firewalld via command line

This short post is just going to briefly go over the more common commands you need in order to manage firewalld and make sure you keep your servers safe. This firewall works in conjunction with the dynamic portal for ViciDial as well as the built in whitelist initially named ViciWhite in the IP list area in Admin.

Dynamic portal
Dynamic portal

Systemctl and Firewalld

Enable firewalld

This makes sure that firewalld will be started automatically with the server.

systemctl enable firewalld

Start firewalld

After the firewalld service is enabled, you’ll need to start it manually the first time. This is how you would manually start firewalld if it were not already running.

systemctl start firewalld

Stop firewalld

When troubleshooting rules and connection issues, you may need to stop the fireawlld service momentarily. You can stop the service with the following command.

systemctl stop firewalld

Restart firewalld

If for some reason, you need to restart the service, you can do that with the systemctl restart command.

systemctl restart firewalld

Firewalld status

Checking the status of the service gives us the most meaningful and informative output. Here you can see whether the service is enabled, running, failed, or anything else.

systemctl status firewalld

In this example output, you can see that the service is enabled, active, and running on the server. If it were not running or in a failed state, this would be displayed.

[root@alma ~]# systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-01-22 22:50:32 EST; 1h 0min ago
Main PID: 808 (firewalld)
CGroup: /system.slice/firewalld.service
└─808 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Managing Firewalld and Configuring Rules

Now that we have firewalld running, we can get down to set the configuration. We can open ports, allow services, whitelist IPs for access, and more. In all of these examples, we include the –permanent flag. This is important to make sure a rule is saved even after you restart firewalld, or reboot the server. Once you’re done adding new rules, you need to reload the firewall to make the new rules active.

Add a Port for TCP or UDP

You do have to specify TCP or UDP and to open a port for both. You will need to add rules for each protocol.

firewall-cmd --permanent --add-port=22/TCP
firewall-cmd --permanent --add-port=53/UDP

Remove a Port for TCP or UDP

Using a slight variation on the above structure, you can remove a currently open port, effectively closing off that port.

firewall-cmd --permanent --remove-port=444/tcp

Add a Service

These services assume the default ports configured within the /etc/services configuration file; if you wish to use a service on a non-standard port, you will have to open the specific port, as in the example above.

firewall-cmd --permanent --add-service=ssh
firewall-cmd --permanent --add-service=http

Remove a Service

As above, you specify the remove-service option, and you can close off the port that is defined for that service.

firewall-cmd --permanent --remove-service=mysql

Whitelist an IP Address

To whitelist or allow access from an IP or range of IPs, you can tell the firewall to add a trusted source.

firewall-cmd --permanent --add-source=192.168.1.100

You can also allow a range of IPs using what is called CIDR notation. CIDR is outside the scope of this article but is a shorthand that can be used for noting ranges of IP addresses.

firewall-cmd --permanent --add-source=192.168.1.0/24

Remove a Whitelisted IP Address

To remove a whitelisted IP or IP range, you can use the –remove-source option.

firewall-cmd --permanent --remove-source=192.168.1.100

Block an IP Address

As the firewall-cmd tool is mostly used for opening or allowing access, rich rules are needed to block an IP. Rich rules are similar in form to the way iptables rules are written.

firewall-cmd --permanent --add-rich-rule="rule family='ipv4' source address='192.168.1.100' reject"

You can again use CIDR notation also block a range of IP addresses.

firewall-cmd --permanent --add-rich-rule="rule family='ipv4' source address='192.168.1.0/24' reject"

Whitelist an IP Address for a Specific Port (More Rich Rules)

We have to reach back to iptables and create another rich rule; however, we are using the accept statement at the end to allow the IP access, rather than reject its access.

firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.168.1.100" port protocol="tcp" port="3306" accept'

Removing a Rich Rule

To remove a rich rule, use the option —remove-rich-rule, but you have to fully specify which rule is being removed, so it is best to copy and paste the full rule, rather than try to type it all out from memory.

firewall-cmd --permanent --remove-rich-rule='rule family="ipv4" source address="192.168.1.100" port protocol="tcp" port="3306" accept'

Saving Firewall Rules

After you have completed all the additions and subtraction of rules, you need to reload the firewall rules to make them active. To do this, you again use the firewall-cmd tool but using the option –reload.

firewall-cmd --reload

Viewing Firewall Rules

After reloading the rules, you can confirm if the new rules are in place correctly with the following.

firewall-cmd --list-all

Here is an example output from the –list-all option, you can see that this server has a number of ports, and services open in the firewall along with a rich rule (that forwards one port to another).

[root@alma ~]# firewall-cmd --list-all
public (default, active)
interfaces: enp1s0
sources: 192.168.1.0/24
services: dhcpv6-client dns http https mysql nfs samba smtp ssh
ports: 443/tcp 80/tcp 5900-5902/tcp 83/tcp 444/tcp 3260/tcp
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
rule family="ipv4" source address="192.168.1.0/24" forward-port port="5423" protocol="tcp" to-port="80"


Hopefully this will help a lot of you that end up just not using a firewall at all because it intimidates you not knowing how to use it correctly. Well, I’ve just eliminated that excuse, so now I want to see more of you securing your servers and dialer systems. Here is a few articles to get you started in the right direction.

This will show you how secure OpenSUSE LEAP
Securing CentOS, Alma or Rocky Linux

Here are some more articles in relation to VICIdial security for your servers

How to – Use the built in Dynamic Portal for Vicibox
How to – Turn on IP whitelist in Vicidial
How to – Use one dynamic portal for whitelisting and have it sync across an entire cluster
How to – Fix the firewall on Vicibox10


That’s it for this article, hopefully you guys take this serious because hackers, especially ransomware thieves are targeting dialer servers in particular for their schemes, such as using the VoIP to call their victims to either trick them into downloading files or threatening them over the phone with blackmail or other means. BazarCall is one of the more well known tools thats being used by the ransomware group called Ryuk.

Call Center Solutions For Every type of Business, based in the Cloud

Agent Interface

Call Center Solutions For Every type of Business, based in the Cloud

Credit: Written By Sajid Ahmad

CyburDial Realtime Screen to monitor your agents by listening in, whispering(the agent can hear you but customer can not) or barging the call to take it over.
CyburDial Realtime Screen

What is a cloud center cloud solution?

Call center cloud solutions are the new age way to keep people working mainly when COVID hit. its to replace the more commonly known on-premise locations and having to house equipment for placing and receiving calls. It has given the call center world basically no restrictions when it comes to location, people they want to hire that don’t live locally and so many more benefits that it just doesn’t make sense not to switch to a cloud based phone system such as CyburDial.

In this, the cloud call focus can use the innovation of cloud communication that shows up with coordinated and fundamental elements, for example, IVR to give that expert voice edge to your clients, a live board to see an unmistakable image of business calls, call directing for sending the right calls to the right divisions or specialists.

This multitude of advantages show up with a virtual number or a complementary number. There are different numbers planned behind a complementary number. It makes more straightforward to advance significant calls to the right specialists or divisions.

Aside from these fundamental highlights, complementary numbers assist clients with contacting the business clients.

In the current day’s electronic world, cloud call focus arrangement gives simple admittance to the administrations which are fundamental for business correspondence like fast availability, better effort, and quick client question redressal.

These days if crowding into a physical location call center are over!

What are the advantages of a cloud call focus arrangement?

Cloud call focus arrangement collects the capability of a business to effort its clients with next to no geological limitations. As of not long ago, the old conventional framework used to give restricted client outreach choices that too with the adequate sum put resources into the establishment of the disconnected equipment.

Use CyburDial on any device
You can use CyburDial from any device with no additional downloads needed

Be that as it may, the cloud communication arrangement will provide your business with every one of the advantages of a call center, but without any burdens jor overhead that come with a physical location.

-:- Cloud Based Contact Center Solution -:-

Here are a few advantages that our cloud call focus arrangement will give your business and enable you to set up a cloud-based smaller than normal call community for your call taking care of:

1. More straightforward versatility:

Cloud call focus arrangement permits your business to scale and extend with no additional venture on cumbersome equipment. In situations where organizations need to add more specialists to the group or move to an alternate area or a nation out and out, Call center solutions on cloud focuses arrangements will not end up being oppressive.

2. Upgraded unwavering quality:

With quick cloud-based call center arrangements, your business can profit quickly while giving your clients the chance to have there goals met with almost zero wait time. Making them happy ends with you acquiring more clients via word of mouth w mean mmhich we all know it’s the best type of marketing on the planet.

3. Savvy module:

Setting up a contact center solution such as CyburDial is a way less feverish strategy than introducing massive on-premise equipment. It’s totally savvy on the grounds that your business can save that ridiculous amount you would normally spend on hardware for a local office and use it to put resources into the establishment and marketing for massive equipment.

4. First class security:

Cloud based contact center solutions offer more dependable information security as it is totally put away upheld in the cloud which empowers information encryption, ongoing administrator control, and server security with an intense firewall solution that totally locks down the system, but at the same time has something called the Dynamic portal which allows agents to authenticate their IP on the server in order to gain access. Tried approval is urgent with regards to the cloud call focus, in this way, it accompanies different security levels.

Dynamic portal
Dynamic portal

5. Insignificant margin time:

Customarily introduced equipment is inclined to separate in vital circumstances and normally takes more than an adequate measure of time in handling. In any case, with a cloud based contact center solution’ like CyburDial, it has immaterial personal time and guarantees no call misfortune for your business.

6. State-of-the-art framework mix:

Dissimilar to conventional equipment, cloud communication works with your clients to remain refreshed with current mechanical updates and enable your group to acquire the necessary computerization and improvement. Your business can then effectively overhaul and upgrade your contact center to be in-accordance with the ongoing TCPA changes and more importantly, to keep up with the times.

Data Center
Data Center

7. Execution investigation and information accessibility:

You can track, record and investigate the exhibition of your representatives with definite reports benefited by cloud based contact center. It is planned in a manner to furnish you with an easy to understand insight alongside thorough reports of recorded and convenient followed calls.

8. Business accessibility: 

Your business can undoubtedly guarantee 24*7 accessibility for your clients with a cloud-based call place arrangement. With customary equipment nonstop accessibility is hard to satisfy as it anticipates that the group should remain on the PC consistently. Consequently, with cloud innovation, progression in client care administration is altogether guaranteed by your business.


Hopefully this short article has given you some new insight and a better perspective on why you should change from those old bulky hard phones that take up room on your desk and switch to a system that works right on the computer you use all day anyways, or better yet, pull it up on your iPad, your iPhone, Android, tablet, surface or literally any smart device with a browser that you can think of, even your smart TV. Let’s leave the past and join the future, come join us as we revolutionize the telecommunications world by bringing in a solution that not only handles phone calls, but so much more and we can also integrate any CRM you already use to where they will communicate back and forth and sync your information across both platforms seamlessly. Oh, and one last thing i forgot to mention, CyburDial isn’t something you are going to rent from us or pay a ridiculous per seat charge($150+ per seat) like these other dialer systems(which we do have seat rentals available for startups if you prefer), but CyburDial is a custom built dialer system that you will own! That’s right, you buy the cloud based server which we will show you some options to pick from, we install our custom system on your server and then handle all your integrations for CRM’s and anything else you may need to combine with your new state of the art technology. We then provide you with learning material such as a 600 page manual, videos demonstrating how to use most of the more common features you will need to know about, an in depth training over zoom for both your agents and then your managers, making sure you have everything you need to know, in order to be successful in your business, but that’s not all, we are also going to provide you with 90 days support included in your buildout, to answer any questions as they come along, hop on a zoom call with you and/or your team to show you live how to do something your unsure of, we will create some loom videos for anything that’s confusing any of your staff, as well as 24 hour access to our helpdesk to make sure someone is ALWAYS around to help you. So what are you waiting for? Get ahold of us now by calling us at 725-22-CYBUR – Emailing us at sales@dialer.one or if you’d like to talk to someone over chat, click the little chat box in the corner or come join our Live Support Channel on Skype which has people from over 45 countries covering 6 continents where the passing of knowledge and the generosity of men and women helping each other is in no short demand because when you join CyburDial, its not just one of the best decisions you’ll make by becoming business associates, but you also become family.

-Chris aka carpenox

Tips and Tricks – Uncommon Issues

90 Day Callback filter

Tips and Tricks – Uncommon Issues

8/21/2022- carpenox

In this article, I am going to go over some of the more often asked questions and how to fir them. If you still don’t understand, feel free to join our live chat. Also included will be some pretty useful ways to use Linux’ built in tools for your benefit.

1) Lets start easy with “htop”. This command, “htop” will display your current drain on system resources and show you where you stand. Take a look at the picture below:

htop
htop

2) Creating a filter to only call certain status every 90 days only

This next one can be very useful for those of you that need to drop certain dispositions from being called for a set time period, for this example, we’re gonna say 90 days for any lead marked with NI(not interested). You need to create a “filter” and paste the following mysql query which can be altered to fit your needs: “status IN (‘NI’) and modify_date < NOW() – INTERVAL 90 DAY OR status IN (‘N’,’NA’ ,’B’,’AB’,’DROP’,’PDROP’,’NEW’,’NP’,’NANQUE’,’ADCT’)”. The first status “NI” can be set to anything you want, like ‘ADCT’ to go back and see if those temporary disconnected numbers are back or whatever dispo you’d like to go back to. You can also change the 90 to however many days you want to wait before dialing those again and finally, you can change from the right side of the query where it says “status IN (‘N’,’NA’ ,’B’,’AB’,’DROP’,’PDROP’,’NEW’,’NP’,’NANQUE’,’ADCT’)” and either add to it or remove from it, etc. Here is a small example of the one used in this article:

filter
90 day filter

3) Is your audio store not accepting new files? Does it keep telling you improper format? Not a problem, we need to run a few commands in the Linux cli to get this fixed up. Copy and paste the code below:

cd /usr/share/astguiclient/
sed -i 's/wgetbin -q/wgetbin --no-check-certificate -q/g' ADMIN_audio_store_sync.pl

/usr/share/astguiclient/ADMIN_audio_store_sync.pl --debugX


chmod -R 777 audio folder in /var/www/html/audio_folder (somehting like ndt7h4rr8fynf3y8er)
chown -R apache:apache /var/www/html/audio_folder (somehting like ndt7h4rr8fynf3y8er)

4) Need to change your recording links from http to https? Try the following query in mysql:

UPDATE recording_log
SET location = REPLACE(location, 'http://127.0.0.1/', 'https://127.0.0.1/')
WHERE location LIKE '%http://127.0.0.1/%';

you can also run this with archive_log instead of recording_log and the Ip's can be switched out with FQDN's or domain names.

5) Here is a simple way to change the passwords for all users as well as a couple variants to get more specific:

update vicidial_users 
set pass="newpass";  ###update all users password

update vicidial_users 
set pass="newpass" 
where user between 7000 AND 7015;  ##update users that are only between 7000 and 7015

update vicidial_users 
set pass="newpass"
 where user_level between 1 AND 8;  ##change password for all users between levels 1 and 8, dont change level 9 passwords

That’s it for today, I’ll add some more tomorrow and the days to follow so stay tuned.

Thanks, Chris aka carpenox


9/5/2022 – Adding a few more

6) Speed up call handling for agent only or dial servers only. (no web/DB)

If you are using servers where agents only log in and handle calls, but no calls are placed out from it, then you can use the new delay options on those servers to enhance efficient operations. The –autodial-delay=X option in the ADMIN_keepalive_ALL.pl script will allow you to set the delay to 100 milliseconds for these agent-only servers(the default is 2500ms). Lowering the delay for agent-only servers makes the auto-dial FILL process more responsive to the changes in the agent state on the agent-only servers which will enhance how your cluster operates. You can also use the –adfill-delay=X CLI option for the ADMIN_keepalive_ALL.pl script on the server that is running the FILL process and lower it as well if you have a larger cluster. The default of that process is also 2500ms, but you can lower it down to 500ms if needed.

7) Are all your calls showing DISPO?

This is usually because your php time doesnt match the system. You can change it by editing /etc/php.ini for CentOS/Alma/Rocky or /etc/php7/php.ini for Leap. Just change it to match and you’ll be good to go.

8) How can I move a lead based on how many times its been called or how old the lead is?

The answer is yes, you can use the script named dispo_move_list.php, that you can find in your /usr/src/astguiclient/trunk/extras folder on your web server. It has a few different choices you can use that you can see below:

# Definable Fields: (other fields should be left as they are)
# - log_to_file - (0,1) if set to 1, will create a log file in the agc directory
# - sale_status - (SALE---XSALE) a triple-dash "---" delimited list of the statuses that are to be moved
# - exclude_status - (Y,N) if set to Y, will trigger for all statuses EXCEPT for those listed in sale_status, default is N
# - talk_time_trigger - (0,1,2,3,...) if set to number greater than 0, will only trigger for talk_time at or above set number, default is 0
# - called_count_trigger - (1,2,3,...) if set to number greater than 0, will only trigger for called_count at or above set number, default is 0
# - list_id_trigger - (101,...) if set to number greater than 99, will only trigger for list_id equal to the set number(NOTE: list_id must be sent), default is disabled
# - list_id - (101,...) if you want to use list_id_trigger then this must be set: "list_id=--A--list_id--B--", default is disabled
# - lead_age - (1,2,3,...) if set to number greater than 0, will only trigger for a lead entry_date this number of days old or older, default is 0
# - new_list_id - (999,etc...) the list_id that you want the matching status leads to be moved to
# - reset_dialed - (Y,N) if set to Y, will reset the called_since_last_reset flag on the lead
# - populate_sp_old_list - (Y,N) if set to Y, will populate the security_phrase field of the lead with the old list_id
# - populate_comm_old_date - (Y,N) if set to Y, will populate the comments field of the lead with the date and time when the lead was last called
# Multiple sets of statuses:
# - sale_status_1, new_list_id_1, reset_dialed_1, exclude_status_1, called_count_trigger_1 - adding an underscore and number(1-99) will allow for another set of statuses to check for and what to do with them
# - multi_trigger - (talk-age...) if set to 1 or more of "talk,age,list,count,status"(separated by '-') it will check for only one of included triggers to be met for the lead to be moved, (does not work with multiple sets)

9) Can I record my agents outside of ViciDial or once calls are transferred outside the system?

Yes, you can. You have to use an agi script called agi-NVA_recording.agi which was made for this purpose. Here are some triggers for it below:

# ; 1. logging output (NONE|STDERR|FILE|BOTH)
# ; 2. the ViciDial user ID, if empty it defaults to accountcode(usually phone extension) or vicidial_live_agents user who launched the call
# ; 3. log this call in user_call_log (Y|N) default N
# ; 4. log this call in call_log (Y|N) default N, ONLY NEEDED FOR INBOUND AND INTERSYSTEM CALLS!!!
# ; 5. audio record this call (Y|N) default N
# ; 6. double-log this call in call_log (Y|N) default N, ONLY NEEDED FOR INBOUND CALLMENU FORWARDED CALLS!!!
# ; 7. play the recording ID of this call before recording starts
# ; 8. include the recording ID in the filename
# ; 9. search vicidial_list for phone number dialed (Y|N) default N, assumes 10 digit phone numbers
# ; 10. if 9 is Y, this is search method (ALLLISTS|PHONE) default ALLLISTS, search all lists, use phone setting, CURRENTLY DOES NOTHING
# ; 11. error out and end call if phone number is not found (Y|N) default N
# ; 12. run the phone entry's NVA Call URL (Y|N) default N
# ; 13. if 9 is Y, and phone number is not found, insert into phone's NVA List ID (Y|N) default N
# ; 14. if 13 is Y, override phone's NVA List ID with this list ID when lead is inserted
# ; 15. if 13 is Y, override phone's NVA Phone Code with this phone code when lead is inserted
# ; 16. if 13 is Y, override phone's NVA Status with this status when lead is inserted

Here as an example to give you an idea how it looks:
# ;custom dialplan entry example: (similar to the defaultlog Call Menu)
#exten => _X.,1,AGI(agi-NVA_recording.agi,BOTH------Y---N---Y---N---N---N)
#exten => _X.,n,Goto(default,${EXTEN},1)
#exten => _X.,n,Hangup

10) Why don’t calls to Canada show the caller ID? (They display those weird V435345874353457353 numbers)

It’s because Canadian telco’s accept any CID that is sent and Vicidial sends this UID first which is ignored by American telco’s and it was a hard solution for me to find, so here it is for you guys. It uses a dialplan that was given to me by The dialplan God – Striker24/7.

exten => _81NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _81NXXNXXXXXX,n,NoOp(MY CALLERD !!!! ${CALLERID(all)})
exten => _81NXXNXXXXXX,n,Set(_CALLERID(num)=${CALLERID(num)})
exten => _81NXXNXXXXXX,n,Dial(IAX2/ASTloop/9${EXTEN:1},,tTo)
exten => _81NXXNXXXXXX,n,Hangup()

exten => _91NXXNXXXXXX,1,Set(CALLERID(num)=${CALLERID(num)})
exten => _91NXXNXXXXXX,n,Set(CALLERID(name)=${CALLERID(num)})
exten => _91NXXNXXXXXX,n,NoOp(MY CALLERD !!!! ${CALLERID(all)} ${CALLERID(num)} ${CALLERID(name)})
exten => _91NXXNXXXXXX,n,Dial(SIP/${EXTEN:1}@TILTX,,tTo)
exten => _91NXXNXXXXXX,n,Hangup()

Well thats it for today, hopefully these help someone.

-Chris aka carpenox

How to – Create an IVR for inbound calls

IVR

How to – Create an IVR for inbound calls

In this article I am going to over how to create an inbound call menu or IVR (Interactive Voice Response) for ViciDial which will help reduce your drop percent to help you legally within the 3% drop rate for the USA or 5% drop rate for Canada, by way of the FCC guidelines.

Step 1 – Create the call menu

Login to the admin GUI for ViciDial and click “inbound” then “add a new call menu” as shown below., then name your call menu. (For this example, I named it IVR)

add a new call menu
Add a new call menu

Step 2 – Setup your basic IVR options

Now we are going to setup the top portion on the call menu/IVR. Assuming you have already created your audio recording for your IVR and added it to the audio store, select that file at the “Menu Prompt” option. You can also fill out your timeout prompt, invalid prompt and other options as shown below:

IVR Options
IVR Options

Step 3 – Create your IVR options

Now we will select a few common IVR options to add to your call menu. For this example I have given options to 1) leave a voicemail message, 2) be transferred to a live agent, 3) Be added to the Do Not call list or #) to play the options again. See below:

IVR selections
IVR Selections

Step 4 – Route unanswered Inbound calls to IVR

The final step is to add this IVR/Call menu to your inbound calls when your agents aren’t available. For this you need to go to your inbound ingroup and change your “call time” and no agent queueing/after hours options to reflect the picture below:

Set the call menu for the inbound calls

This articles assumes you know how to already setup the other parts needed for this such as creating audio recordings, uploading them to the audio store and setting up inbound groups. If you have any questions feel free to visit our skype live chat. Hopefully this helps some of you that have been asking me about this.

-Chris aka carpenox

How to – Setup Email for ViciDial reports and voicemail

email vicidial

How to – Setup Email for ViciDial reports and voicemail

This article will go over how to setup your email configuration on your server in order to get reports from ViciDial or to receive voicemail to email notifications and recordings. Gmail recently changed the way their security is handled so some changes need to be made in order for your emails to go through. You can alter the config below for any email service you may use.

Step 1 – Edit your postfix config file

Ok so first you need to edit your postfix configuration by editing main.cf and adding a few lines to the bottom of it.

nano /etc/postfix/main.cf
### Now paste the following lines to the bottom: ###
relayhost = [smtp.gmail.com]:587
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = lmdb:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous
smtp_sasl_mechanism_filter = plain
smtp_use_tls = yes

Step 2 – Create a Gmail APP Password

  1. Go to Gmail and log in to your account.
  2. Now, in the upper-right corner, click the Home Account icon. In the open wizard, click “Manage my Accounts.
  1. You will be redirected to Gmail Settings. In the left tab, click Security, and then click ‘2-step verification’ in the ‘Signing into Google’ section.Click on verification
  2. The 2-step verification window will appear on the screen, click ‘Get started.’2-step verification window
  3. In the next step, Google will ask you to use your phone as your second sign-in step. Click ‘Try it Now’ to move ahead. You will be asked to log in to Gmail again, and a notification will appear on your phone screen to confirm the sign-in, click Yes.Notification will appear on your phone screen to confirm the sign-in
  4. After giving access from your phone, Google will ask you to add a backup option, enter your phone number, and click Send.Add a backup option
  5. A code will be sent to your phone to confirm the login, enter the code in the opened window and click ‘Next.’A code will be sent to your phone

2-step verification has been enabled. Now, you can easily create an App Password to login to third-party apps.

Creating App Passwords

  1. To create the App Password after enabling 2-step verification, go to ‘Manage your Account’ from the home tab.
  2. Now, in managing accounts, click the Security tab in the left pane, and then scroll down to ‘Signing to Google.’
  3. Here, you’ll see the App Passwords option, click over it. You will be asked to sign in again to your Gmail account.Sign in to your Gmail account
  4. After signing in, select the type of app and device for which you want to generate an app password and click Generate.Select the type of app and device
  5. The App Password will be created; you can copy it to the clipboard, and click ‘Done.’App Password will be created

That’s how you can create App Password for your Gmail account. Now, you can use this Password to login to Gmail with your ViciDial server.

Step 3 – Edit your sasl_password file

Now you need to edit your sasl_password file as shown below:

nano /etc/postfix/sasl_passwd
### Alter the line below with your username and password ###
[smtp.gmail.com]:587 youremail@gmail.com:password

That’s all there is to it, now set your email account on your voicemail boxes or automated reports in ViciDial and you should be good to go.

I hope this helps.

-Chris aka carpenox

How to – Use CID groups

CID Groups

How to – Use CID groups

This article is going to go over the method to best setup CID groups and the different ways to configure each option available for them including statefill, statelookup and creating auto rotators. This will assume you know how to add DID’s to the system which is fairly easy. So the first thing you need to do is create the CID group as defined below:

Step 1 – Create CID group

Within the ViciDial admin gui go to the Admin section then to CID groups

CID groups
CID Groups

Once you are here, just click “Add a CID Group”:

Add a CID group

The first one we will create is for state lookup method, define “AREACODE” as the group type like shown below:

CID group - state lookup
CID group – State lookup

hit submit and you’ll see it looking like the below picture

CID Group added

Step 2 – Add the DID’s to the CID Group

Next, we will be using the admin utilities to add your DIDs to the CID Group. Go to the “Reports” page and scroll down to the bottom to click on “Admin utilities” then click on “Admin bulk Tools”

Click Admin Utilities

click Admin Bulk Tools

Now scroll down to “CID Groups and AC-CID Bulk Add” and add your DID’s, selecting “state lookup” will assign each number with its area code to the proper state its from, selecting “statefill” will automatically add every area code for each state you have a DID for with separate entries for each area code which is a really nice option to ensure local presence in some fashion even if you don’t own DID’s from every area code.

Add DID to the CID group

When you choose statefill youll see the same number submitted many times, this is normal

statefill
StateFill Option

After doing this you’ll notice it filled it every area code for this example I did it for Florida, and even though I only entered 5 area codes, it filled in these 5 numbers for every area code in Florida:

Area Code Statefill

Step 3 – Assign CID group to your campaign

Now you just have to assign the newly created CID group to the detail view of your campaign as shown below, make sure you set “Custom CallerID:” to Y

assign cid group to campaign
Assinging CID Group to campaign

Now I will show you how to create an auto rotating CID group which will rotate all the DID’s added to this group based on intervals you can choose. Complete step one again but choose “None” for the “CID Group Type” as shown below”

Auto Rotator - vicidial
Create CID Group for Auto Rotator

Once your hit submit, choose how often you want the DID’s to change, a good starting point is every 5 minutes or 35 calls as shown below:

auto rotator
Set intervals for auto rotator

Go back and complete step 2 again using the “state lookup” method and assign the CID Group to the campaign, now your DID’s will auto rotate, I hope you have enjoyed this tutorial and like always, if you have any questions, feel free to join our Live Support on Skype.

I hope this helps

-Chris aka carpenox

How to – Add conferences for add on servers to a cluster

vicidial conferences

How to – Add conferences for add on servers to a cluster

This article will show you how to add additional servers to your cluster and make sure all the conferences are also added. Its just a few simple steps needed to have it done for you.

Step 1 – Adding the second server(or 3rd, 4th, 5th, whatever)

There is a SQL script already created that does all the hard work for you, just follow the commands below:

mysql -A asterisk
\. /usr/src/astguiclient/trunk/extras/second_server_install.sql
vicidial conferences
This should be the output you see if done correctly

Step 2 – Updating the IP from 10.10.10.16 to your new server IP

For this part, there is a perl script that will update the conferences and vicidial conferences as well as the new server that was added to your GUI as “TESTast”. Just copy and paste the following line into your Linux CLI:

/usr/share/astguiclient/ADMIN_update_server_ip.pl --old-server_ip=10.10.10.16

Then make sure you add your IP to the third question it asks you as shown below:

vicidial conferences
Changing the server IP

Step 3 – Run the install.pl script

Now we need to run the install.pl script to connect the second server to DB server

cd /usr/src/astguiclient/trunk
perl install.pl

Make sure when you get to the DB server question you input your DB server IP(where the blue arrow is)

perl install.pl
Change DB server IP

Step 4 – Change the name of the server in the ViciDial GUI

Make sure to change the name of your server and update the Asterisk version and trunks

Change TESTast to your new server name
asterisk
Change your asterisk version and trunks

Thats all there is to it, you should now have your second server added to your cluster. IF you have any questions feel free to comment here or stop by our Skype Live support