Text Call Detail Records - Revision history

Luc Morissette: This applies to ProSBC as well

2023-08-14T13:00:13Z

This applies to ProSBC as well

← Older revision		Revision as of 09:00, 14 August 2023
Line 8:		Line 8:
	\|Tmedia		\|Tmedia
	\|2.8, 2.9, 2.10, 3.0, 3.2		\|2.8, 2.9, 2.10, 3.0, 3.2
			\|-
			\|SBC
			\|3.0, 3.1
	\|}		\|}

	Text [[call detail record\|call detail records]] (CDR) can be used on the [[ProSBC]], [[TMG800]], [[TMG3200]] or [[TMG7800]]. The Call Detail Records are saved in a log file on a local disk. An entry is made for each call leg, at the start of a call and at the end of the call. In addition, the system can be configured to update the CDRs periodically.		Text [[call detail record\|call detail records]] (CDR) can be used on the [[ProSBC]], [[TMG800]], [[TMG3200]] or [[TMG7800]]. The Call Detail Records are saved in a log file on a local disk. An entry is made for each call leg, at the start of a call and at the end of the call. In addition, the system can be configured to update the CDRs periodically.

Luc Morissette: Added link to version 3.2

2023-08-14T12:58:28Z

Added link to version 3.2

← Older revision		Revision as of 08:58, 14 August 2023
Line 21:		Line 21:
	== Configuration ==		== Configuration ==
	'''Refer to the appropriate Toolpack release:'''		'''Refer to the appropriate Toolpack release:'''
	*[[Toolpack:Enabling_CDR_C\|Web Portal v2.9, 2.10, 3.0: CDR configuration]]		*[[Toolpack:Enabling_CDR_D\|Web Portal v3.2: CDR configuration]]
			*[[Toolpack:Enabling_CDR_C\|Web Portal v2.9, 2.10, 3.0, 3.1: CDR configuration]]
			<div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;">
	*[[Toolpack:Enabling_CDR_B\|Web Portal v2.8: CDR configuration]]		*[[Toolpack:Enabling_CDR_B\|Web Portal v2.8: CDR configuration]]
	~~<div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;">~~
	*[[Toolpack:Enabling_CDR_A\|Web Portal v2.7: CDR configuration]]		*[[Toolpack:Enabling_CDR_A\|Web Portal v2.7: CDR configuration]]
	*[[Toolpack:Enabling_RADIUS_A\|Web Portal v2.6: CDR configuration]]		*[[Toolpack:Enabling_RADIUS_A\|Web Portal v2.6: CDR configuration]]

Luc Morissette: Removed 2.7 from most of the page

2023-06-26T13:03:21Z

Removed 2.7 from most of the page

← Older revision		Revision as of 09:03, 26 June 2023
Line 1:		Line 1:
	{{DISPLAYTITLE:Text Call Detail Records}}		{{DISPLAYTITLE:Text Call Detail Records}}
			{\| class="wikitable"
			\|-
			\|rowspan="3"\|This article applies to:
			\|'''Product'''
			\|'''Version'''
			\|-
			\|Tmedia
			\|2.8, 2.9, 2.10, 3.0, 3.2
			\|}
	Text [[call detail record\|call detail records]] (CDR) can be used on the [[ProSBC]], [[TMG800]], [[TMG3200]] or [[TMG7800]]. The Call Detail Records are saved in a log file on a local disk. An entry is made for each call leg, at the start of a call and at the end of the call. In addition, the system can be configured to update the CDRs periodically.		Text [[call detail record\|call detail records]] (CDR) can be used on the [[ProSBC]], [[TMG800]], [[TMG3200]] or [[TMG7800]]. The Call Detail Records are saved in a log file on a local disk. An entry is made for each call leg, at the start of a call and at the end of the call. In addition, the system can be configured to update the CDRs periodically.

Line 41:		Line 49:
	=== Timestamps ===		=== Timestamps ===
	@{AlertTime}: Time when the call has started ringing.		@{AlertTime}: Time when the call has started ringing.
	~~Note: Supported on release 2.7 and up only.~~
	@{AlertTime:format}: Same as @{AlertTime} but with custom print format (local time zone), using 'strftime' style, with added		@{AlertTime:format}: Same as @{AlertTime} but with custom print format (local time zone), using 'strftime' style, with added
	support for @m replaced by milliseconds.		support for @m replaced by milliseconds.
