Cdr
The Cdr event is only raised when the cdr_manager backend is loaded and registered with the CDR engine.
Note
This event can contain additional fields depending on the configuration provided by cdr_manager.conf.
AccountCode- The account code of the Party A channel.Source- The Caller ID number associated with the Party A in the CDR.Destination- The dialplan extension the Party A was executing.DestinationContext- The dialplan context the Party A was executing.CallerID- The Caller ID name associated with the Party A in the CDR.Channel- The channel name of the Party A.DestinationChannel- The channel name of the Party B.LastApplication- The last dialplan application the Party A executed.LastData- The parameters passed to the last dialplan application the Party A executed.StartTime- The time the CDR was created.AnswerTime- The earliest of either the time when Party A answered, or the start time of this CDR.EndTime- The time when the CDR was finished. This occurs when the Party A hangs up or when the bridge between Party A and Party B is broken.Duration- The time, in seconds, of EndTime - StartTime.BillableSeconds- The time, in seconds, of AnswerTime - StartTime.-
Disposition- The final known disposition of the CDR.NO ANSWER- The channel was not answered. This is the default disposition.-
FAILED- The channel attempted to dial but the call failed.Note
The congestion setting in
cdr.confcan result in theAST_CAUSE_CONGESTIONhang up cause or theCONGESTIONdial status to map to this disposition. -
BUSY- The channel attempted to dial but the remote party was busy. ANSWERED- The channel was answered. The hang up cause will no longer impact the disposition of the CDR.CONGESTION- The channel attempted to dial but the remote party was congested.AMAFlags- A flag that informs a billing system how to treat the CDR.OMIT- This CDR should be ignored.BILLING- This CDR contains valid billing data.DOCUMENTATION- This CDR is for documentation purposes.UniqueID- A unique identifier for the Party A channel.UserField- A user defined field set on the channels. If set on both the Party A and Party B channel, the userfields of both are concatenated and separated by a;.
User Notes
No notes yet. Be the first to contribute a tip or example.
Contribute a note
Share a tip, gotcha, or practical example. Keep it under 2000 characters. No questions (use the Asterisk community forums for support). Wrap code in backticks.