Asterisk CDR - Revision history

Pchero: /* See also */

2019-09-23T09:40:43Z

Pchero: /* Variables */

2018-11-22T16:03:56Z

Variables

← Older revision		Revision as of 16:03, 22 November 2018
Line 94:		Line 94:
	* ${CDR(lastapp)}: Last app executed.		* ${CDR(lastapp)}: Last app executed.
	* ${CDR(lastdata)}: Last app's arguments		* ${CDR(lastdata)}: Last app's arguments
	* ${CDR(start)}: ~~Timethe~~ call started.		* ${CDR(start)}: Time the call started.
	* ${CDR(answer)}: Time the call was answered.		* ${CDR(answer)}: Time the call was answered.
	* ${CDR(end)}: Time the call ended.		* ${CDR(end)}: Time the call ended.

Pchero: /* Semantics and Syntax */

2018-11-21T15:48:30Z

Semantics and Syntax

← Older revision		Revision as of 15:48, 21 November 2018
Line 25:		Line 25:
	When a channel hangs up, all CDRs associated with it are implicitly fiinalized. When all CDRs for a channel are finalized, the CDRs are Dispatched to the backends for storage.		When a channel hangs up, all CDRs associated with it are implicitly fiinalized. When all CDRs for a channel are finalized, the CDRs are Dispatched to the backends for storage.

	=== Creation ===		=== CDR Lifetime ===

			==== Creation ====
	A CDR record is created in any one of the following situations.		A CDR record is created in any one of the following situations.
	* Whenever a channel is created.		* Whenever a channel is created.
Line 71:		Line 73:
	==== Dispatch ====		==== Dispatch ====
	When a CDR is dispatched, all CDRs associated with the channel are committed to permanent storage. The CDRs at this point are removed from memory.		When a CDR is dispatched, all CDRs associated with the channel are committed to permanent storage. The CDRs at this point are removed from memory.

			=== Fields ===
			==== AMA Flags ====
			AMA Flags are set on a channel and are conveyed in the CDR. They inform billing systems how to treat the particular CDR. Asterisk provides no additional semantics regarding these flags - they are present simply to help external systems classify CDRs.
			* OMIT
			* BILLING
			* DOCUMENTATION

	== Variables ==		== Variables ==

Pchero: /* See also */

2018-11-21T15:36:50Z

Pchero: /* Finalization */

2018-11-20T12:28:19Z

Finalization

← Older revision		Revision as of 12:28, 20 November 2018
Line 68:		Line 68:

	If at any point the Party A channel for a CDR is hung up, all CDR records for that Party A are dispatched.		If at any point the Party A channel for a CDR is hung up, all CDR records for that Party A are dispatched.

			==== Dispatch ====
			When a CDR is dispatched, all CDRs associated with the channel are committed to permanent storage. The CDRs at this point are removed from memory.

	== See also ==		== See also ==

Pchero: /* Bridging */

2018-11-20T12:27:27Z

Bridging

@@ Line 49: / Line 49: @@
 : If the channel entering the bridge is the Party B, the other channel has a CDR with a Party B, and this channel is not that CDR's Party B, then the existing CDR is finalized and a new CDR is created for that other channel with this channel as the Party B.
 * If a third party joins the bridge with Party A and Party B, the process choosing the Party A channel is repeated for each pairing of channels. Thus, in a three-way call there will be three CDR records; in a four-way call there will be six record.
 == See also ==

Pchero: /* Semantics and Syntax */

2018-11-20T11:31:03Z

Semantics and Syntax