Line 51:		Line 58:
	@{ConnectedTimeUtc:format}:Same as @{ConnectedTime:format} but printed in UTC time, rather than local time zone.		@{ConnectedTimeUtc:format}:Same as @{ConnectedTime:format} but printed in UTC time, rather than local time zone.
	@{CallDuration}: Call duration in seconds (not available in the "start" CDR log)		@{CallDuration}: Call duration in seconds (not available in the "start" CDR log)
	~~Note: Supported on release 2.7 and up only.~~
	@{CallDurationMs}: Call duration in milliseconds (end - connected time) (not available in the "start" CDR log)		@{CallDurationMs}: Call duration in milliseconds (end - connected time) (not available in the "start" CDR log)
	~~Note: Supported on release 2.7 and up only.~~
	@{EndTime}: Time when the call started terminating (in number of seconds since epoch).		@{EndTime}: Time when the call started terminating (in number of seconds since epoch).
	Note: This slightly differs from the @{Timestamp}, since the 'End' CDR trace is printed once the call		Note: This slightly differs from the @{Timestamp}, since the 'End' CDR trace is printed once the call
Line 63:		Line 68:
	@{EndTimeUtc:format}: Same as @{EndTime:format} but printed in UTC time, rather than local time zone.		@{EndTimeUtc:format}: Same as @{EndTime:format} but printed in UTC time, rather than local time zone.
	@{RingingDuration}: Ringing duration in seconds (connected - start time)		@{RingingDuration}: Ringing duration in seconds (connected - start time)
	~~Note: Supported on release 2.7 and up only.~~
	@{RingingDurationMs}: Ringing duration in milliseconds (connected - start time)		@{RingingDurationMs}: Ringing duration in milliseconds (connected - start time)
	~~Note: Supported on release 2.7 and up only.~~
	@{StartTime}: Time when the call was created (in number of seconds since epoch)		@{StartTime}: Time when the call was created (in number of seconds since epoch)
	@{StartTime:format}: Same as @{StartTime} but with custom print format (local time zone), using 'strftime' style, with added		@{StartTime:format}: Same as @{StartTime} but with custom print format (local time zone), using 'strftime' style, with added
Line 83:		Line 86:
	@{CallingNumber}: Calling number		@{CallingNumber}: Calling number
	@{CallingPresentation}: Calling presentation: "Unspecified", "NotAvailable", "Allowed", "Restricted", "AddressRestricted" or "NameRestricted"		@{CallingPresentation}: Calling presentation: "Unspecified", "NotAvailable", "Allowed", "Restricted", "AddressRestricted" or "NameRestricted"
	~~Note: Supported on release 2.7 and up only.~~
	@{CallingSubscriberNumber}: Second calling number (ISDN), Generic number of type "additional calling party number" (SS7) and SIP P-asserted-identity, userinfo		@{CallingSubscriberNumber}: Second calling number (ISDN), Generic number of type "additional calling party number" (SS7) and SIP P-asserted-identity, userinfo
	~~Note: Supported on release 2.7.43 and up only.~~
	@{CallType}: Call type ("Telephony" or "VOIP")		@{CallType}: Call type ("Telephony" or "VOIP")
	@{IncomingNAP}: Name of the NAP that originated this call (incoming call leg's NAP name).		@{IncomingNAP}: Name of the NAP that originated this call (incoming call leg's NAP name).
	~~Note: Supported on release 2.7 and up only.~~
	@{NAP}: Name of the NAP this call leg is from		@{NAP}: Name of the NAP this call leg is from
	@{OriginatorName}: Direction of the call:		@{OriginatorName}: Direction of the call:
Line 94:		Line 94:
	Note: In release 2.6 and earlier, the direction of the call is as follows:		Note: In release 2.6 and earlier, the direction of the call is as follows:
	- "originate" (incoming call leg) - "answer" (outgoing call leg)		- "originate" (incoming call leg) - "answer" (outgoing call leg)
	In release 2.7, the CDR option "Reverse CDR call origin" in Gateway configuration provides the same values as release 2.6.		In release 2.7+, the CDR option "Reverse CDR call origin" in Gateway configuration provides the same values as release 2.6.
	@{OriginalCalledNumber}: Original called number		@{OriginalCalledNumber}: Original called number
	~~Note: Supported in release 2.7 and up only.~~
	@{Protocol}: Type of protocol used ("SS7", "ISDN", or "SIP")		@{Protocol}: Type of protocol used ("SS7", "ISDN", or "SIP")
	@{RedirectingNumber}: Redirecting number		@{RedirectingNumber}: Redirecting number
	~~Note: Supported in release 2.7 and up only.~~
	@{TerminationCause}: Cause of the call termination, printed as an integer value (refering enum TBCMC_CALL_REASON_CODE)		@{TerminationCause}: Cause of the call termination, printed as an integer value (refering enum TBCMC_CALL_REASON_CODE)
	@{TerminationCauseString}: Cause of the call termination, printed as a string value		@{TerminationCauseString}: Cause of the call termination, printed as a string value
Line 140:		Line 138:
	The call statistics variable enables the printing of RTP, RTCP and T38 statistics in the text CDR logs.		The call statistics variable enables the printing of RTP, RTCP and T38 statistics in the text CDR logs.
	* Available '''only in the "end" CDR entry'''		* Available '''only in the "end" CDR entry'''
	* Available in release '''2.7.103''' and above only

	Example:		Example:
