[SOLVED] Tying recording_log table to others

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

[SOLVED] Tying recording_log table to others

Postby AlSam » Tue Oct 28, 2014 11:42 am

I am trying to figure out where the data in the vicidial_id field in the recording_log table comes from. In most cases, it is obvious. The value comes from the uniqueid field in the vicidial_log table. In other cases, I cannot figure out where it came from. Here is a small excerpt from the recording_log table. I removed a few fields because the output took up a lot of space from left to right. Notice the second record's value in the vicidial_id field is 1414178762.4965 which is the typical pattern of the uniqueid field in the vicidial_log table but the first record's value I can't find in any other table. I would appreciate help in finding this out. Thanks in advance for any and all help.

P.S. The reason for all this is that I need to be able to determine whether the recording is related to a manual call, automated outbound call or inbound and which ingroup it belongs to.

ViciBox Redux v.3.1.10 | VERSION: 2.4-334a BUILD: 110831-2038 | Asterisk 1.4.38-vici | 1 Web 1 DB 5 Asterisk | Amfeltec PCIe timer | No additional software

Code: Select all
mysql> SELECT recording_id, extension, length_in_sec, location, lead_id, `user`, vicidial_id FROM recording_log where recording_id in (4555179,4555180);
+--------------+-----------+---------------+--------------------------------------------------------------------------------------+----------+--------+-----------------+
| recording_id | extension | length_in_sec | location                                                                             | lead_id  | user   | vicidial_id     |
+--------------+-----------+---------------+--------------------------------------------------------------------------------------+----------+--------+-----------------+
|      4555179 | 8309      |           120 | http://172.26.5.166/RECORDINGS/MP3/20141024-152556_7875158129-all.mp3                | 13564434 | 105238 | 1793725         |
|      4555180 | 8309      |           302 | http://172.26.5.164/RECORDINGS/MP3/20141024-152602_PYMENEW_7877259455_103068-all.mp3 | 13509695 | 103068 | 1414178762.4965 |
+--------------+-----------+---------------+--------------------------------------------------------------------------------------+----------+--------+-----------------+
2 rows in set (0.00 sec)
Last edited by AlSam on Wed Oct 29, 2014 11:52 am, edited 1 time in total.
ViciBox v.7.0.4-170113 | VERSION: 2.14-697a BUILD: 190121-2019 | Asterisk 11.25.1-vici | All-In-One | No additional software
AlSam
 
Posts: 125
Joined: Thu Sep 02, 2010 1:17 pm

Re: Tying recording_log table to others

Postby geoff3dmg » Wed Oct 29, 2014 7:50 am

Are they inbound/closer calls? As they will be in vicidial_closer_log instead.
Vicibox 5.03 from .iso | VERSION: 2.10-451a BUILD: 140902-0816 | Asterisk 1.8.28.2-vici | Multi-Server | Amfeltec H/W Timing Cards | No Extra Software After Installation | Dell PowerEdge 1850 | Pentium 4 'Prescott' Xenon Quad @ 3.40GHz
geoff3dmg
 
Posts: 403
Joined: Tue Jan 29, 2013 4:35 am
Location: Lancashire, UK

Re: Tying recording_log table to others

Postby AlSam » Wed Oct 29, 2014 11:51 am

I was able to match the first call to the vicidial_closer_log table. Thanks for the quick response.
ViciBox v.7.0.4-170113 | VERSION: 2.14-697a BUILD: 190121-2019 | Asterisk 11.25.1-vici | All-In-One | No additional software
AlSam
 
Posts: 125
Joined: Thu Sep 02, 2010 1:17 pm


Return to Support

Who is online

Users browsing this forum: Google [Bot] and 126 guests