Page 322 - Asterisk™: The Future of Telephony
P. 322
dst
Destination extension.
dcontext
Destination context.
clid
Caller ID with text (80 characters).
channel
Channel used (80 characters).
dstchannel
Destination channel, if appropriate (80 characters).
lastapp
Last application, if appropriate (80 characters).
lastdata
Last application data (arguments, 80 characters).
start
Start of call (date/time).
answer
Answer of call (date/time).
end
End of call (date/time).
duration
Total time in system, in seconds (integer), from dial to hangup.
billsec
Total time call is up, in seconds (integer), from answer to hangup.
disposition
What happened to the call (ANSWERED, NO ANSWER, BUSY).
amaflags
What flags to use (DOCUMENTATION, BILL, IGNORE, etc.), specified on a per-channel
basis, like accountcode. AMA flags stand for Automated Message Accounting flags,
which are somewhat standard (supposedly) in the industry.
userfield
A user-defined field, maximum 255 characters.
Storing CDRs in a Database
CDRs can also be stored in a database. Asterisk currently supports SQLite, PostgreSQL,
MySQL, and unixODBC, but we will cover only ODBC in this book (see Chapter 12).
Many people prefer to store their CDRs in a database, so that queries can be run to help
with billing and resource management.
294 | Chapter 13: Managing Your Asterisk System