recording_log table no end_time

[jgaropel]

Hi,

We are currently upgrading to this version:


VERSION: 2.2.1-261 BUILD: 100625-1118

My problem is actually not a problem but I'm using this for internal data report... There's no end time in the recording_log table this I miss something or any settings in the admin page to do this?

[williamconley]

please post your original installation method with version and a link to the upgrade instructions you used/are using (or inform us of the instruction set in some other way?)

please also post an example of what you are saying along with the URL from where you acquired the sample (you can remove your ip/domain, we just need the rest of it to be sure we know the page/data in question)

are you saying that your recordings do not have an end time in your log file? or that there is no FIELD for an end time?

is there a start time and a call length?

[fporio]

Hi William,

i work with jgaropel.

It is fresh installed using ViciBox_Redux.x86_64-3.1.12.iso
Vicidial: VERSION: 2.2.1-237 BUILD: 100510-2015
Asterisk: 1.4.39.2-vici
Multi-Server: web,db,dialer,archive

I followed the instruction instructions from
ViciBox_Redux_v3-Install.pdf
and
ViciBox_Redux_v3-Cluster.pdf

Our problem is that the end_time, end_epoch,length_in_sec,length_in_min and vicidial_id is always NULL.

My guess is that php script that should be executed at the end of the crashes or doesn't get executed.

I hope you can help us out with this.

[mflorell]

I would suggest upgrading to the latest svn/trunk version, a lot of changes have been made since that version.

[fporio]

Ok. il try that out.

[fporio]

Hi,

I upgraded to:

VERSION: 2.4-344a
BUILD: 111024-1234

Now end_time, end_epoch, length_in_sec, length_in_min and vicidial_id has the values.

Although don't what's the use of the vicidial_id field.

Thanks.

Matt

[mflorell]

vicidial_id is either the uniqueid of the call or for inbound queue calls handled by an agent they can be the closecallid of the vicidial_closer_log record for that call.

[fporio]

I though it was just for the unique_id for the vicidial_log. Now i know.

Thanks a lot Matt;

[kelvin]

Hi mflorell:
I have the same problem as above, would you like to list what's changes since version 2.2.1 about this serious problem? Because we have several projects run in version 2.2.1 and we will take high risky if we upgrade all files and database to version 2.4. But I still want to resolve this problem ASAP.

[williamconley]

I'm not sure he'll be able to answer your question. the problem was solved by upgrading to a later version.

the changes between your version and the latest version are kinda "too many to list".

the present vicidial version is very stable, if that's what you are asking. all our clients are using the latest SVN trunk in 2.4 from the moment of their installation.

[kelvin]

Hi William:
Thanks your feedback. But I still want to know related files about above problem and I will find difference among these files between 2.2.1 and 2.4 by myself. We have modified lots of source code in 2.2.1 so that's why I can't upgrade to 2.4 right now.