Thanks for the reply. Most of what you have provided makes sense and I've already been using the fields as described.
For the call direction you said to use field 13. It looks like leg #1/3 is always set to "answer" and leg #2/4 is always set to "originate" though so I'm still not sure how to reliably determine direction based on that. Any ideas?
For Status, I'm trying to determine one of the following but I'm not seeing anything in the document that provides this:
Connected
No Answer
Busy
Error
Voice Mail
Thanks,
Darcy
It's not obvious but you can find out most of them
I'm working on an application that receives CDR files from a Cisco UC560 device (File Accounting). I have the following document:
"CDR Accounting for Cisco IOS Voice Gateways" that lists the fields available in the CSV file that is FTP'd to my service.
I need to display the calls that were made in a way that is easy for end users to understand:
http://www.cisco.com/en/US/docs/ios/voice/cdr/developer/guide/cdrcsv.html
Time of Call
113
String
Feature invocation time.
10
Disconnect time in NTP format: hour, minutes, seconds, microseconds, time_zone, day,
month, day_of_month, year.
, Calling#
21 clid
Calling number.
, Called#
22
Called number.
, Call Direction,
13
Gateway's
behavior in relation to the connection that is active for this leg.
answer = Legs 1 and 3 --> incoming leg
originate =Legs 2 and 4 --> ougoing leg
callback = Legs 1 and 3
Type,
3 leg-type
Call leg type:
1=Telephony
2=VoIP
3=MMOIP
4=Frame Relay
5=ATM
Status,
???
90 feature-op-status
Success(0) or failure (1).
Duration,
Field 10 - field 113
I've checked the Cisco site but can't find any examples of how to determine the different call scenarios that are found in the files. For example, what characteristics tell me that this is an inbound call vs. and outbound call.
Is there a document or sample code available that discusses the File Accounting format in more detail?
Thanks