miércoles, 17 de noviembre de 2021

Zypper Cheat Sheet

https://en.opensuse.org/images/1/17/Zypper-cheat-sheet-1.pdf 

lunes, 15 de noviembre de 2021

O leads on the hooper

Postby mcargile » Wed Jun 02, 2010 9:36 am

There are three main things that can prevent leads from loading into the hopper when the server is setup and running correctly.

1. There are no leads in the local call time you have specified. Remember this is local to the leads location. So if you have it set to 12pm to 5pm and it is 9am where all your leads are it will not load leads. Change the local call time for the campaign.

2. No dialable Dial statuses. If your campaign only has NEW set as a dial status and you have no leads in your list that are NEW it wont be able to load leads. Add other dial statuses to the campaign.

3. All leads with a Dial status allowed by the campaign are marked as CALLED. Vicidial will only call leads that are set to NOT CALLED in the list. Reset the list and the leads will be marked as NOT CALLED. Note, resetting the list will NOT change the dial statuses just the called status for a lead.

If none of these help there is most likely something wrong on your server, or you are using an advanced feature of Vicidial (lead filters, lead recycling, etc) and should read up on it more before continuing.
Michael Cargile | Director of Consulting | ViciDialGroup | www.vicidial.com

The official source for VICIDIAL services and support. 1-888-894-VICI (8424)
mcargile
Site Admin
 
Posts: 571
Joined: Tue Jan 16, 2007 10:38 am

 

http://www.vicidial.org/VICIDIALforum/viewtopic.php?t=11596

domingo, 31 de octubre de 2021

PostalCode or State based dialing

 

Re: PostalCode or State based dialing

Unread postby mflorell » Sat Oct 30, 2021 5:56 pm

Yes, you can for postal code, but not for state, because several states are split by timezones so it wouldn't work very well.

You can switch your whole system to use postal code time-zone encoding, or just do it per list. Either way, you will need to modify the crontab entry for the GMT-offset script to do so:

For whole system by postal-code:
ADMIN_adjust_GMTnow_on_leads.pl --debug --postal-code-gmt

For per-list choice encoding:
ADMIN_adjust_GMTnow_on_leads.pl --debug --list-settings

miércoles, 27 de octubre de 2021

VICIdial recording folders

 Stages:


1: /var/spool/asterisk/monitor - During the call (representing "don't mess with this", usually a virtual drive for speed)
2: /var/spool/asterisk/monitorDONE - After the call (representing "ok, process this")
3: /var/spool/asterisk/monitorDONE/ORIG - After compression, this file contains the "now redundant" uncompressed file. Can be deleted immediately. but keep the folder, just delete the files inside.
4: /var/spool/asterisk/monitorDONE/MP3 - After compression, the MP3 is dropped here indicating "ready for permanent storage" (this is a TEMPORARY folder, files here will not stay long)
5: /var/spool/asterisk/monitorDONE/FTP - After the FTP process pushes the file to an FTP service, the MP3 file is moved from MP3 to FTP to indicate archiving has completed. If everything worked as planned, this file is now redundant.
6: /var/spool/asterisk/monitorDONE/FTP2 - If, however, you have a "redundant backup" configured and are pushing files to a 2nd FTP server, the ".mp3" that was in the FTP folder will get pushed to the 2nd FTP service, and then the file will be moved from FTP to FTP2 indicating that process has completed as well.

The recording scripts in the crontab manage the movement via FTP and FTP2. Each script has its own options (avilable by running the script with "--help" after it) and notes in the trunk /DOCS/ folder and manual.

https://vicidialforum.com/threads/recordings-directory.20646/

VICIdial filter

Re: How to filter out specific local call time hours?

Unread postby mflorell » Mon Oct 25, 2021 4:20 pm

We don't really have a single reference for filter examples, but there are probably dozens spread out through the Forums. Here are a few:

Below are several examples of Filters that can be used to further limit VICIdial outbound calling

72 hour block on auto-Answering-Machine detected calls -
This specific example was used to comply with the UK's OFCOM auto-dialing regulations to not call back auto-detected answering machines within 3 days of the last attempt:
( ( (status='AA') and (last_local_call_time < CONCAT(DATE_ADD(CURDATE(), INTERVAL -3 DAY),' ',CURTIME()) ) ) or (status != 'AA') )

