ReleaseNotes9: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

New Features

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.

Bug Fixes

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.

V1 Hotfix 2 (10197)

These are the fixes included in Reporting V1 hotfix 2. Definition

New Features

reporting: postgresql-8.4 debian package update

Status	Closed
Id	66271

debian update for postgresql 8.4.

Bug Fixes

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.

V1 Hotfix 3 (10201)

These are the fixes included in Reporting V1 hotfix 3. Definition

Bug Fixes

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

New Features

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.

Bug Fixes

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.

V1 Hotfix 5 (10276)

These are the fixes included in Reporting V1 hotfix 5. Definition

New Features

reporting: send reports per email

Status	To-decide
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.

reporting: logo and footer for pdf reports

Status	To-decide
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.

Bug Fixes

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.

V1 Hotfix 6 (10282)

These are the fixes included in Reporting V1 hotfix 6. Definition

New Features

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	To-decide
Id	75760

under diagnostics kann man ein email senden. So überprüft man ob emails verschickt werden.

reporting: call duration and alert duration in filter settings

Status	To-decide
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	To-decide
Id	75903

it is now possible to configure the mail client on Linux to send mails via Exchange.

Bug Fixes

reporting: mails were not sent in vm installations

Status	To-decide
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	To-decide
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	To-decide
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	To-decide
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.

V1 Hotfix 7

These are the fixes included in Reporting V1 hotfix 7. Definition