martes, 20 de noviembre de 2018

vicidial log tables

This document is meant for reference only, and it may not contain all log tables.


call_log - log of Asterisk inbound and outbound calls. Not necessarily accurate for call totals within VICIdial
callcard_log - Details involving the optional calling card module.
live_inbound_log - Logs of calls as they enter Call Menus.
park_log - Logs calls parked by agents.
recording_log - log for all recordings made within VICIdial or Asterisk.
user_call_log - manual dial calls placed in agent screen, includes 3way calls
vicidial_admin_log - Changes made through the admin interface.
vicidial_agent_log - Agent activity through the agent interface.
vicidial_agent_skip_log - Logs leads agent skipped in manual preview dial mode.
vicidial_ajax_log - Special debugging log for agent screen AJAX which must be enabled in System Settings.
vicidial_api_log - Log of all Agent and Non-Agent API calls to the system.
vicidial_carrier_log - Details about outbound calls, used in the carrier response log report.
vicidial_chat_log - Log of converstaions via optional chat module.
vicidial_closer_log - Contains logs for all ViciDial inbound calls that entered an In-Group(queue).
vicidial_cpd_log - Logs CPD responses if using Sangoma CPD(Lyra).
vicidial_dial_log - Logs outbound call information, similar to vicidial_log but contains more info for troubleshooting, including outgoing CID.
vicidial_did_agent_log - Only populated if "DID Agent Log" is enabled in system settings, will log the user that received a call from a DID
vicidial_did_log - Logs of all inbound calls as they came into the system
vicidial_dnc_log - Logs adding/deleting from the DNC lists.
vicidial_dnccom_filter_log - Log for the optional DNC.com integration.
vicidial_dtmf_log - Logs DTMF received within Asterisk.
vicidial_email_log - Log of inbound/reply emails.
vicidial_grab_call_log - Logs the agent grabs of calls waiting in queue
vicidial_lead_search_log - Logs of agent lead search events.
vicidial_list_update_log - Logs the optional list update process(which has to be manually set up on server)
vicidial_log - Contains logs for all ViciDial-initiated outbound calls, much more information than call_log, and more accurate.
vicidial_log_extended - Full caller_code and URL trigger information for inbound and outbound calls.
vicidial_log_noanswer - Only populated if "No-Answer Log" is enabled in system settings, will log no-answer calls
vicidial_manager_chat_log - Log of manager to agent chats.
vicidial_monitor_log - Will log agent monitoring sessions that use the monitoring AGI script
vicidial_nanpa_filter_log - Logs filtering processes of the optionaly NANPA cellphone filtering, if enabled on your system
vicidial_outbound_ivr_log - Will log call menu entries from outbound auto-dial survey calls
vicidial_process_trigger_log - There is a process triggering feature on the back end, this logs those actions
vicidial_qc_agent_log - Log for quality control module
vicidial_recording_access_log - Logs who accessed or attempted to access recordings, if that System Setting feature is enabled.
vicidial_remote_agent_log - logs calls taken by remote agents.
vicidial_report_log - Logs who ran a report, how long it took, etc.
vicidial_timeclock_audit_log - This is separate from the timeclock and logs all clock punches, is not altered if a manager alters a timeclock entry
vicidial_timeclock_log - Log for the timeclock, i.e. punching in/out.
vicidial_url_log - Used by the URL report, logs URL responses and other details from URL calls initiated by VICIdial (i.e. dispo call url)
vicidial_user_closer_log - logs the closer(in-group) selections by the agents in the agent screen.
vicidial_user_log - Logs agent screen login and logout activity.
vicidial_user_territory_log - Logs the Territory selections by the agents in the agent screen.
vicidial_xfer_log - logs of transfers of calls from ViciDial agents to other in-groups(queues)

http://www.vicidial.org/docs/LOG_TABLES.txt

lunes, 19 de noviembre de 2018

vicidial variables

Call URL features(start call url, dispo call url, etc...)

Details on the Call URL and webform-type fields and dynamic URL construction:

Web Form -  This is where you can set the custom web page that will be

opened when the user clicks on the WEB FORM button. To customize the

query string after the web form, simply begin the web form with VAR

and then the URL that you want to use, replacing the variables with

the variable names that you want to use --A--phone_number--B-- just

like in the SCRIPTS tab section.

Start Call URL -  This web URL address is not seen by the agent, but

it is called every time a call is sent to an agent if it is populated.

Uses the same variables as the web form fields and scripts. This URL

can NOT be a relative path. The Start URL does not work for Manual

dial calls. Default is blank.

Dispo Call URL - This web URL address is not seen by the agent, but it

is called every time a call is dispositioned by an agent if it is

populated. Uses the same variables as the web form fields and scripts.

dispo and talk_time are the variables you can use to retrieve the

agent-defined disposition for the call and the actual talk time in

seconds of the call. This URL can NOT be a relative path. Default is

blank.

Add Lead URL -  This web URL address is not seen by the agent, but it is called

every time a lead is added to the system through the inbound process. Default 

is blank. You must begin this URL with VAR if you want to use variables, and of

course --A-- and --B-- around the actual variable in the URL where you want to

use it. Here is the list of variables that are available for this function: 

lead_id, vendor_lead_code, list_id, phone_number, phone_code, did_id, 

did_extension, did_pattern, did_description, uniqueid, call_id. This feature is

only available for In-Groups.

No Agent Call URL - This is similar to Dispo Call URL, but it is for calls

that are not sent to agents such as DROPs, No Answers, Busys and timeouts. This 

option is available for Campaigns and In-Groups. This feature will only work for

auto-dial and inbound calls, not manual dial calls. For inbound calls, the 

specific in-group that a call was sent to needs to have the No Agent Call URL 

