Reference9:Release Notes Linux Reporting
This roadmap describes the V1 (that is, Reference9: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!
V1 Hotfix 1 (10181)
These are the fixes included in Reporting V1 hotfix 1. Definition
reporting callback request from mypbx may crash with uninitialized reporting config
Status | Closed |
Id | 63709 |
If one has never configured replication or ldap for Reporting, a reporting callback request from mypbx won't work (the process crashes).
This is fixed now by checking a config parameter.
reporting: wrong remote party in some transfer and forward events
Status | Closed |
Id | 63819 |
We assumed that the remote party does not change after transfer/forward event and that the next event after those contains more information over the remote party but this is wrong since the remote party may change.
reporting: process.fcgi crashes with filters containing a remote number condition
Status | Closed |
Id | 63878 |
forgot to open parenthesis
conn_length was also forgotten to change to conn_duration
Reporting: better visibility of replication status
Status | Closed |
Id | 63920 |
The connection status to the configured replication server is now shown.
The last run is now also shown, even if there was no successful database connection.
reporting: if conn to/from event present, conn-duration must be at least one
Status | Closed |
Id | 64267 |
Sometimes conn event and disc/rel event present the same time. Maybe, this should be changed in PBX but we check it anyway.
Connected time must be at least 1. This is also applicable for billing.
reporting: mypbx missed calls wrong for multiple registrations
Status | Closed |
Id | 65103 |
If one user has multiple registrations, missed calls were recognized, although the calls has been answered.
Calls from other registrations are disregarded now.
reporting: show call duration time instead of conn duration time in report
Status | Closed |
Id | 65132 |
As the whole call flow is shown in the report, showing the call duration makes more sense.
reporting: conn, call and billing time calculation
Status | Closed |
Id | 65146 |
billing calls are those having "from", "ct" or "cf" as dir attribute in cdrs. So far we have only considered calls with a setup-from as first event but "ct" and "cf" calls can present a setup-to event and they must be charged too.
all times must be ended with the first disc event.
conn time must not be counted after a transfer-from or cf-from event.
reporting: allow two or more LDAP configurations to have same PBX name
Status | Closed |
Id | 65253 |
it is needed if you have more than one trunk.
Linux: LDAP query if no name available in CDR
Status | Closed |
Id | 63134 |
If the CDR contains no name on it, make a LDAP query to the PBX before writing the CDR into the database.
Try with OPENLDAP library.
reporting: replication not running ssl
Status | Closed |
Id | 63933 |
configure postgresql to run ssl during replication. We will use the web server certificate.
reporting: added delete tag in application xml file
Status | Closed |
Id | 63936 |
delete tag defines which files/directories must be deleted during uninstall
Reporting: separate authentication for reporting web access
Status | Closed |
Id | 64875 |
It is now possible to configure a separate authentication to the innovaphone reporting web site.
reporting: download xml report if it has an invalid format
Status | Closed |
Id | 64882 |
we offer now a link to download the xml report if it has an invalid format and therefore cannot be displayed by the browser.
reporting: LDAP: add Name and Number attributes
Status | Closed |
Id | 64919 |
we have added two new fields for Name and Number Attributes in the LDAP configuration.
So far we had just used "displayName" as Name attribute and "mobile,telephoneNumber and HomePhone" as Number attributes.
reporting: improvements on xml/pdf representation
Status | Closed |
Id | 65151 |
we usually use information on the alarm event but conn event normally contains more data. Check which one is better.
pdf looks strange if LDAP returns large strings
reporting: suppress last digits of called/calling party for external calls
Status | Closed |
Id | 65259 |
allow to suppress last digits of called/calling party for external calls. It can be configured how many digits must be replaced with a '*'.
reporting: diagnostics page available with logs/rpcap
Status | Closed |
Id | 65365 |
The diagnostics page with reporting related log files and rpcap functionality is now also available on the reporting web site.
Reporting: transfers on a slave PBX will now generate a new event: transfer-remote
Status | Closed |
Id | 65475 |
when a transfer event happens on a slave PBX, it cannot be known the status of the call afterwards. This new event indicates this situation and a connected status will be shown in the report.
reporting: show only one CDR for transfer/forward calls per user
Status | Closed |
Id | 65820 |
Currently both generated CDRs for a user of a transfer or forward call are shown. Diversions are now divided in two CDRs, one showing the whole call flow and another containing billing information, which will not be shown in call lists.
V1 Hotfix 2 (10197)
These are the fixes included in Reporting V1 hotfix 2. Definition
Reporting: check if database is being restored before writing a CDR
Status | Closed |
Id | 66757 |
avoid writing a CDR to the DB if it is being restored since this could corrupt the DB.
This CDR will be sent by the PBX again since Linux is responding with 500 HTTP Error Code.
Cumulative hotfix installation script didn't apply second hotfix
Status | Closed |
Id | 66917 |
As the version of the previously installed hotfix hasn't been set properly.
Reporting: current password was not checked before setting a new password
Status | Closed |
Id | 67386 |
we used localhost and given password to make a connection to the db but localhost needs no password.
reporting: postgresql-8.4 debian package update
Status | Closed |
Id | 66271 |
debian update for postgresql 8.4.
V1 Hotfix 3 (10201)
These are the fixes included in Reporting V1 hotfix 3. Definition
Duplicated report lines on certain filter options
Status | Closed |
Id | 68123 |
Certain filter options caused duplicated lines in a report.
This has been fixed by changing the query.
Reporting: ldap results were not escaped
Status | Closed |
Id | 68654 |
any string must be 'postgresql' escaped before inserting it into the DB.
V1 Hotfix 4 (10237)
These are the fixes included in Reporting V1 hotfix 4. Definition
invalid log file entries for mypbx requests if reporting database is not running
Status | Closed |
Id | 71277 |
Invalid log file entries have been written for mypbx requests, if the reporting database was down.
Call list sorting by call duration now numerical, not alphanumerical
Status | Closed |
Id | 71450 |
The call list sorting by call duration was alphanumerical, not numerical.
This has been fixed.
Viewing log files with invalid chars now possible
Status | Closed |
Id | 71716 |
Viewing log files with invalid chars is now possible over the diagnostics page.
linux: added non-blocking option on flock() call for log files
Status | Closed |
Id | 71838 |
The flock() call was eventually blocking if the lock could not be acquired. If we do not get the lock after ten attempts, the log trace will be lost.
dynamic list row add/remove doesn't trigger page to top any more
Status | Closed |
Id | 71957 |
Adding or removing a line of a dynamic list doesn't trigger the jump to the page top any more.
Possibility to clear the call list in mypbx
Status | Closed |
Id | 71202 |
A new button is now available in mypbx to clear the call list.
possibility to clear log files
Status | Closed |
Id | 71714 |
Log files can be cleared now.
Just system specific log files can't be cleared.
added trace level option
Status | Closed |
Id | 71857 |
There is now the possibility to enable further tracing levels.
Increased maximum height of filter list
Status | Closed |
Id | 71865 |
Currently only four filter options can be viewed at a time.
With the fix, the lists height increases from 2 until 16 items until the scrollbar of the list is enabled.
V1 Hotfix 5 (10276)
These are the fixes included in Reporting V1 hotfix 5. Definition
LDAP filters are now stored in the DB instead of XML
Status | Closed |
Id | 73439 |
LDAP filters have been moved to the DB.
This makes it easier to replicate them to a standby installation.
reporting: send reports per email
Status | Closed |
Id | 72391 |
Reports can be now sent per email.
filter option for report times
Status | Closed |
Id | 73006 |
A filter can now define report times, e.g. all records between 08:00 and 16:00.
Status | Closed |
Id | 73542 |
It is now possible to add a logo and footer in pdf reports
exclude outgoing calls without number/h323 from mypbx call list
Status | Closed |
Id | 73561 |
Calls are not shown anymore, if someone just offhooks and onhooks without dialing.
V1 Hotfix 6 (10282)
These are the fixes included in Reporting V1 hotfix 6. Definition
reporting: mails were not sent in vm installations
Status | Closed |
Id | 75359 |
The vm installation was creating a local-host-names file with wrong data and this was making DNS problems.
reporting: possible buffer overrun reading system processes
Status | Closed |
Id | 75645 |
when restoring db from a backup, we do not accept cdrs. We look the running processes searching from "db-restore" in files whose size is null. I allocated a 1024 bytes thinking that was enough, apparently not.
mypbx call list query optimized for speed
Status | Closed |
Id | 75646 |
The query execution lasted quite long, if a user had cleared the call list and less than 20 calls in this list.
reporting: summary of pdf reports was not displayed correctly
Status | Closed |
Id | 75655 |
The summary was not always displayed correctly
report mails with non latin1 chars in mail name
Status | Closed |
Id | 75667 |
The mail name has to be correctly encoded to be correctly parsed by cron.
LDAP servers now support object filters
Status | Closed |
Id | 75697 |
This is needed, if an innovaphone PBX is used as phone book.
check if reporting application already exists on reporting application install
Status | Closed |
Id | 75828 |
This check hasn't been done yet and caused application issues, if someone installs an already existing reporting application again.
Reporting: pdf reports showing connected duration instead of call duration
Status | Closed |
Id | 76303 |
both times are normally equal, that's why we did not see the bug.
possible trap after failed DB insert of a CDR
Status | Closed |
Id | 76625 |
A possible trap after a failed DB insert of a CDR has been fixed.
prevent failing CDR insert with replication
Status | Closed |
Id | 76633 |
A missing LOCK statement could have caused a failed CDR insert in replication scenarios.
Possiblity to delete CDRs from database since time X and/or pbx object Y
Status | Closed |
Id | 73944 |
You can now define a time period and/or a pbx object for which CDRs are deleted in the database.
reporting: test email functionality
Status | Closed |
Id | 75760 |
under diagnostics kann man ein email senden. So berprft man ob emails verschickt werden.
reporting: call duration and alert duration in filter settings
Status | Closed |
Id | 75764 |
How long a call was connected or how long a "not connected" call was ringing.
reporting: send mails via external server (smtp relay)
Status | Closed |
Id | 75903 |
it is now possible to configure the mail client on Linux to send mails via Exchange.
V1 Hotfix 7 (10285)
These are the fixes included in Reporting V1 hotfix 7. Definition
check for postgresql installation before editing postgresql conf file
Status | Closed |
Id | 77334 |
only remove certain lines from default pg_hba.conf file if postgresql hasn't been installed yet.
myPBX: Clearing call list does not work in IE8
Status | Closed |
Id | 77915 |
IE8 caches the HTTP requests to reporting. Therefore after clearing the call list the old (uncleared) callist is displayed again.
An expires header is now sent within the response.
Reporting: Localised date and time format in myPBX call list
Status | Closed |
Id | 76779 |
Call list shall contain localised date and time. Also today's and yesterday's date should be replaced by words.
reporting: make LDAP queries for Trunk Line Objects
Status | Closed |
Id | 76906 |
we now see in reports in the "Left" column "external number Amt" for the Amt object but this external number may appear in LDAP. If this number is found in LDAP, we replace previous value with the LDAP result.
Status | Closed |
Id | 77381 |
Some shared code has been moved for future innovaphone applications for the linux application platform.
V1 Hotfix 8 (10288)
These are the fixes included in Reporting V1 hotfix 8. Definition
some preperations for web interface translations
Status | Closed |
Id | 78428 |
Changed some small things for future web interface translations.
filter call direction options transfer/call forward did not work
Status | Closed |
Id | 78618 |
Both options did not work and have been fixed.
Show pickup party after transfer/cf/alert in call report
Status | Closed |
Id | 79495 |
Currently the connect information is wrong for calls which have been pickuped.
Now, a new line will be shown for the pickup party.
option to show filter info in xml/pdf for call report not only in an email report
Status | Closed |
Id | 78762 |
Currently only the PDF of an email report contains the filter information.
Now, also the xml can contain it and manual reports can also contain the information now.
Parse language code from mypbx
Status | Closed |
Id | 78879 |
For localization of the call list.
V1 Hotfix 9 (10294)
These are the fixes included in Reporting V1 hotfix 9. Definition
Reporting: Mails not sent due to special characters
Status | Closed |
Id | 80459 |
wrong handling of special characters.
Enter key submits filter changes now
Status | Closed |
Id | 80763 |
The enter key now submits filter changes when used in a filter editing field.
Reporting: avoid empty page at end of PDF reports
Status | Closed |
Id | 80787 |
sometimes an empty page appeared at the end of pdf reports.
V1 Hotfix 10 (10303)
These are the fixes included in Reporting V1 hotfix 10. Definition
Enter key submits mail changes now
Status | Closed |
Id | 81184 |
Instead of canceling changes.
do not send an alarm for deadlocks on CDR insert
Status | Closed |
Id | 83267 |
as this CDR insert will be retried afterwards again.
multi-client capability for reporting
Status | Closed |
Id | 82835 |
It is now possible to configure different user logins. The admin can assign so called base filters to these users and the users can just use the assigned base filters to create reports or report mails.
They can also create own filters based on one of the assigned base filters.
German translation for the web interface and reports
Status | Closed |
Id | 83047 |
Added the german translation.
V1 Hotfix 11 (10317)
These are the fixes included in Reporting V1 hotfix 11. Definition
Localise time of callbacks in reports and mypbx calllist
Status | Closed |
Id | 84256 |
The callback time was language independet and now it is localised in the report xml, which is used for reports and the mypbx calllist.
PDF report creation didn't work with group by and sort by options
Status | Closed |
Id | 84346 |
e.g. in Report Mails, but also from web ui.
Suggest possible PBX object names on creation of a report
Status | Closed |
Id | 83834 |
On entering a PBX object (long name) to create a report for this object, possible values are now selectable from a displayed list.
To keep the response time low, only values from CDRs of the last week are shown.
retry sending of Report Mail on failure and write error to log file
Status | Closed |
Id | 84591 |
The sending of a report mail is now retried two times, if the sending fails and the error is written to the innovaphone-reporting log file, if the last try also fails.
Language for Report Mail configurable
Status | Closed |
Id | 84692 |
The language for a report mail is now configurable.
Alarms are now cleared if condition is cleared
Status | Closed |
Id | 85085 |
Alarms of the Linux Application Platform or by applications like Reporting are now cleared, if the alarm condition doesn't exist anymore.
V1 Hotfix 12 (10323)
These are the fixes included in Reporting V1 hotfix 12. Definition
Remove duplicate connected CFNR calls from report
Status | Closed |
Id | 85476 |
Users with multiple registrations had multiple calls in their report, if the call had a CFNR and was connected afterwards.
Sent mail reports are not stored in sent file anymore
Status | Closed |
Id | 85485 |
Sent mail reports had been stored in a file. This isn't done anymore now.
Occasional corrupt report attachments
Status | Closed |
Id | 85556 |
Sometimes sent report archives were corrupt, because the sending mail program didn't recognize the mime type of the file and changed the binary file before sending it.
This is fixed now.
Don't treat CFU calls with connect as "No response" calls
Status | Closed |
Id | 85863 |
With a filter with the "No response" check, forwarded calls with a connect after the forward shouldn't be shown.
Enable PosgreSQL Autovauum feature correctly
Status | Closed |
Id | 86504 |
There was a configuration option missing for this feature to work properly.
Restrict myPBX call list to calls of the last month
Status | Closed |
Id | 86573 |
This prevents high response times if a user does not have 20 calls in the last month.
Do not uninstall already installed packages after failed hotfix installation
Status | Closed |
Id | 86597 |
Due to a bug, already installed packages have been uninstalled after a failed hotfix installation.
Column with "Alerting time" for reports
Status | Closed |
Id | 85478 |
Show the alerting time as column in report.
Option to compress/not compress the report in a report mail
Status | Closed |
Id | 85580 |
Added the possibility to define whether a report in a mail will be compressed or not.
Reporting: reports in CSV format
Status | Closed |
Id | 85823 |
Reports in CSV format without call history Status:
Summary for each group in a grouped report
Status | Closed |
Id | 85972 |
Each group gets now a new summary line after the last record of the group, which contains the following information:
Number of incoming calls
Number of outgoing calls
Total connected duration
Total alert duration
V1 Hotfix 13 (10329)
These are the fixes included in Reporting V1 hotfix 13. Definition
Alert/conn duration filter didn't always work
Status | Closed |
Id | 86970 |
The filter settings for alert and conn duration didn't work under certain other filter options.
CSV export didn't work with certain group by and sort by settings
Status | Closed |
Id | 87492 |
If group by was set to date and sort by to any value, the CSV export failed.
Report on the web didn't show correct group summary if sorted differently
Status | Closed |
Id | 87532 |
A grouped report didn't correctly show the group summary, if one of the sort columns has been used.
Reporting: Remote Party Information is empty
Status | Closed |
Id | 87742 |
Calls having only Setup and Rel events contain the information of the remote party inside the release event. (we were using setup) Status:
LDAP server configuration now requires LDAP port and suggests default 389
Status | Closed |
Id | 87983 |
The LDAP port is now required and the default port 389 is suggested.
Check of running processes didn't work sometimes
Status | Closed |
Id | 88553 |
Due to the output width of the ps command.
Possibility to configure displayed duration in report
Status | Closed |
Id | 85768 |
You have now the possibility to select the displayed duration:
Call Duration (Total)
Call Duration (User)
Billing Duration
Optimized myPBX call list query
Status | Closed |
Id | 86824 |
The query has been optimized for a faster response time.
Reporting: LDAP Einrichtung mit Wildcard fr PBX Name
Status | Closed |
Id | 88129 |
Jetzt wird '%' als Wildcard akzeptiert. Status:
Check of running db restore/backup etc. available for other applications now
Status | Closed |
Id | 88339 |
The check of a running db restore/backup etc. is now available for other applications.
This offers the possibility to prevent database access during certain operations.
Anonymize internal names/numbers in a report
Status | Closed |
Id | 88425 |
New option added to anonymize internal names/numbers.
V1 Hotfix 14 (10336)
These are the fixes included in Reporting V1 hotfix 14. Definition
Avoid using exec and system in PHP
Status | Closed |
Id | 89234 |
these functions are consuming very much time. We will now implement locks through files and PHP will only call file_exist function.
These change will also be applied to cdr.c
Anonym flag now available as base filter option
Status | Closed |
Id | 88907 |
If this flag is set, all reports created with this base filter will be anonym.
Show summarized alert duration in summary
Status | Closed |
Id | 89033 |
The alert duration of incoming/outgoing calls is now shown in the summary.
Some optimizations for a better web ui performance
Status | Closed |
Id | 89238 |
Added some session vars to avoid running slow code multiple times.
Background processes run with a lower priority now.
V1 Hotfix 15 (10353)
These are the fixes included in Reporting V1 hotfix 15. Definition
Internal database connection was slow due to SSL mode
Status | Closed |
Id | 90519 |
The connection string was slightly wrong, so SSL mode wasn't disabled as intended.
Therefor the connection was slower than expected.
Reporting: optimization of the CDR receiving process
Status | Closed |
Id | 90894 |
postgresql takes too long to open a connection to the db. Now we have an opened DB connection and we queue the incoming CDRs.
LDAP: use next configured server if the actual one returns no name or error.
Status | Closed |
Id | 91228 |
if actual LDAP server does not return a name maybe another configured server does. Therefore test all configured LDAP servers.
Right now we only use the first valid one.
Stop database if application is uninstalled
Status | Closed |
Id | 91293 |
The database is now stopped, if it gets uninstalled on an application uninstall.
Otherwise it doesn't start again on the correct port after a new install...
LDAP: National/Trunk prefix may not exist
Status | Closed |
Id | 91798 |
Some countries like Norway or Spain do not present a Trunk Prefix like Germany does.
V1 Hotfix 16 (10358)
These are the fixes included in Reporting V1 hotfix 16. Definition
Filter with too many conditions failed
Status | Closed |
Id | 92762 |
A filter with too many conditions caused a buffer overrun.
V1 Hotfix 17 (10369)
These are the fixes included in Reporting V1 hotfix 17. Definition
Fixed user login page alignment
Status | Closed |
Id | 93309 |
The page was wrongly aligned.
Deletion of a large amount of CDRs didn't work
Status | Closed |
Id | 94803 |
If one tried to delete a large amount of CDRs (e.g. > 100000), the process failed without an error message.
This is fixed now, although the process lasts longer now.
PDF report creation might have failed with selected grouping
Status | Closed |
Id | 94972 |
The page count has been wrongly calculated, if the report has been grouped.
Limit web reports to prevent browser crashes
Status | Closed |
Id | 95003 |
If the shown web report is too large, some browsers are crashing.
This is now prevented by a limit to the shown calls. The report itself can still be directly downloaded without this limit.
External calls mistakenly recognised as pickup calls
Status | Closed |
Id | 95663 |
If an external connected number differs from the called number, the call has been recognized as a pickup call.
LDAP: add number resolution without percentage character
Status | Closed |
Id | 95749 |
a customer has problems with LDAP resolution and we guess the problem resides on the % character. Now the filter contains both cases, number with and without percentages.
Increased performance of database restore
Status | Closed |
Id | 94771 |
With a change of the restore process, the restore time could be reduced.
Direct report download on web interface
Status | Closed |
Id | 94935 |
For huge reports it might be usefull to directly download the report instead of viewing it in the browser first before downloading it.
Added Italian translation
Status | Closed |
Id | 95366 |
Italian translation is now available for the Linux Application Platform and its applications.
V1 Hotfix 18 (10371)
These are the fixes included in Reporting V1 hotfix 18. Definition
Mails: allow SMTP Relay without Authentication
Status | Closed |
Id | 96062 |
Mail tool was wrongly configured if user was given without password.
myPBX call list authentication works with Reporting access credentials now
Status | Closed |
Id | 96094 |
The myPBX call list authentication only worked with the Linux Web Server credentials, although it is possible to configure separate Reporting access credentials.
Now both credentials will work.
V1 Hotfix 19 (10372)
These are the fixes included in Reporting V1 hotfix 19. Definition
Save Reporting user login in browser
Status | Closed |
Id | 97621 |
The "Stay logged in" checkmark didn't work.
Report number filtering only checks first number now
Status | Closed |
Id | 97703 |
Instead of checking all numbers, just the first relevant number is checked now.
User defined filter can be deleted now
Status | Closed |
Id | 97721 |
The check if the filter can be deleted has been fixed and a user defined filter can be deleted now.
V1 Hotfix 20 (10375)
These are the fixes included in Reporting V1 hotfix 20. Definition
IE10 compatibility for web reports
Status | Closed |
Id | 99330 |
Creation of web reports in IE10 wasn't working.
Force PostgreSQL to free disk space after deletion of CDRs
Status | Closed |
Id | 99967 |
PostgreSQL does not free disk space after deletion of table data to keep the space for further usage.
Now this space is really freed after deleting CDRs.
V1 Hotfix 21 (10376)
These are the fixes included in Reporting V1 hotfix 21. Definition
Support of UTF-8 only languages like Russian
Status | Closed |
Id | 100942 |
Currently only latin1 languages were possible within the web interface. Now also UTF8 only languages are possible.
V1 Hotfix 22 (10377)
These are the fixes included in Reporting V1 hotfix 22. Definition
LDAP: traces for unset parameters
Status | Closed |
Id | 101846 |
Wrong http error strings returned on failing CDR
Status | Closed |
Id | 101969 |
There was a mismatch of error code and error string.
Retry CDR insert after broken postgresql connection
Status | Closed |
Id | 102304 |
Instead of directly returning an error, the insert is now retried one time.
V1 Hotfix 23 (10380)
These are the fixes included in Reporting V1 hotfix 23. Definition
V1 Hotfix 24 (10383)
These are the fixes included in Reporting V1 hotfix 24. Definition
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.
Fix wrongly released version number in cumulative hotfix
Status | Closed |
Id | 107872 |
The cumulative hotfix 23 contained a hotfix 22 with a wrong build number 10378.
The cumulative hotfix 24 will now replace this number with 10377 and further hotfixes will be installed correctly.
V1 Hotfix 25 (10386)
These are the fixes included in Reporting V1 hotfix 25. Definition
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...
V1 Hotfix 26 (10387)
These are the fixes included in Reporting V1 hotfix 26. 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.
V1 Hotfix 27 (10389)
These are the fixes included in Reporting V1 hotfix 27. Definition
LDAP: Name resolution did not work for local numbers
Status | Closed |
Id | 112320 |
The customer did not entry the phone number im LDAP Server including area code for local numbers.
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.
V1 Hotfix 28 (10391)
These are the fixes included in Reporting V1 hotfix 28. 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.
V1 Hotfix 29 (10396)
These are the fixes included in Reporting V1 hotfix 29. 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.
V1 Hotfix 30 (10397)
These are the fixes included in Reporting V1 hotfix 30. Definition
XML escape callback information in reports
Status | Closed |
Id | 118658 |
Otherwise the report can't be displayed.
V1 Hotfix 31 (10400)
These are the fixes included in Reporting V1 hotfix 31. 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.
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.
V1 Hotfix 32 (10401)
These are the fixes included in Reporting V1 hotfix 32. Definition
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.
V1 Hotfix 33 (10404)
These are the fixes included in Reporting V1 hotfix 33. Definition
V1 Hotfix 34 (10405)
These are the fixes included in Reporting V1 hotfix 34. Definition
LDAP: no name resolution if external line prefix was longer than one digit
Status | Closed |
Id | 138518 |
external line can be longer.
V1 Hotfix 35 (10406)
These are the fixes included in Reporting V1 hotfix 35. Definition
V1 Hotfix 36
These are the fixes included in Reporting V1 hotfix 36. Definition