CDR reports

[backe]

Hi!

Regarding CDR reports, I have a question.
How do you deal with calls that are not established (that have rang on dialed number, but haven’t been answered), and in CDR you have that call lasted a period of time (e.g. 4 tenths of minute).

I can not charge this call.

How can, customer know which calls are established?

 

[tlpeter]

how can you charge a call that isn't been there ?

 

[backe]

The point is:
When the destination phone has rang for e.g. 15 seconds, and hasn’t been answered, on CDR I get that the call has lasted 2 tenths of minute.
Based on CDR I should charge this call, but I can not do that, because there was no conversation.
The customer is not satisfied, because CSR and real traffic don’t mach.

 

[kavsagol]

To what CDR are you referring to - The DR you set up in the System tab or SMDR records from Delta Server?

 

[dhibsystel]

Hi,

if you use IP OOFICE, Like SMDR records
(field : CALL_DURATION), if the trunk or the line that the IP OFFICE use for the external calls is ANALOGIC trunk, ip office doesn't can't distinct between the begin of the call( begin ringing ) and when the other side take down the call, otherwise, if you have numeric line, ip office can distinct between the too duration ( ring duration and call duration ) and what you will see is the real time conversation.

I have develope an application with smdr, if you need you can try it !

 

[backe]

I use CDR I’ve set up in the System tab.

If that's no trouble for you, dhibsystel, I could try it.
You can send mi on ipavaya@gmail.com

 

[kavsagol]

I have been using the system CDR in the following setting:

Format - Unformated
Record Options: Normal

I don't have the problem you describe, but an opposite one: The CDR reports the call length in segments of 6 seconds (10th of a minute), but it truncates them: A call of 15 seconds will be calculated as a call of 12 seconds. Calls which were not answered will give a value of 0, calls which are shorter than 6 seconds will also have a value of 0.

IMO Avaya put the CDR function because someone nagged them about it, and they didn't think it all the way through. I have never seen a CDR system that rounds the length of the calls downwards, except for IPO's.

 

[sizbut]

Each CDR record includes a "Condition Code" element, which uses a single letter to indicate the result of the call. That includes indicatign calls that rang but then hung up and calls that rang against busy destinations.

 

[kavsagol]

The condition code works only for outgoing calls, I need to keep t rack of incoming calls as well.

 

[backe]

I use Expanded (enhanced) CDR format
And I always in "Condition Code" get:
- 9 - Identifies an incoming external call
- A - Identifies an outgoing external call

I'll try with Unformated (normal) and let you know.

 

[sizbut]

The condition code works only for outgoing calls, ..."

If you thinks thats the case, then you have a bug. Condition codes are used for all call type including incoming and internal.

 

[dhibsystel]

Hi,

You Can look at this :

* Condition Code
The condition code indicates what type of call the record describes. For example, condition code C indicates a conference call, 7 indicates an ARS call, etc. The table below shows condition codes for most record formats. The 59-character format uses different condition codes from those used for other record types.

Description

0 - Identifies an outgoing intra-switch call (a call that originates and terminates on the switch).

9 I Identifies an incoming external call.
A - Identifies an outgoing external call.
C L Identifies a conference call.
E N An incomplete external call, due to all trunks being busy or out of service. Incoming trunk calls to a busy terminal do not generate a CDR record.
G - Indicates a call terminating to a ringing station.
H - Indicates that a ringing call that was then abandoned.
I - Indicates a call attempt to a busy station.
CDR can also record the ring time to answer or abandon for incoming calls originated by the trunk group. In addition, CDR indicates if the incoming destination is busy. This record is separate from the normal call duration record printed for an answered call. This information is indicated by the condition code.

When an incoming call is terminated to an internal destination, the call is tracked from the time ringing feedback is given to the originator. If the call is answered, a CDR record is printed with the condition code G and the duration reflects the time between the start of ringing and the answer of the call. If the call is abandoned before being answered, the system prints a record with the condition code H and the duration reflects the time between the start of ringing and the time the call was abandoned. If the destination is busy, a CDR record is printed with the condition code I and a duration of 0.

* Dialed Number
This field contains the number dialed. If it is an outgoing call, the field contains the number dialed by a system user. If it is an incoming call, the field contains the extension that was dialed. If more than 18 digits are dialed, the least significant digits (starting from the right) are truncated.

* Duration
This is the duration of the call or call segment. It is recorded in hours, minutes and tenths of minutes. Calls are rounded down in 6-second increments. Therefore, a call of 5-second duration will be indicated as 0 duration. If 9999 appears in this field, this call was in progress when a time change was made in the witch

http://www.carrollcommunications.com/manager/cdrrecords.html

 

[kavsagol]

I just made some tests with the CDR, I have IPO 3.1(65). I made two incoming calls and two outgoing calls, and there was absolutely no difference between the answered and unanswered calls. I tried unformatted, both normal and enhanced.