Reference10:Release Notes Reporting
This roadmap describes the V10 (that is, Reference10:Concept_Reporting based) Reporting based on the linux application platform.
This article is generated automatically. Do not edit! Please see the disclaimer before using the information presented here!
V10 Service Release 1 (100062)
These are the fixes included in Reporting V10 service release 1. Definition
Logrotation didn't work due to updated logrotate package
| Status | Closed |
| Id | 103856 |
The updated packages required permission changes on and in some files.
V10 Service Release 2 (100067)
These are the fixes included in Reporting V10 service release 2. Definition
myPBX call list: Script error when retrieving history from reporting
| Status | Closed |
| Id | 104948 |
remote_ajax.htm, Line 77:
"Die fr diesen Vorgang erforderlichen Daten sind noch nicht verfgbar".
Cross-domain problem with Force-https on ILAP.
V10 Service Release 3 (100079)
These are the fixes included in Reporting V10 service release 3. Definition
Correctly check running processes in application installation files
| Status | Closed |
| Id | 106040 |
This check failed without correct system time (no NTP server).
Increased max length of report mails field
| Status | Closed |
| Id | 107134 |
From 60 to 1024 chars.
Correctly escape long name and pbx/system name
| Status | Closed |
| Id | 107723 |
Otherwise the report generation failed.
Reporting: Scheduled clean-up for old CDR data
| Status | Closed |
| Id | 104815 |
It can be configured now, after how many months CDRs are automatically deleted.
V10 Service Release 4 (100083)
These are the fixes included in Reporting V10 service release 4. Definition
Performance optimization of mypbx call list query
| Status | Closed |
| Id | 108259 |
Certain users with a non standard call behavior (e.g. 1 call/month) couldn't retrieve the mypbx call list within the mypbx timeout.
The query has been optimized and this optimization also positivly affects most other users.
LDAP: rebind needed to follow referrals
| Status | Closed |
| Id | 108647 |
If we try to follow the referrals we need to re-authenticate. If not done the LDAP library attempts with anonymous and the server responds with an error.
Correctly show connected number in report if no alert is present and setup is empty
| Status | Closed |
| Id | 108667 |
The connected number was shown as "N/A". Now the correct connected number is shown.
Report compatibility with IE 11
| Status | Closed |
| Id | 109496 |
Microsoft changed their navigator.appName to "Netscape" (obviously) so we needed another check to test for Internet Explorer...
V10 Service Release 5 (100086)
These are the fixes included in Reporting V10 service release 5. Definition
LDAP: search filter was not correct
| Status | Closed |
| Id | 110893 |
LDAP filter was not built correctly, add exact number dialed
LDAP: name resolution for an internal number in special case
| Status | Closed |
| Id | 111136 |
setup-from before an unconditional diversion contains no name information.
Support client timezone for call list in myPBX
| Status | Closed |
| Id | 110032 |
myPBX shows times in the client timezone now.
V10 Service Release 6 (100088)
These are the fixes included in Reporting V10 service release 6. Definition
Fixed wrong reporting data for certain call forwards
| Status | Closed |
| Id | 112365 |
Certain call forward scenarios produced wrong caller information reports.
Old CDRs will be still wrongly shown. Just new CDRs are fixed.
Increased number of relay cdr files from 6 to 10
| Status | Closed |
| Id | 112413 |
http://wiki.innovaphone.com/index.php?title=Reference10:Concept_Reporting#Relay_CDRs
V10 Service Release 7 (100097)
These are the fixes included in Reporting V10 service release 7. Definition
Reporting cleanup might have failed
| Status | Closed |
| Id | 113885 |
e.g. if the database connection broke down during cleanup, the database was in a bad state afterwards.
Increased maximum length of LDAP user name
| Status | Closed |
| Id | 114217 |
Increased maximum length to 128 characters.
V10 Service Release 8 (100105)
These are the fixes included in Reporting V10 service release 8. Definition
Reporting-LDAP: case insensitive comparison for name- and numberattributes
| Status | Closed |
| Id | 114996 |
Name attributes were not found.
Reporting-LDAP: search only for configured name- and number attributes
| Status | Closed |
| Id | 115349 |
Client was asking for all existing attributes. We save now some bandwidth.
Updated translations
| Status | Closed |
| Id | 115368 |
Updated translations of Linux and its applications.
V10 Service Release 10 (100114)
These are the fixes included in Reporting V10 service release 10. Definition
XML escape callback information in reports
| Status | Closed |
| Id | 118658 |
Otherwise the report can't be displayed.
Duplicate misleading entries in call list if a user has multiple endpoints registered
| Status | Closed |
| Id | 119192 |
If a user has multiple endpoints and one of these endpoints is not responding (e.g. a wireless endpoint out of range) a failed call was displayed even if the call was accepted by another endpoint in addition to the connected call.
Do not use HTML5 number type for dialing location input fields
| Status | Closed |
| Id | 121162 |
Now a configured '00' is shown, not '0' anymore.
Web reports support playback of recorded calls with the innovaphone Voice Player
| Status | Closed |
| Id | 118559 |
If calls have been recorded with the innovaphone Voice Recorder, they can be now played with the innovaphone Voice Player inside a report generated on the web UI of the Reporting.
V10 Service Release 11 (100118)
These are the fixes included in Reporting V10 service release 11. Definition
Added missing index for filters with group conditions
| Status | Closed |
| Id | 120417 |
Filters with group conditions are now faster as a missing index has been added.
Added another trace output for CDR retrieval if alarm sending fails
| Status | Closed |
| Id | 120491 |
The URL is now also printed.
CSV with separate columns time and date
| Status | Closed |
| Id | 120283 |
Two additional columns time and date added.
V10 Service Release 12 (100124)
These are the fixes included in Reporting V10 service release 12. Definition
Report mail attachment name with correct UTF-8 encoding
| Status | Closed |
| Id | 122460 |
The attachment name encoding wasn't correctly set for report mails.
Updated translations
| Status | Closed |
| Id | 122668 |
Updated translations.
V10 Service Release 13 (100127)
These are the fixes included in Reporting V10 service release 13. Definition
V10 Service Release 14 (100136)
These are the fixes included in Reporting V10 service release 14. Definition
V10 Service Release 15 (100147)
These are the fixes included in Reporting V10 service release 15. Definition
LDAP: no external line defined, direct dialing case.
| Status | Closed |
| Id | 127830 |
Reporting was not resolving names in this special situation where no Trunk Object was defined.
Log files didn't work after uninstall and reinstall of an application
| Status | Closed |
| Id | 128001 |
The application specific log files didn't work after uninstall and reinstall of the application.
Optimized sorting for CDRs with the same timestamps
| Status | Closed |
| Id | 128195 |
CDRs with the same timestamp are now additionally sorted by their database ID.
V10 Service Release 16 (100154)
These are the fixes included in Reporting V10 service release 16. Definition
Validation check for email adresses
| Status | Closed |
| Id | 129306 |
A new validation check also checked DNS records for the email domain which produced false results.
Fixed potential failure of reporting replication due to duplicated CDR guids
| Status | Closed |
| Id | 129490 |
If there have been duplicated CDR guids the replication might have failed.
This is fixed now.
Added Polish translation
| Status | Closed |
| Id | 130261 |
We added the Polish translation.
Mainly innovaphone Reporting has been translated, but innovaphone Faxserver and innovaphone Exchange Calendar Connector are also mostly translated.
The innovaphone application platform itself still remains untranslated for Polish.
V10 Service Release 17 (100157)
These are the fixes included in Reporting V10 service release 17. Definition
Do not return a server error 500 on CDR XML parse errors
| Status | Closed |
| Id | 132424 |
Otherwise the PBX always tries to send the same CDR again.
Instead ignore this CDR and set up an event on the PBX with the failed XML.
V10 Service Release 18 (100160)
These are the fixes included in Reporting V10 service release 18. Definition
Destroy session data for php scripts which are not used within web UI
| Status | Closed |
| Id | 133075 |
This reduces the amount of session files and speeds up the session cleanup script.
V10 Service Release 19 (100163)
These are the fixes included in Reporting V10 service release 19. Definition
LDAP: no name resolution if external line prefix was longer than one digit
| Status | Closed |
| Id | 138518 |
external line can be longer.
V10 Service Release 20 (100168)
These are the fixes included in Reporting V10 service release 20. Definition
V10 Service Release 21 (100173)
These are the fixes included in Reporting V10 service release 21. Definition
Correct handling of missing msg/time attribute in CDR xml
| Status | Closed |
| Id | 141662 |
A missing msg attribute could have caused a trap of an application on the Linux AP.
Optimized query for missed calls in myPBX with Reporting
| Status | Closed |
| Id | 142479 |
The query for missed calls might have taken quite long, so that other call list request got stuck and caused "Call list not available" errors in myPBX.
V10 Service Release 22 (100174)
These are the fixes included in Reporting V10 service release 22. Definition
V10 Service Release 23 (100176)
These are the fixes included in Reporting V10 service release 23. Definition
V10 Service Release 24 (100178)
These are the fixes included in Reporting V10 service release 24. Definition
Reporting/myPBX: handling of calls to unregistered users
| Status | Closed |
| Id | 148399 |
These calls were shown as missed calls although they just contained setup und release events without an alert event.
Now these calls are not shown as missed call in myPBX anymore although the call itself will be still shown in the call list.
In the call details, the call will be shown with an error symbol.
Cause Codes:
18 == No User Responding
19 == No Response from User
Call-Lists: Calls to users with multiple registrations, which were forwarded, were shown multiple times
| Status | Closed |
| Id | 148583 |
Indicate in CDRs that there are more CDRs for the same call
V10 Service Release 25 (100181)
These are the fixes included in Reporting V10 service release 25. Definition
Added possibility to configure also weeks for CDR cleanup
| Status | Closed |
| Id | 151698 |
Weeks can be also configured now, in addition to months.
Added French, Russian and Czech translations to Linux and its applications
| Status | Closed |
| Id | 151956 |
French, Russian and Czech translations are now integrated.
V10 Service Release 26 (100183)
These are the fixes included in Reporting V10 service release 26. Definition
Show calls with CFNR to another user as missed call in the myPBX call list
| Status | Closed |
| Id | 154442 |
These CFNR calls are now shown as missed call in the myPBX call list.
The myPBX and phone call list now behaves the same.
Such calls are also missed if the user, to which the CFNR pointed, connects the call.
Fixed negative call durations in reports
| Status | Closed |
| Id | 154447 |
A certain waiting queue call could have caused negative call durations within the reporting database.
V10 Service Release 27 (100090)
These are the fixes included in Reporting V10 service release 27. Definition
Fixed filters with multiple same report times for different days
| Status | Closed |
| Id | 155942 |
A false primary key definition prevented such configurations.
Do not show connected calls from WQs as missed call in myPBX
| Status | Closed |
| Id | 158104 |
This was caused by a previous hotfix.
V10 Service Release 28 (100193)
These are the fixes included in Reporting V10 service release 28. Definition
Possible deadlock with CDRs and database reindex
| Status | Closed |
| Id | 157441 |
The deadlock itself can't be avoided, but the database connection itself went bad.
Now, the database connection is restarted in such a situation.
Renamed filter property "Call duration" to "Call duration (User)"
| Status | Closed |
| Id | 158305 |
It now matches the name of the call duration which can be selected on the report page.
The filter currently doesn't allow to filter for "Call duration (Total)".
V10 Service Release 29 (100194)
These are the fixes included in Reporting V10 service release 29. Definition
Speedup CDR deletion and database cleanup afterwards
| Status | Closed |
| Id | 163231 |
A separate REINDEX of the database is not neccessary anymore since PostgreSQL 9.0.
Additionally more RAM is now assigned to the process which cleans the database.
RAM is calculated based on free RAM with a minimum value of 32MB.
The general setting of maintenance_work_mem has been changed according to the total system RAM (5%).
A warning is now shown that CDR deletion might prevent CDRs from being written to the database.
V10 Service Release 30 (100195)
These are the fixes included in Reporting V10 service release 30. Definition
V10 Service Release 31 (100199)
These are the fixes included in Reporting V10 service release 31. Definition
V10 Service Release 32 (100210)
These are the fixes included in Reporting V10 service release 32. Definition
Do not perform vacuum full after CDR cleanup
| Status | Closed |
| Id | 169045 |
VACUUM FULL requires too much additional disk space.
Without the FULL option, freed disk space cannot be reclaimed by the OS, but PostgreSQL will still reuse it for further CDRs.
V10 Service Release 33 (100215)
These are the fixes included in Reporting V10 service release 33. Definition
Reporting: accept fcgi requests even if no threads are available
| Status | Closed |
| Id | 169428 |
we were waiting for a thread to become available before accepting new fcgi requests. Now we will accept requests and respond with 500 if no thread is available. This request should come again later.
Fixed possible NULL pointer trap in CDR/myPBX calllist application
| Status | Closed |
| Id | 169695 |
In case a user didn't exist, the application could have trapped.
Increased name/number attribute field length of LDAP servers
| Status | Closed |
| Id | 171666 |
To 1024 chars.
V10 Service Release 34
These are the fixes included in Reporting V10 service release 34. Definition