Text Call Detail Records - Revision history

Luc Morissette: /* Information related to signaling */

2019-12-19T15:47:05Z

Information related to signaling

2019-01-29T14:51:36Z

Timestamps

2018-03-27T12:52:37Z

Information related to signaling

2018-03-26T20:20:01Z

Configuration

2018-01-17T14:46:10Z

update text

2017-12-22T12:58:43Z

Information related to signaling

2017-09-11T20:47:54Z

LM Removed the *. They were formatting characters, but unnecessary when 'space' is used

2017-05-26T01:16:18Z

Statistics

2016-09-12T17:31:57Z

Changed tbproduct for tbinfo to support TSBC3000-680 and TSBC3000-2700 products

2016-04-29T17:49:50Z

@@ Line 82: / Line 82: @@
   @{CallingPresentation}:    Calling presentation: "Unspecified", "NotAvailable", "Allowed", "Restricted", "AddressRestricted" or "NameRestricted"
                               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.
   @{CallType}:               Call type ("Telephony" or "VOIP")

@@ Line 40: / Line 40: @@
   @{AlertTime}:              Time where the call has started ringing.
                               Note: Supported on release 2.7 and up only.
   @{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

@@ Line 108: / Line 108: @@
   @{SipCallId}:              Content of the "call-id" SIP header
   @{ChargeIndicator}:        For TDM (SS7 and CAS R2); received charge indicator in Alert message.
 === Information related to media ===

@@ Line 11: / Line 11: @@
 == Configuration ==
 '''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_A|Web Portal v2.7: CDR configuration]]
 *[[Toolpack:Enabling_RADIUS_A|Web Portal v2.6: CDR configuration]]
 == CDR Text Variables ==

@@ Line 21: / Line 21: @@
 === Variables used for identifying call (or call leg) in general ===
   @{StatusType}:             Indicates the type of record ("Start", "Update" or "End").
-  @{LegId}:                  Unique Id for this leg (32 bits value, but may eventually be upgraded to 64 bits value).
+  @{LegId}:                  Unique Id for this leg (32 bits value).
   @{OtherLegId}:             Id of the other call leg joined with current call leg.
   @{SessionId}:              Unique call identifier for two joined and answered call legs, including failed outgoing call attempts (route retry)

@@ Line 95: / Line 95: @@
   @{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
-  @{OriginalCause}:          Original cause of the call termination, printed as a string value (refering enum TBCMC_CALL_REASON_CODE)
+  @{OriginalCause}:          Original cause of the call termination (before it was converted to protocol-specific cause for current call leg), printed as a string value (refering enum TBCMC_CALL_REASON_CODE)
   @{TerminationSource}:      Identifies the cause of the leg termination:
                                 - "TermInd":       Terminating indication has been received on this leg

@@ Line 131: / Line 131: @@
 Refer to the following pages for the list of statistics:
-* [[Call_statistics_format_B|Call statistics format for Toolpack 2.9 or later]]
+* [[Call_statistics_format_C|Call statistics format for Toolpack 3.0 or later]]
 * [[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]]

@@ Line 194: / Line 194: @@
 == 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 tbproduct: if the command can be executed, the disk is SATA or SSD).
+*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]]

← Older revision		Revision as of 17:49, 29 April 2016
Line 196:		Line 196:
	*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 tbproduct: if the command can be executed, the disk is SATA or SSD).		*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 tbproduct: 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.		*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]]