Two examples for blocking areacodes -
These examples are for two areacodes in Puerto Rico:
(left(phone_number,3) NOT IN('787','939'))
(phone_number NOT LIKE '787%' AND phone_number NOT LIKE '939%')

Exclude a list of cities:
(city NOT IN('london','paris','tampa'))

Include only specific states:
state IN('FL','NY','CA')

Do not call NI(Not Interested) leads for 7 days
( ( (status='NI') and (last_local_call_time < CONCAT(DATE_ADD(CURDATE(), INTERVAL -7 DAY),' ',CURTIME()) ) ) or (status != 'NI') )

No more than one call per lead per 24 hours:
(last_local_call_time < CONCAT(DATE_ADD(CURDATE(), INTERVAL -1 DAY),' ',CURTIME()) )

Multiple filters in one -
This filter was designed to limit the call attempts, states and time zones of leads:
called_count IN('7','8','9') and state NOT IN('CA','OR','WA') and gmt_offset_now IN('-4','-5')

This Filter would exclude the 12-oclock hour for EST(Eastern Standard Time) leads on an EST-configured system, during standard time only(not during daylight savings time):

( (hour(now()) <= 11) and (hour(now()) >=13) and (gmt_offset_now='-4.0') )
mflorell
Site Admin
 
Posts: 17877
Joined: Wed Jun 07, 2006 3:45 pm
Location: Florida

lunes, 25 de octubre de 2021

Regarding Server Requirement

 

Re: Regarding Server Requirement

Postby mflorell » Mon Oct 25, 2021 9:51 am

You will definitely need a cluster.

I would recommend:
1 dedicated database server
1 dedicated web server
5-10 dialers

The database server should be a dual-quad-core CPU with 16+GB RAM and a fast drive system(preferably SSD drives in a RAID 10 on a MegaRAID card)
The webserver and dialers can be single-quad-code CPUs with 8GB RAM and standard drives

domingo, 17 de octubre de 2021

Modify vicidial realtime report

 


If you are going to just hard-code the new column, you should only need to modify the AST_timeonVDADall.php script. If you want to make it an option you will also need to modify the realtime_report.php script.

http://www.vicidial.org/VICIDIALforum/viewtopic.php?f=2&t=41049&sid=520fd832a108a0a94a32622d2030c61b

martes, 12 de octubre de 2021

Re: Regarding SVN upgrade impact

 

Re: Regarding SVN upgrade impact

Postby mflorell » Thu Oct 07, 2021 6:19 am

As long as you follow the instructions in the UPGRADE document, and upgrade and install the same updated VICIdial code on every server in your cluster you should be fine.

We recommend upgrading the DB schema first, then the webserver then the dialers. Making sure to reboot the dialers after they have been upgraded.

viernes, 1 de octubre de 2021

change time zone

 


1) change system time on yast









2) change time zone on php


/etc/php7/cli/php.ini

/etc/php7/apache2/php.ini



[Date]

; Defines the default timezone used by the date functions

; http://php.net/date.timezone

date.timezone = America/Los_Angeles


3) reboot


jueves, 30 de septiembre de 2021

Real time report not counting time on pause or closer status

 


Postby manny » Sun Mar 27, 2011 6:22 pm

Done!

I just added
CODE: SELECT ALL
[Date]
; Defines the default timezone used by the date functions
date.timezone = America/Mexico_City


reboot, and all was back to normal, counting the time in time hehe,

Thanks a LOT!!

jueves, 16 de septiembre de 2021

Vicidial phone alias

 Postby mflorell » Sun Sep 26, 2010 3:42 pm

Let's say you have 3 servers:
10.0.0.11
10.0.0.12
10.0.0.13

and you have an agent phone you want to phone-load-balance-login across all three servers, you would need to create a phones entry for that phone on each server with a different login:
101a -> 10.0.0.11
101b -> 10.0.0.12
101c -> 10.0.0.13

