VOS3000 CDR text files
Besides its database, VOS3000 can write every call to a plain text file each hour, ready for your own billing or analysis scripts.
Updated · By the VOS3000 Web team
Quick answer: With the softswitch parameter SS_CDR_RECORD_TO_FILE set to On, VOS3000 also writes every CDR to a text file, one file per hour named YYYYMMDDHH.txt in the cdr folder of the installation directory. Each line is one call with 19 fields, from caller and callee to end reason and PDD.
- Turn on
- SS_CDR_RECORD_TO_FILE = On
- File name
- YYYYMMDDHH.txt, one per hour
- Hold time
- In milliseconds
- Zero-second calls
- Only with SS_CDR_RECORD_NONCONNECT on
Turn it on
In the VOS3000 desktop client, open Operation management → Softswitch management → Additional settings → System parameter and set SS_CDR_RECORD_TO_FILE to On. To include calls with 0 seconds of talk time (failed and unanswered calls), also set SS_CDR_RECORD_NONCONNECT to On.
Where the files are
The softswitch writes the files into the cdr folder under its installation directory, one file per hour, named YYYYMMDDHH.txt. The file 2026112114.txt holds the calls that ended between 14:00 and 15:00 on 21 November 2026.
The fields
Each line is one call, with these fields in this order:
| # | Field | Meaning |
|---|---|---|
| 1 | callerE164 | Caller number |
| 2 | calleeE164 | Callee number |
| 3 | startTime | Start time, such as 2026-11-21 14:20:18 |
| 4 | stopTime | End time |
| 5 | holdTime | Talk time in milliseconds |
| 6 | endReason | End reason code; see the lookup |
| 7 | endDirection | Who hung up: 0 caller, 1 callee, 2 server |
| 8 | callerGatewayId | Calling (mapping) gateway |
| 9 | calleeGatewayId | Called (routing) gateway |
| 10 | callerIp | Caller IP |
| 11 | calleeIp | Callee IP |
| 12 | callerAccessE164 | Caller number as received |
| 13 | calleeAccessE164 | Callee number as received |
| 14 | callerToGatewayE164 | Caller number as sent out |
| 15 | calleeToGatewayE164 | Callee number as sent out |
| 16 | calleeBilling | Billed by: 0 caller, 1 callee |
| 17 | billingMode | -1 no billing, 0 phone number, 1 gateway ID, 3 phone card |
| 18 | callerPdd | Time from receiving the call to connecting it |
| 19 | calleePdd | Time from sending the call to the route's response |
Fields 12 to 15 show your dial plans at work: compare the numbers as received with the numbers as sent out.
Using the files
- Copy the finished hour's file to your billing or analysis system every hour.
- Watch disk space: the files are not your billing record, so archive or delete old ones.
- SERVER_CDR_FILE_WRITE_INTERVAL and SERVER_CDR_FILE_WRITE_MAX control a second, optional set of CDR files written by the VOS3000 server: how often a new file starts (60 to 86400 seconds) and how many are kept (2048 by default).
For searching CDRs, exporting to Excel, and the CDR link for your own systems, see VOS3000 CDR.
Questions about this topic
How do I export VOS3000 CDR to text files automatically?
Set the softswitch parameter SS_CDR_RECORD_TO_FILE to On. VOS3000 then writes one text file per hour in the cdr folder of its installation directory.
Is holdTime in seconds?
No, in milliseconds. Divide by 1000 for seconds.
Are failed calls in the CDR text files?
Calls with 0 seconds of talk time are only written when SS_CDR_RECORD_NONCONNECT is on.
Try every step in the live demo
Each screen in this guide is in the VOS3000 Web demo, with made-up data. Sign in with demo / demo.
Keep reading
Search and read CDR
Find calls, read every CDR column and understand termination reasons.
Termination reason lookup
Type a code like -55 or 486, or a name, and see what it means.
System parameters
Where the SERVER_ and SS_ parameters are, and the billing, CDR and call ones worth knowing.
Reports and analysis
Revenue, clearing and gateway reports, and which one answers which question.