PBXware 2.x
FAQs
  General
  Backup & Restore
  Codecs
  Conferencing
  Conf Files
  Destinations
  DID
  Extensions
  IVR
  Licencing
  Monitor
  Music On Hold
  MySQL
  System Daemon
  OSC (Online Self Care)
  Protocols
  Providers
  Queue
  Networking
  Reports
  Servers
  Setup Wizard
  Sounds
  System
  SSH
  TFTP
  Trunks
  UAD
  Voicemail
  Zaptel
  Agents
  Enhanced Services
  Fax
  Cabling
  Presentation
  SM Settings
CDR Database Structure in Static/ODBC Mode

In Static/ODBC mode, which is the recommended mode of work, PBXware uses
MySQL 4.0 for database.

To access that database:

cd /home/servers/sitemanager

sh/mysql --password=$(cat sh/lib/mysql)

When inside,

show databases;

the command will show several databases, among which you will have
pbxware_xxx databases, where xxx are the numbers of your tenant prefix.
So, if you have 5 tenants you will have 5 pbxware_xxxx tables.

Let's say that you have a tenant with prefix 100.

use pbxware_100;

will use that tenant's database.

Now: show tables will show all the tables in this database. CDRs
database is named "cdr".

If you type: show fields from cdr;
you will get list of fields which are pretty self explanatory but here

http://www.voip-info.org/wiki/view/Asterisk+billing


you have most of the fields explained. The ones that are not:


tenant - tenant on which the call was made

billamount - how much the call was billed

accountcode - the extension which is making call and can be different
from src field

userfield - extension which received a call and can be diferrent then
dst field. in userfield sometimes you could have recording if queue
agents are in question


uniqueid - is a link to recording which is essentially a timestamp when
the call was recorded.


 
End User Pricing
Unlimited stock
Please register

This website uses cookies. By using this website, you consent to the use of these cookies. View policy I agree