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

Bug Fixes

reporting callback request from mypbx may crash with uninitialized reporting config

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