Then you go into to add a new alias(101x) for this set of phone logins which has this as the extension:
101a,101b,101c

Then the agent logs in with 101x as the phone login and tada, it works!

viernes, 10 de septiembre de 2021

fail2ban


jail.conf and jail.local 

backend =  systemd



# JAILS
#
[asterisk-udp]

enabled  = true
filter   = asterisk
port     = 5060,5061
protocol = udp
#logpath  = /var/log/asterisk/full
logpath  = /var/log/asterisk/fail2ban2
action   = iptables-allports[name=recidive, protocol=all]



[ssh-iptables]

enabled  = true
filter   = sshd
action   = iptables[name=SSH, port=ssh, protocol=tcp]
           sendmail-whois[name=SSH, dest=you@mail.com, sender=fail2ban@mail.com]
logpath  = /var/log/messages
maxretry = 5



//////////////////////////


filter.d/asterisk.conf file for Asterisk 1.8:

# Fail2Ban configuration file
#
#
# $Revision: 251 $
#

[INCLUDES]

# Read common prefixes. If any customizations available -- read them from
# common.local
before = common.conf


[Definition]

#_daemon = asterisk

# Option:  failregex
# Notes.:  regex to match the password failures messages in the logfile. The
#          host must be matched by a group named "host". The tag "<HOST>" can
#          be used for standard IP/hostname matching and is only an alias for
#          (?:::f{4,6}:)?(?P<host>\S+)
# Values:  TEXT
#
# Asterisk 1.8 uses Host:Port format which is reflected here

failregex = NOTICE.* .*: Registration from '.*' failed for '<HOST>:.*' - Wrong password
            NOTICE.* .*: Registration from '.*' failed for '<HOST>:.*' - No matching peer found
            NOTICE.* .*: Registration from '.*' failed for '<HOST>:.*' - No matching peer found
            NOTICE.* .*: Registration from '.*' failed for '<HOST>:.*' - Username/auth name mismatch
            NOTICE.* .*: Registration from '.*' failed for '<HOST>:.*' - Device does not match ACL
            NOTICE.* .*: Registration from '.*' failed for '<HOST>:.*' - Peer is not supposed to register
            NOTICE.* .*: Registration from '.*' failed for '<HOST>:.*' - ACL error (permit/deny)
            NOTICE.* .*: Registration from '.*' failed for '<HOST>:.*' - Device does not match ACL
            NOTICE.* .*: Registration from '\".*\".*' failed for '<HOST>:.*' - No matching peer found
            NOTICE.* .*: Registration from '\".*\".*' failed for '<HOST>:.*' - Wrong password
            NOTICE.* <HOST> failed to authenticate as '.*'$
            NOTICE.* .*: No registration for peer '.*' \(from <HOST>\)
            NOTICE.* .*: Host <HOST> failed MD5 authentication for '.*' (.*)
            NOTICE.* .*: Failed to authenticate user .*@<HOST>.*
            NOTICE.* .*: <HOST> failed to authenticate as '.*'
            NOTICE.* .*: <HOST> tried  to authenticate with nonexistent user '.*'
            VERBOSE.*SIP/<HOST>-.*Received incoming SIP connection from unknown peer
   
# Option:  ignoreregex
# Notes.:  regex to ignore. If this regex matches, the line is ignored.
# Values:  TEXT
#
ignoreregex =

add to  nano  /etc/asterisk/logger.conf
asterisk -x " core reload"
fail2ban2 => security,notice,warning,error

Verify  file exist
 ls /var/log/asterisk/fail2ban2
 systemctl restart fail2ban


 systemctl status fail2ban



iptables  -L -n
Chain f2b-SSH (1 references)
target     prot opt source               destination
REJECT     all  --  192.184.14.100       0.0.0.0/0            reject-with icmp-port-unreachable
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Chain f2b-recidive (1 references)
target     prot opt source               destination
REJECT     all  --  20.191.79.63         0.0.0.0/0            reject-with icmp-port-unreachable

jueves, 9 de septiembre de 2021

Re: Getting multiple inbound calls to an agent at a time

 

Re: Getting multiple inbound calls to an agent at a time