← Older revision		Revision as of 11:31, 20 November 2018
Line 24:		Line 24:

	When a channel hangs up, all CDRs associated with it are implicitly fiinalized. When all CDRs for a channel are finalized, the CDRs are Dispatched to the backends for storage.		When a channel hangs up, all CDRs associated with it are implicitly fiinalized. When all CDRs for a channel are finalized, the CDRs are Dispatched to the backends for storage.

			=== Creation ===
			A CDR record is created in any one of the following situations.
			* Whenever a channel is created.
			* Whenever a channel leaves a bridge and is not hung up.
			* When a CDR is forked from a prior record.
			* When a channel enters a multi-party bridge.
			* When a channel dials more than one channel.

			When it is created, a CDR inherits the uniqueid and linkedid from its Party A channel, and a new sequence number is generated. When created as a result of a dial operation, the channel acting as the caller is always the Party A.

			==== Dialing Parties ====
			When a channel is known to dial other channels, a CDR is created for each dial attempt. The dial status is recorded for each dial attempt as a CDR Disposition. Note that all dial attempts may be dispatched depending on the CDR configuration. The caller is always the Party A in the created CDRs.

			==== Bridging ====
			If a channel is bridged with another channel, the following procedure is performed.
			* The CDR is marked as having entered a bridge. If there is no other channel in the bridge, the CDR waits for another channel to join.
			* For each pairing of channels, the channels are compared to determine which is the Party A channel and which is the Party B channel.
			: If the channel entering the bridge is the Party A, the CDR has a Party B, and the channel it is bridged with is the Party B, the CDR continues.
			: If the channel entering the bridge is the Party A, the CDR has a Party B, and the channel is not already the Party B, the current CDR is finalized and a new CDR is created for the relationship between the two parties. Note that the original CDR will be re-activated if the existing Party B enters the bridge.
			: If the channel entering the bridge is the Party A, the CDR has no Party B, then the channel it is bridged with becomes the Party B.
			: If the channel entering the bridge is the Party B, the other channel has a CDR with no Party B, this channel becomes the Party B and existing CDR is finalized.
			: If the channel entering the bridge is the Party B, the other channel has a CDR with a PArty B, and this channel is that CDR's Party B, then the existing CDR is finalized and the other channel's CDR activated.
			: If the channel entering the bridge is the Party B, the other channel has a CDR with a Party B, and this channel is not that CDR's Party B, then the existing CDR is finalized and a new CDR is created for that other channel with this channel as the Party B.
			* If a third party joins the bridge with Party A and Party B, the process choosing the Party A channel is repeated for each pairing of channels. Thus, in a three-way call there will be three CDR records; in a four-way call there will be six record.

	== See also ==		== See also ==

Pchero: /* Basic */

2018-11-20T10:54:32Z

Basic

@@ Line 3: / Line 3: @@
 == Basic ==
-Asterisk 12 부터 CDR 내용이 변경되었다.
+Asterisk-12 부터 CDR 내용이 변경되었다.
 * Individual components in Asterisk no longer modify CDRs directly. CDRs are produced based on the state of the channels and bridges within Asterisk. As a result, there is much greater degree of consistency in CDRs throughout Asterisk, regardless of the application channels happen to be executing in.
 * The behaviour of CDRs between multiple parties is now defined.
 * Depending on how channels are dialed and bridged, multiple CDRs will be created for a given call. Post-processing of these records will be required to determine the overall statistics of the call.
 [[category:asterisk]]

Pchero at 09:53, 20 November 2018

2018-11-20T09:53:51Z

← Older revision		Revision as of 09:53, 20 November 2018
Line 1:		Line 1:
	== Overview ==		== Overview ==
	Asterisk CDR(Call Detail Record) 내용 정리.		Asterisk CDR(Call Detail Record) 내용 정리.

			== Basic ==
			Asterisk 12 부터 CDR 내용이 변경되었다.
			* Individual components in Asterisk no longer modify CDRs directly. CDRs are produced based on the state of the channels and bridges within Asterisk. As a result, there is much greater degree of consistency in CDRs throughout Asterisk, regardless of the application channels happen to be executing in.
			* The behaviour of CDRs between multiple parties is now defined.
			* Depending on how channels are dialed and bridged, multiple CDRs will be created for a given call. Post-processing of these records will be required to determine the overall statistics of the call.

	[[category:asterisk]]		[[category:asterisk]]

Pchero: Created page with "== Overview == Asterisk CDR(Call Detail Record) 내용 정리. category:asterisk"

2018-11-20T09:45:35Z

Created page with "== Overview == Asterisk CDR(Call Detail Record) 내용 정리. category:asterisk"

New page

== Overview ==
Asterisk CDR(Call Detail Record) 내용 정리.

[[category:asterisk]]

← Older revision		Revision as of 09:40, 23 September 2019
Line 108:		Line 108:
	* https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification		* https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification
	* https://wiki.asterisk.org/wiki/display/AST/CDR+Variables		* https://wiki.asterisk.org/wiki/display/AST/CDR+Variables
			* https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Function_CHANNEL

	[[category:asterisk]]		[[category:asterisk]]

@@ Line 71: / Line 71: @@
 ==== Dispatch ====
 When a CDR is dispatched, all CDRs associated with the channel are committed to permanent storage. The CDRs at this point are removed from memory.
 == See also ==
 * https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification
 [[category:asterisk]]