field filled in or this function will not run for that call.

CRM Popup Login - If set to Y, the CRM Popup Address is used to open a new 

window on agent login to this campaign. Default is N.

CRM Popup Address - The web address of a CRM login page, it can have variables 

populated just like the web form address, with the VAR in the front and using 

--A--user_custom_one--B-- to define variables. 

You can have lead information be auto-populated in the URL

options(webform, webform2, start_call_url, dispo_call_url, crm_popup_url) using

"--A--field--B--" where field is one of the following fieldnames:

(not all of these are available for all features)

vendor_lead_code, source_id, list_id, gmt_offset_now,

called_since_last_reset, phone_code, phone_number, title, first_name,

middle_initial, last_name, address1, address2, address3, city, state,

province, postal_code, country_code, gender, date_of_birth, alt_phone,

email, security_phrase, comments, lead_id, campaign, phone_login,

group, channel_group, SQLdate, epoch, uniqueid, customer_zap_channel,

server_ip, SIPexten, session_id, dialed_number, dialed_label, rank,

owner, camp_script, in_script, script_width, script_height,

recording_filename, recording_id, user_custom_one, user_custom_two,

user_custom_three, user_custom_four, user_custom_five,

preset_number_a, preset_number_b, preset_number_c, preset_number_d,

preset_number_e, preset_number_f, preset_dtmf_a, preset_dtmf_b,

did_id, did_extension, did_pattern, did_description, closecallid,

xfercallid, agent_log_id, entry_list_id, call_id.

For examples(and sample result URL):

VARhttps://astguiclient.sf.net/test_VICIDIAL_output.php?test=--A--vendor_lead_code--B--&appt_date=--A--appointment_date--B--&color=--A--favorite_color--B--&city=--A--nearest_city--B--&cities=--A--multi_city--B--&topics=--A--topics--B--

(https://astguiclient.sf.net/test_VICIDIAL_output.php?test=92837492837&appt_date=2010-10-31&color=green&city=ALBUQUERQUE&cities=CHICAGO,TAMPA&topics=price,quality)

VARhttp://192.168.192.3/agc/vdc_call_url_test.php?leadID=--A--lead_id--B--&listID=--A--entry_list_id--B--&dispo=--A--dispo--B--&talk_time=--A--talk_time--B--

(http://192.168.192.3/agc/vdc_call_url_test.php?leadID=321452&listID=101&dispo=NI&talk_time=214)

VARhttp://www.server.org/env.php?one=--A--user_custom_one--B--&two=--A--user_custom_two--B--

(http://www.server.org/env.php?one=asmith&two=hS87yt2)

https://github.com/inktel/Vicidial/blob/master/docs/CALL_URL_FEATURES.txt
http://vicidial.org/docs/CALL_URL_FEATURES.txt

lunes, 12 de noviembre de 2018

Hiding phone numbers on UI interface from agents

Postby mflorell » Fri Sep 23, 2011 6:32 am
This is already a feature, "Disable Alter Customer Phone" in campaigns can be set to HIDE and there is a User setting "Agent Alter Customer Phone" that can override this per-user.

List Mix


Postby mflorell » Thu May 27, 2010 4:32 pm
It's not experimental, it is just too much control for about 99.5% of ViciDial users out there. We have a couple clients using it and it works great if you keep very close tabs on your lists. What we see when clients usually call us with dialing problems that have List Mix enabled is that most of their lists need to be reset or they do not have the right statuses selected. 

An example: a client called up with problems. We looked at their settings and ran the hopper script and saw that with a hopper level of 100 they were only actually inserting 11 leads be run because most of their lists had no leads available to be dialed. List Mix only does exactly what you tell it to, nothing more, and that means you have to do most of the work setting the right ratios and statuses and resetting the lists.

sábado, 13 de octubre de 2018

Re: Call Note



Postby mflorell » Fri Sep 29, 2017 9:56 am
Campaign Detail -> Call Notes Per Call

Call Notes Per Call -Setting this option to ENABLED will allow agents to enter in notes for every call they handle in the agent interface. The notes entry field will appear below the Comments field in the agent interface. Also, if the Agent User Group is allowed to view Call Logs then the agent will be able to view past call notes for a lead at any time. Default is DISABLED.

Re: Add FPG number on agent screen



Postby mflorell » Sat Sep 22, 2018 4:26 pm
We added the dispo_add_FPG.php script for a client to do something similar. They had this trigger based on the Agent Selected Disposition of the call, so it was very easy on the agent side of things.


# dispo_add_FPG.php
#
# This script is designed to be used in the "Dispo URL" field of a campaign
# or in-group. It adds the phone_number of the call to a designated inbound 
# Filter Phone Group
#
# This script is part of the API group and any modifications of data are
# logged to the vicidial_api_log table.
#
# Example of what to put in the Dispo URL field:
VARhttp://192.168.1.1/agc/dispo_add_FPG ... _to_file=1

# 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
# - FPG_id - (999,etc...) the Filter Phone Group ID that you want the phone number to be inserted into
mflorell
Site Admin
 
Posts: 17032
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: vicidial_dmtf_log empty table



Postby muyousif » Sat Sep 15, 2018 1:05 pm
Ok I was able to solve this issue. Actually asterisk was not generating/passing dtmf events to listencron asterisk manager user. I had to add dtmf in asterisk manager file for cron and listencron users which solved the issue.

[cron]
secret = 1234
read = system,call,log,verbose,command,agent,user,originate,dtmf
write = system,call,log,verbose,command,agent,user,originate,dtmf

[listencron]
secret = 1234
read = system,call,log,verbose,command,agent,user,dtmf
;read = all
write = command
ViciBox v.6.0.3 | VERSION: