575 4182


PBXware 3.x
  General
  Backup & Restore
  Codecs
  Conferencing
  Conf Files
  Destinations
  DID
  Networking
  Extensions
  IVR
  Licencing
  Monitor
  Music On Hold
  MySQL
  System Daemon
  OSC (Online Self Care)
  Protocols
  Providers
  Queues
  TFTP
  Trunks
  Reports
  Setup Wizard
  Servers
  Sounds
  System
  SSH
  UAD
  Voicemail
  Agents
  Enhanced Services
  Cabling
  SM Settings
  Presentation
CDR Table Structure

Although Bicom Systems doesn't support direct reading from PBXware database, CDR table is sometimes needed for customers to read directly from it. To understand the structure of the table, we are presenting the description of table fields:

  • AcctId - Auto-incremented number of the CDR record
  • tenant - Number of the tenant on which call occured (3 characters or NULL if non-MT)
  • clid - Caller ID name (80 characters)
  • src - Caller ID number (string, 80 characters)
  • dst - Destination extension (string, 80 characters)
  • dcontext - Destination context (string, 80 characters)
  • channel - Channel used (80 characters)
  • dstchannel - Destination channel (80 characters)
  • lastapp - Last application used (80 characters)
  • lastdata - Last application arguments (80 characters)
  • calldate - Start date/time of the call (date)
  • duration - Total time of call, in seconds (integer)
  • billsec - Total time the call is up, in seconds (integer)
  • billamount - Total billing of the call based on billsec
  • disposition - What happened to the call: ANSWERED, NO ANSWER, BUSY, FAILED, UNKNOWN
  • amaflags - What flags to use: DOCUMENTATION, BILL, IGNORE, specified per channel basis
  • accountcode - What account number to use: Asterisk billing account (string, 20 characters)
  • uniqueid - Unique ID of the CDR which uses linux time stamp
  • userfield - A user-defined field (string, 255 characters)

 
End User Pricing
Unlimited stock
Please register