[asterisk-bugs] [JIRA] Commented: (ASTERISK-20504) Asterisk 1.8 should use [compat] section in asterisk.conf and behave acconding to the flag pbx_realtime=1.6

[Tiago Geada (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197906#comment-197906 ] 

Tiago Geada commented on ASTERISK-20504:
----------------------------------------

Well...

We are a call center that started small and grown wide in a short time window. We use queue_log to read stuff about calls. For instance our 'panel board' in java reads AMI events, but has a few stats readings from queue_log such as count ABANDON, ENTERQUEUE events do show some numbers.

Our call reports, are also read from queue_log, to know number of calls lost before wating 15 seconds, or after or whatever. These reports are pretty big and its a module per partner...

Even asterisk AEL's do write custom stuff (such as 'INCOMING', 'OUTGOING' 'HUNGUP') using internal variable ${EPOCH}
Even recorded calls path is written in queue_log ... All about our PBX comes from (and goes into) queue_log table.

Today we also use CDR, however, only new apps/scripts read from there, and everything else we heavily relly on, is using queue_log.


Some aplications do get deprecated, and replacements are using CDR, but we simply can not change all of it. We are always too busy with whatever else comes along.

As for me, I would like to upgrade asterisk, but it is not essential. If there is no backwards compatibility we will not upgrade, unless it becomes really necessary for some reason...

Also, issue 17036 seems to be affecting only text file.

I must state, in the past we used to change sourcecode ( there was a }else{ to chose between RT queue_log or file quele_log) to keep both text file and mysql queue_log. Today however we no longer need the text file.

> Asterisk 1.8 should use [compat] section in asterisk.conf and behave acconding to the flag pbx_realtime=1.6
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20504
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20504
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/res_config_mysql, Applications/app_queue
>    Affects Versions: 1.8.16.0
>         Environment: Debian wheezy, mysql (using addon res_config_mysql)
>            Reporter: Tiago Geada
>
> in 1.6 queue_log was being populated with the column 'time' formated as UNIX TIME STAMP, while in 1.8, res_config starts by complaining about column time being varchar(11) while it should be char(26) and every queue event is registered with datetime format (as in '2012-10-02 00:01:04') instead of '1349132464'
> I thought in asterisk.conf [compat] section having "pbx_realtime=1.6" would take care of this, but it does not.
> Shouldn't date be inserted as unixtimestamp, if this compat flag is set to 1.6 ??
> Also, maintaining this compatibility, queue_log should still need only one 'data' column, instead of 'data1','data2','data3','data4' and 'data5'

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira