Call Detail
Records (CDRs)
VoiceGuide v7
will store a log of all the calls which arrived or were made by the
system.
The CDR logs
are automatically saved in VoiceGuide's \cdr\ subdirectory, and
optionally saved to an external database or a SysLog server.
The call
information is stored in the following CDR format:
- account: An account code
designation (string)
- src: Caller*ID number
(string)
- dst: Destination extension
(string)
- dcontext: Destination
context/submenu (string)
- clid: Caller*ID with text
(string)
- channel: Channel used
(string)
- dstchannel: Destination
channel if appropriate (string)
- lastapp: Last application
if appropriate (string)
- lastdata: Last application
data (arguments) (string)
- start: Start of call
(date/time)
- answer: Answer of call
(date/time)
- hangup: End of call
(date/time)
- duration: Total time in
system, in seconds (integer)
- billsec: Total time call
is up, in seconds (integer)
- disposition: What happened
to the call: ANSWERED, NO ANSWER, BUSY (string)
- amaflags: Billing flags
(string)
Saving CDR logs to
Database
To save the
CDR logs to a database the appropriate table must be created and a
connection string to the database must be specified in VG.INI
file.
Here is a
screenshot from SQL Server 2005 showing the created the OutDialQue
database and the CallQue table:
The type of
each of the columns in the CDR table can be seen in the
screenshot.
Note that two
separate tables need to be created: CdrIn stores incoming call
details and CdrOut stores outgoing call details.
An example
VG.INI entry for a SQL Server based CDR log would be:
CDR_ODBC_ConnectString=Driver={SQL Native
Client};Server=127.0.0.1;Database=CdrLog;Uid=voiceguide;Pwd=voiceguide;
The
above CDR_ODBC_ConnectString entry must be located in the [Log] section
of the VG.INI file.