PBX setup · Asterisk

Connect Asterisk to TIM4biz

Asterisk powers a huge family of phone systems — FreePBX, FusionPBX, Issabel and custom builds. TIM4biz consumes the standard Asterisk CDR record so every Asterisk-based platform is supported the same way, on Linux, Docker or in the cloud.

Asterisk project Features list Report examples

Create your TIM4biz account

Start with a trial account. We'll send your Asterisk collector details once you're set up.

Create your TIM4biz trial account at account sign up.
We'll send your Asterisk collector credentials to you. These include the TIM4biz CDR host, port and account identifier used by your Asterisk CDR backend.
Enable the Asterisk CDR backend and confirm all standard fields are written, as described below.
Sign in to your TIM4biz account to view your reports. Reports can be run interactively on the website and can be scheduled to be automatically emailed to you.

Asterisk CDR configuration

All standard CDR fields are required. Make sure your Asterisk CDR backend (cdr_csv, cdr_odbc, cdr_adaptive_odbc or your distro's equivalent) is enabled and writing the fields below for every call.

Configure: cdr.conf / cdr_adaptive_odbc.conf — then reload with module reload cdr on the Asterisk CLI.

Field	Description
`accountcode`	An account code associated with the Party A channel.
`src`	The Caller ID number.
`dst`	The destination extension.
`dcontext`	The destination context.
`clid`	The Caller ID text.
`channel`	The name of the Party A channel.
`dstchannel`	The name of the Party B channel.
`lastapp`	The last application the Party A channel executed.
`lastdata`	The application data for the last application the Party A channel executed.
`start`	The time the CDR was created.
`answer`	The time when Party A was answered, or when the bridge between Party A and Party B was created.
`end`	The time when the CDR was finished, when either party hangs up, or when the bridge between parties is broken.
`duration`	The time in seconds from start until end.
`billsec`	The time in seconds from answer until end.
`disposition`	The final known disposition of the CDR record. See CDR dispositions for possible values.
`amaflags`	A flag specified on the Party A channel. See AMA records for possible values.
`userfield`	User-defined field. If set on both Party A and Party B channels, the userfields are concatenated and `;` separated.
`uniqueid`	A unique identifier for the Party A channel.
`linkedid`	A unique identifier that unites multiple CDR records. See linkedid propagation for more details.
`peeraccount`	The account code of the Party B channel.
`sequence`	A numeric value that, combined with uniqueid and linkedid, can be used to uniquely identify a single CDR record.

After reloading the CDR module, place a test call and confirm a row appears in your CDR backend. TIM4biz will then pick the record up and report on it.

‹ Back to supported PBX list

Need help connecting Asterisk?

Our support team can walk you through the CDR backend setup for FreePBX, FusionPBX, Issabel or your custom Asterisk build.

Contact support