Line 149:		Line 146:
	* [[Call_statistics_format_B\|Call statistics format for Toolpack 2.9 or 2.10]]		* [[Call_statistics_format_B\|Call statistics format for Toolpack 2.9 or 2.10]]
	* [[Call_statistics_format_A\|Call statistics format for Toolpack 2.8]]		* [[Call_statistics_format_A\|Call statistics format for Toolpack 2.8]]
	* [[Call_statistics_format_A\|Call statistics format for Toolpack 2.7.103 or later]]

	=== Information related to routing ===		=== Information related to routing ===

Allyntree: general edit

2021-07-08T14:54:25Z

general edit

Show changes

Luc Morissette: Added title

2021-07-02T13:45:36Z

Added title

← Older revision		Revision as of 09:45, 2 July 2021
Line 1:		Line 1:
			{{DISPLAYTITLE:Text Call Detail Records}}

	Text [[call detail record\|call detail records]] (CDR) can be used on the [[ProSBC]], [[TMG800]], [[TMG3200]] or [[TMG7800]]. The Call Detail Records are saved in a log file on a local disk. There is an entry done for each call leg, at the start of a call and at the end of the call. In addition, the system can be configured to update the CDRs periodically.		Text [[call detail record\|call detail records]] (CDR) can be used on the [[ProSBC]], [[TMG800]], [[TMG3200]] or [[TMG7800]]. The Call Detail Records are saved in a log file on a local disk. There is an entry done for each call leg, at the start of a call and at the end of the call. In addition, the system can be configured to update the CDRs periodically.

Luc Morissette: Added ProSBC. Removed the Notes - this dated back previous to 2011

2021-07-02T13:41:38Z

Added ProSBC. Removed the Notes - this dated back previous to 2011

← Older revision		Revision as of 09:41, 2 July 2021
Line 1:		Line 1:
	Text [[call detail record\|call detail records]] (CDR) can be used on the [[TMG800]], [[TMG3200]] or [[TMG7800]]. The Call Detail Records are saved in a log file on a local disk. There is an entry done for each call leg, at the start of a call and at the end of the call. In addition, the system can be configured to update the CDRs periodically.		Text [[call detail record\|call detail records]] (CDR) can be used on the [[ProSBC]], [[TMG800]], [[TMG3200]] or [[TMG7800]]. The Call Detail Records are saved in a log file on a local disk. There is an entry done for each call leg, at the start of a call and at the end of the call. In addition, the system can be configured to update the CDRs periodically.

	The format of the CDR traces is defined by configuration, using variables that are replaced by the Gateway application when writing to the log.		The format of the CDR traces is defined by configuration, using variables that are replaced by the Gateway application when writing to the log.
Line 190:		Line 190:
	== Redundancy ==		== Redundancy ==

	In a [[TMG7800]] configuration, with redundant TMG-Control servers, or [[TMG3200]]/[[TMG800]] in 1+1 configuration, only the active server writes the CDR logs. Since the active server may change over time, CDR parsing must take into account that CDR logs may be found in files from the two servers.		In a [[TMG7800]] configuration, with redundant TMG-Control servers, or [[TMG3200]]/[[TMG800]] and [[ProSBC]] in 1+1 configuration, only the active server writes the CDR logs. Since the active server may change over time, CDR parsing must take into account that CDR logs may be found in files from the two servers.


	The analysis of the logs for the purpose of extracting billing information must be done after combining the two logs, from both ~~TMG-Control~~ servers, sorting the entries by timestamp for example. See how to [[TMG:Retrieve_Text_CDR\|Retrieve Text CDR here]].		The analysis of the logs for the purpose of extracting billing information must be done after combining the two logs, from both servers, sorting the entries by timestamp for example. See how to [[TMG:Retrieve_Text_CDR\|Retrieve Text CDR here]].

	== CDR entry loss due to switchover ==		== CDR entry loss due to switchover ==
Line 206:		Line 206:

	There are 2 ways to retrieve the text CDR manually or automatically. The procedures are described in [[TMG:Retrieve_Text_CDR\|Retrieve Text CDR]].		There are 2 ways to retrieve the text CDR manually or automatically. The procedures are described in [[TMG:Retrieve_Text_CDR\|Retrieve Text CDR]].

	~~== Notes ==~~
	*This mode of operation is not recommended for [[TMG800]] or [[TMG3200]] with a flash disk (last shipment January 2011). However, the [[TMG800]] or [[TMG3200]] with SATA or SSD disk option is OK (use command [[Get Product Type\|tbinfo]]: if the command can be executed, the disk is SATA or SSD).
	*TelcoBridges does not recommend storing CDR logs via network file systems (NFS or other). We highly recommend writing to a local hard drive and have developed a background script that moves the gzipped log segments for backup or analysis.

	[[Category:Revise on Major]]		[[Category:Revise on Major]]

