Reference9:Concept Reporting

Requirements

It is needed to have the application platform installed and running.

Installation

Download the latest version of innovaphone reporting.

Log into the application platform, go to the Applications tag, click on Upload/Update and upload the downloaded file. The installation will start automatically and the page will refresh every two seconds showing the installation process. If there is no error during the installation you will see at the end "Installation was succesfull". Otherwise, you will get "installation failed" and the reason why it went wrong.

Configuration

Device

It is required to have a Reporting license installed on your device. Check under General/License if you already have one.

Any innovaphone device which sends CDRs to the reporting application must have at least one CDR interface configured. Log into your device, click on Gateway and use the following options for the configuration of the CDR interface:

- Type: HTTP/HTTPS

- Address: ip address of the application platform

- Port: 80

- Method: POST/GET

- Path: ap/cdr.fcgi

The application platform is by default password protected and will drop the received CDRs. There are two ways to have the CDRs written in the database. Either the innovaphone Application platform URL/username/password is configured in your device under Services/HTTP/Client or you configure the "ap/cdr.fcgi" path as public in the application platform (see explation below, 3.2)

Appendix

Report XML

 <report>
   <record>
     ....
     <remote name="saturn" number="101" dn="Saturn"/>
     <status>co</status>
     <type>ct</type>
     <dir>i</dir>
     <billing-duration seconds="40">0:40</billing-duration>
     <call-duration seconds="40">0:40</call-duration>
     <conn-duration seconds="20">0:20</conn-duration>
   </record>
 </report>

• remote: outgoing calls -> dialed endpoint
• remote: incoming calls -> first ep2 above entry event or entry event if this is the first one
• remote: incoming calls with incoming transfer after entry event -> transfer target
• status: outgoing calls -> best found status in call flow
• status: incoming calls -> status of entry event
• type: the type of the entry event or, if not set, the type of the next event, if given
• dir: o (outgoing) if the first event is the entry event and the caller is ep1
• dir: i (incoming) if not o
• billing-duration: outgoing call -> duration from the first event until the last event in the flow
• billing-duration: incoming call -> duration from the first transfer/forward event until the last event in the flow
• call-duration: duration of the whole call
• conn-duration: duration from the entry event until the event, where the local endpoint isn't connected any more