oxo system call duration problem with 2016

[rajansuruli15]

[/img]Hi,

I am also having the same issue. My pbx release is R710. Not only duration my date also showing weird. If i generate report for this month, it's showing for 14,15 and 16th days. But till now only 06th.
And the same duration issue with all calls, added 224hr added.

Any info will be helpful...

Thanks & Regards,
Rajan

[Kis Gezu]

Hello. The script OHLdriver does it work? The script for the processing program or create the .xml file before.

[vigzol]

I found it on the ALE business portal site:

OXO TECHNICAL ALERT - Metering ticket call duration fault

Since the date changed from 2015 to 2016 the OmniPCX Office has incurred a (CDR) metering ticket call duration fault. The consequence of this fault is that the OmniPCX Office metering ticket call duration now adds 24 hours to the real call duration.

Eg. if an outgoing call is 5 minutes duration then the resulting metering ticket is showing a call duration of 24:05:00.

All OmniPCX Office software are impacted by this fault.
ALE R&D has identified the fault and is currently producing new software versions to fix the issue.
The solution will be delivered in Official software releases that will be downloadable from our BP web site.

The Official OmniPCX Office software correction versions are as follows:

R920/078.001 and will be downloadable from the BP web site as of Friday 8th January 2016
R10.1/046.001 and will be downloadable from the BP web site as of Friday 8th January 2016
R10.2/031.001 and will be downloadable from the BP web site as of Friday 15th January 2016

A further update will be provided with details about our solution delivery for software releases prior to R920.

There is no available workaround solution for this fault.
ALE has allocated the maximum resources to provide a solution in the shortest possible time frame.

This Alert will be updated in the coming hours to provide you with further details about our solution delivery.

[rajansuruli15]

Hi vigzol,


Thanks for your post...

So all the old Release customers should upgraded their PBX to latest release. It's going to be problem for BP customers who don't have the SPS contract.


Regards,
Rajan K.S

[cavagnaro]

It says another update will be provided for older releases.

Enviado de meu C6603 usando Tapatalk

[vigzol]

This is an update 2 for technical ALERT OXO / all releases

Since the date changed from 2015 to 2016 the OmniPCX Office has incurred a (CDR) metering ticket call duration fault. The consequence of this fault is that the OmniPCX Office metering ticket call duration now adds 24 hours to the real call duration.

Eg. if an outgoing call is 5 minutes duration then the resulting metering ticket is showing a call duration of 24:05:00.

All OmniPCX Office software are impacted by this fault
ALE R&D has identified the fault and is currently producing new software versions to fix the issue.
The solution will be delivered in Official software releases that will be downloadable from our BP web site.

The Official OmniPCX Office software correction versions are as follows:

Software Releases currently in Software support phase

R920/078.001 already delivered and available for download from the BP web site
R10.1/046.001 already delivered and available for download from the BP web site
R10.2/031.001 will be downloadable from the BP web site as of Friday 15th January 2016

Software Releases out of Software support phase ( phased out )

R610/054.001 will be downloadable from the BP web site as of Friday 15th January 2016
R710/101.001 will be downloadable from the BP web site as of Friday 15th January 2016
R820/091.001 will be downloadable from the BP web site as of Friday 15th January 2016

We are currently making a feasibility study into the possibility of delivering the correction in phased out software release older than R610. This Alert will be updated again by the end of next week to provide you with more details about our solution delivery possibility for those software releases prior to R610.

There is no available workaround solution for this fault.
ALE has allocated the maximum resources to provide a solution in the shortest possible time frame.

[MakLampir]

I also have the same problem.
And I was grateful to find the answer here.
Thanks brother

[ademok]

This problem happens in all version (R2.1,R3.1..R10.2)

[ademok]

I solved the problem by applying the initial duration 8770

[ykruchko]

Hi.
Where I can download new firmware to fix that problam? And how I can check what version of firmware stay now ?