Page 1 of 3
oxo system call duration problem with 2016
Posted: 02 Jan 2016 09:02
by ademok
Hello everybody ,
The duration of calls made by subscribers in 2016, more than 24 hours on it.
When the system date to 2015 does not a problem .
Does anyone have any idea about this problem?
ticketcollect file is attached.
Is there a reasonably likely to help me with this?
Re: oxo system call duration problem with 2016
Posted: 03 Jan 2016 15:26
by haje
Hello, i have the same problem on IP metering.
thaks for your idea...
Re: oxo system call duration problem with 2016
Posted: 04 Jan 2016 06:08
by Kis Gezu
Hi, it may also have the same problem of IP measurement.
Please help me
Re: oxo system call duration problem with 2016
Posted: 04 Jan 2016 12:56
by Maulwurf
same at my oxo R10.2.
Example: call duration 3 minutes.
Ticket Collector Call Duration is: 24:03
Re: oxo system call duration problem with 2016
Posted: 04 Jan 2016 13:00
by Andy Francis
Hi All,
Tri-Line have released a workaround to this issue for maintained customers using their TIM range of call logging/accounting products. Simply log in to their Gateway to get an update to the processing interface.
Best regards,
Andy
--
Tri-Line Technical Support Engineer
Re: oxo system call duration problem with 2016
Posted: 04 Jan 2016 15:17
by murraya
so many same issue...
Has any yet reported as bug to ALE?
Re: oxo system call duration problem with 2016
Posted: 05 Jan 2016 05:26
by Maulwurf
There is no available workaround solution for this fault.
The solution will be delivered in Official software releases that will be downloadable from our BP web site.
Tech Reference : crqms00187165/crqms00187048
Re: oxo system call duration problem with 2016
Posted: 05 Jan 2016 07:10
by AgustinRay
ALE has being reported some days ago, they are working on the issue. Its a world wide problem and as Maulwurf said, there is nothing you can do. Maybe set the year to 2015 and delete previous tickets, but this only generates inconsistency.
Its weird ALE hasn't post anything and their web page.
I just hope the do a fix for all the releases, since we have some old ones in old clients.
Re: oxo system call duration problem with 2016
Posted: 05 Jan 2016 07:16
by haje
My Idea is, that OHL Driver do this. Driver make 24h for all time. You can see thas seconds is corect.
Re: oxo system call duration problem with 2016
Posted: 05 Jan 2016 11:14
by giovanni.attolini
For OmniVista users, it's possible run a SQL script to correct records in database before to extract reports.
Code: Select all
update ticket t set t.Duration = (t.Duration - 806400)
where
t.Duration > 806400
and
t.InitialStartDateTime >= '2016-01-01 00:00:00'
Yes, 806400 is the duration in seconds that it have been added to the correct duration.