Luc Morissette: /* Information related to signaling */

2019-12-19T15:47:05Z

Information related to signaling

← Older revision		Revision as of 11:47, 19 December 2019
Line 82:		Line 82:
	@{CallingPresentation}: Calling presentation: "Unspecified", "NotAvailable", "Allowed", "Restricted", "AddressRestricted" or "NameRestricted"		@{CallingPresentation}: Calling presentation: "Unspecified", "NotAvailable", "Allowed", "Restricted", "AddressRestricted" or "NameRestricted"
	Note: Supported on release 2.7 and up only.		Note: Supported on release 2.7 and up only.
	@{CallingSubscriberNumber}: Second calling number (ISDN) or Generic number of type "additional calling party number" (SS7)		@{CallingSubscriberNumber}: Second calling number (ISDN), Generic number of type "additional calling party number" (SS7) and SIP P-asserted-identity, userinfo
	Note: Supported on release 2.7.43 and up only.		Note: Supported on release 2.7.43 and up only.
	@{CallType}: Call type ("Telephony" or "VOIP")		@{CallType}: Call type ("Telephony" or "VOIP")

Abrassard: /* Timestamps */

2019-01-29T14:51:36Z

Timestamps

← Older revision		Revision as of 10:51, 29 January 2019
Line 40:		Line 40:
	@{AlertTime}: Time where the call has started ringing.		@{AlertTime}: Time where the call has started ringing.
	Note: Supported on release 2.7 and up only.		Note: Supported on release 2.7 and up only.
			@{AlertTime:format}: Same as @{AlertTime} but with custom print format (local time zone), using 'strftime' style, with added
			support for @m replaced by milliseconds.
			Example format: %Y-%m-%d %H:%M:%S.@m -> 2009-09-02 12:16:24.333
	@{ConnectedTime}: Time where the call was answered (and connected with another leg) (in number of seconds since epoch)		@{ConnectedTime}: Time where the call was answered (and connected with another leg) (in number of seconds since epoch)
	@{ConnectedTime:format}: Same as @{ConnectedTime} but with custom print format (local time zone), using 'strftime' style, with added		@{ConnectedTime:format}: Same as @{ConnectedTime} but with custom print format (local time zone), using 'strftime' style, with added

Manon Bélanger: /* Information related to signaling */

2018-03-27T12:52:37Z

Information related to signaling

← Older revision		Revision as of 08:52, 27 March 2018
Line 108:		Line 108:
	@{SipCallId}: Content of the "call-id" SIP header		@{SipCallId}: Content of the "call-id" SIP header
	@{ChargeIndicator}: For TDM (SS7 and CAS R2); received charge indicator in Alert message.		@{ChargeIndicator}: For TDM (SS7 and CAS R2); received charge indicator in Alert message.
			@{LocalSipIP}: For SIP calls, IP address locally used for this call leg.
			Note: Supported on release 3.0.70 and up only.
			@{LocalSipPort}: For SIP calls, UDP port locally used for this call leg.
			Note: Supported on release 3.0.70 and up only.
			@{RemoteSipIP}: For SIP calls, IP address of the remote peer for this call leg.
			Note: Supported on release 3.0.70 and up only.
			@{RemoteSipPort}: For SIP calls, UDP port of the remote peer for this call leg.
			Note: Supported on release 3.0.70 and up only.

	=== Information related to media ===		=== Information related to media ===

Luc Morissette: /* Configuration */

2018-03-26T20:20:01Z

Configuration

← Older revision		Revision as of 16:20, 26 March 2018
Line 11:		Line 11:
	== Configuration ==		== Configuration ==
	'''Refer to the appropriate Toolpack release:'''		'''Refer to the appropriate Toolpack release:'''
	*[[Toolpack:Enabling_CDR_C\|Web Portal v2.9: CDR configuration]]		*[[Toolpack:Enabling_CDR_C\|Web Portal v2.9, 2.10, 3.0: CDR configuration]]
	*[[Toolpack:Enabling_CDR_B\|Web Portal v2.8: CDR configuration]]		*[[Toolpack:Enabling_CDR_B\|Web Portal v2.8: CDR configuration]]
			<div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;">
	*[[Toolpack:Enabling_CDR_A\|Web Portal v2.7: CDR configuration]]		*[[Toolpack:Enabling_CDR_A\|Web Portal v2.7: CDR configuration]]
	*[[Toolpack:Enabling_RADIUS_A\|Web Portal v2.6: CDR configuration]]		*[[Toolpack:Enabling_RADIUS_A\|Web Portal v2.6: CDR configuration]]
			</div>

	== CDR Text Variables ==		== CDR Text Variables ==