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

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

New Features

Linux: LDAP query if no name available in CDR

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

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	To-decide
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	To-decide
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	To-decide
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	To-decide
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. Status: Hallo Daniel,

ich verwende Call Duration für die Summary. Sollte passen.

Gruss,

Sergio

reporting: conn, call and billing time calculation

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

it is needed if you have more than one trunk.