Postby mflorell » Thu Sep 09, 2021 4:18 pm

We have seen cases where there are duplicate entries in the vicidial_conferences database table, which can also cause this.

lunes, 6 de septiembre de 2021

WebRTC

 https://itgala.xyz/how-to-setup-webrtc-on-vicibox-and-enable-viciphone/

sábado, 4 de septiembre de 2021

Possible to disable AutoLogOut Timeclock

 

Re: Possible to disable AutoLogOut Timeclock

Postby mflorell » Fri Sep 03, 2021 7:39 pm

Timeclock End of Day exists so that no timeclock entry can be more than 24 hours. It does not affect agent logins or agents in the agent screen, it only affects the timeclock clock-ins.
mflorell
Site Admin
 
Posts: 17831
Joined: Wed Jun 07, 2006 3:45 pm
Location: Florida

lunes, 30 de agosto de 2021

your session has been paused

 Postby mflorell » Sat Mar 29, 2008 9:15 am

This feature is just an alert of an agent being paused by the system. Previously the agent wasn't notified at all. You need to figure out why the agent is being paused, usually it is caused by connectivity issues or an overloaded web server.

viernes, 20 de agosto de 2021

call transfer recording

 You can transfer a call through a different dial prefix that can start a recording using the agi-NVA_recording.agi script. https://github.com/inktel/Vicidial/blob/master/agi/agi-NVA_recording.agi


http://www.vicidial.org/VICIDIALforum/viewtopic.php?p=79426

jueves, 19 de agosto de 2021

Re: CUSTOMER NUMBER ON CALLER ID ON 3 WAY TRANSFER

 

Re: CUSTOMER NUMBER ON CALLER ID

Postby mflorell » Sat May 09, 2015 7:14 am

First, you have to have a carrier that will allow you to send any CID you want, then you use this campaign feature, set to CUSTOMER for your 3 way call to the 3rd party,

3-Way Call Outbound CallerID -This defines what is sent out as the outbound callerID number from 3-way calls placed by the agent, CAMPAIGN uses the custom campaign callerID, CUSTOMER uses the number of the customer that is active on the agents screen and AGENT_PHONE uses the callerID for the phone that the agent is logged into. AGENT_CHOOSE allows the agent to choose which callerID to use for 3-way calls from a list of choices. CUSTOM_CID will use the Custom CID that is defined in the security_phrase field of the list table for the lead.

lunes, 14 de junio de 2021

key report on survey campaing

Method 1

mysql  -e "select * from vicidial_list order by entry_date desc limit 100\G;" asterisk



-------------------------------------

Method 2

database name  asterisk

select asterisk;

MariaDB [asterisk]> select * from vicidial_list order by entry_date desc limit 10\G;

*************************** 1. row ***************************

                lead_id: 2874301

             entry_date: 2021-06-14 16:57:51

            modify_date: 2021-06-14 16:58:18

                 status: SVYHU

                   user: VDAD

       vendor_lead_code: 999999

              source_id: NULL

                list_id: 998

         gmt_offset_now: 0.00

called_since_last_reset: Y

             phone_code:

           phone_number: 393333635186

                  title: NULL

             first_name: Test

         middle_initial: NULL

              last_name: Call

               address1: Test Call

               address2: 2

               address3: 3

                   city: Springfield

                  state: IL

               province: NULL

            postal_code: NULL

           country_code: NULL

                 gender: U

          date_of_birth: NULL

              alt_phone: NULL

                  email: NULL

        security_phrase: 6

               comments: ROBOCALL test call placed 2021-06-14 16:57:51

           called_count: 1

   last_local_call_time: 2021-06-14 16:57:51

                   rank: 99

                  owner: Test Outbound Call

          entry_list_id: 0


 http://www.eflo.net/VICIDIALforum/viewtopic.php?f=2&t=38605

domingo, 24 de enero de 2021

change php time zone

edit the 

/etc/php7/apache2/php.ini


Add the New_York time zone


date.timezone = America/New_York


restart apache2

service apache2 restart

http://78.91.2.1/vicidial/admin.php?ADD=999999&stage=TIME




https://www.php.net/manual/en/timezones.php