TSP Lab	SgaINCDR - IN CDR Assembler module	SgaINCDR

The IN CDR Assembler and KPI generator module
`("SgaINCDR")`

Basic Operation

Periodically scans the working directory for Sga-8025.xxx files, created by the SgaINCDSorter module
Assembles the messages in connection with the same transaction, defined by the Transaction ID (TID)
When the BEGIN is missing, yellow warning lines appear in the log
CDRs created from the complete transactions are written into the log
From the CDRs KPIs are created and written into *.PMS files periodically
Aborts (and Errors) generate alarms, written into alarm files

User Interface

The main menu

Menu	Menuitem	Shortcut(s)	Meaning
[Log]
	Find line containing...	(Ctrl-F)	Find text in log window
	Find next matching line	(F3)	Find next occurrence of text in log window
	Details		Detail level of logging (Off, Normal, Detailed or Debug)
[Actions]
	Go on / Pause	(Ctrl-P, or )	Allow periodic scanning of the working directory for `Sga-8025.xxx` files
	Flush CDR and error counters into log		Actual values of the CDR and error counters are written into the log
	Flush & reset CDR and error counters		Actual values of the CDR and error counters cleared after written into the log
[Options]
	Auto scroll	(ScrollLock, or )	Allow automatic scrolling of the log screen
	Save settings		Save actual settings into the configuration (`SgaINEvD.INI`) file

The bottom status-line

Uptime: time elapsed since module has been started up.
Reading: name of the actual input Sga-8025.xxx file.
MSUs: number of processed MSUs
CDRs: number of complete CDRs
Active transactions: number of transactions that have BEGIN and are not complete yet
Error counters:
- E1: number of messages without a BEGIN (yellow line in the log: "No BEGIN has been seen for the above ABORT.")
- E2: increased when a new BEGIN arrives when the number of the active transactions is reached the SgaINCDR.ini/[Advanced]/dwMaxActiveTransactionCount (Red colored "Too many active transactions!" in the log.)
- E3: TID reuse counter (yellow line in the log)
- E7: number of timed-out transactions (yellow line in the log)
  - with late answer: the answer for the BEGIN arrived later than SgaINCDR.ini/[Advanced]/dwTransactionTimeOut1Sec
  - without any result: the answer for the BEGIN arrived later than SgaINCDR.ini/[Advanced]/dwTransactionTimeOut2Sec (or there was no answer at all)
PMS stats:
- encountered: number of CDRs in the actual PMS stat file
- overflown: if the number of keys in the actual PMS file reached the SgaINCDSorter.ini/[Advanced]/dwMaxStatKeyCount the new keys will be dropped and counted here
- keys: current number of stat keys in the actual PMS file

Details of the log

15:32:59.536 2005.11.30 21:49:52.461 E10/EN3<<< 2/203/713: CONT 960001CE 2C0001CF PC=00CB Invoke (ID:#2) / ConnectToResource

15:32:59.536: Time of logging
2005.11.30 21:49:52.461: Timestamp of the message
E10/EN3<<<: Monitor ID / Link ID / direction of the message
2/203/713: Network Indicator / Destination Point Code / Originating Point Code
CONT: TCAP message type
960001CE: Originating Transaction ID
2C0001CF: Destination Transaction ID
PC=00CB: SCCP/GT (if there is no GT, a virtual GT is created based on the Originating Point Code)
Invoke (ID:#2): TCAP component (invoke ID)
ConnectToResource: INAP operation type

No BEGIN has been seen for the above ABORT.

There has not been BEGIN for this ABORT message. (Yellow lines.)

2005.11.30 21:49:56.980 ....../E00>>> 2/713/208: SK=12 C5000147 30000 ms ---> OK

2005.11.30 21:49:56.980: Timestamp of the BEGIN message
....../E00>>>: Link ID and direction of the BEGIN message
2/713/208: Network Indicator / Destination Point Code / Originating Point Code: parameters of the Begin
SK=12: Service Key parameter in the BEGIN messages
C5000147: Originating Transaction ID of the BEGIN message
30000 ms: Time out (SgaINCDSorter.ini/[Advanced]/dwTransactionTimeOut2Sec)
OK: Status, can be:
- OK: all messages arrived (Black lines.)
- TIME-OUT (w/ late answer): there is answer for the BEGIN but it is later than SgaINCDSorter.ini/[Advanced]/dwTransactionTimeOut1Sec (Yellow lines.)
- TIME-OUT (w/o any result): there is not any answer in SgaINCDSorter.ini/[Advanced]/dwTransactionTimeOut2Sec for the BEGIN (Yellow lines.)
- END/Reject: an END is received but the transaction is rejected (Yellow lines.)
- END/RetErr: the answer is a Return Error (Yellow lines.)

The output statistics file

Date: Date of the stastitics
Time: Beginning of the time interval
SK: Service key for that statistics key
DPC: Destination Point Code
OPC: Originating Point Code
Begin: Number of BEGIN messages for that key
End_OK: Number of normal END-ed transactions
UDTS: Number of UDTS messages
AbortD: Number of Aborted transactions where the Abort arrived from Destination direction
PAbortD: Number of P-Aborted transactions where the Abort arrived from Destination direction
UAbortD: Number of User-Aborted transactions where the Abort arrived from Destination direction
AbortO: Number of Aborted transactions where the Abort arrived from Originating direction
PAbortO: Number of P-Aborted transactions where the Abort arrived from Originating direction
UAbortO: Number of User-Aborted transactions where the Abort arrived from Originating direction
RetErr: Number of Return Errors
Reject: Number of Rejected transactions
TimeOut: Number of Begins without any answer in SgaINCDSorter.ini/[Advanced]/dwTransactionTimeOut2Sec
LateAns: Number of late answers for Begins (SgaINCDSorter.ini/[Advanced]/dwTransactionTimeOut1Sec)
TIDreus: Number of Transaction ID reuse-es
Exit: Number of active transactions closed on exit
EndInX: Number of transactions ended with other cause

The output alarm file

Details of a sample line in the alarm file:

10:43:27.897: Time of logging
2005.11.30 21:49:53.636: Timestamp of the message that caused the alarm
E10/EN1<<< Monitor ID / Link ID / direction of the message
2/203/713: Network Indicator / Destination Point Code / Originating Point Code: parameters of the Begin
P-ABORT: TCAP message type
DA0001CD: Transaction ID
PC=00CB: SCCP/GT (if there is no GT, a virtual GT is created based on the Originating Point Code)
UnrecognizedTransactionID: Cause value if there is

Configuration (`SgaINCDSorter.ini`) file settings

Section	Entry	Example	Meaning
[Position]
	iLeft	140	Position of the program module on the display screen
	iTop	72	Position of the program module on the display screen
	iWidth	995	Position of the program module on the display screen
	iHeight	694	Position of the program module on the display screen
[Options]
	bAutoScroll	True	(Refer to the `[Options]/Auto scroll` menuitem!)
[Advanced]
	wLogDetailLevel	3	(Equals to the listed order; refer to the `[LOG]/Details menuitem!)`
	wMaxCPUUsagePercent	25	Limit of CPU-usage for this module
	dwMaxLinesInLogWindow	1000	Number of lines in the log window on screen
	dwTransactionTimeOut1Sec	15	Time out for answer of BEGINs
	dwTransactionTimeOut1Sec	90	Time out for complete transactions
	dwMaxActiveTransactionCount	1000	Number of active transaction at the same time
	dwFlushStatPeriod	300	Period of closing the PMS stat files
	dwFlushStatDelay	120	After closing stat files a delay is applied before writing out the file
	dwMaxStatKeyCount	25000	Maximum number of statistical keys in the PMS files
	sStatPath	d:\StatFiles	Path for the PMS stat files
	sLogFilesPath	d:\LogFiles	Path for the LOG files
	sTrapFilesPath	d:\Files	Path for the trap files
	sAlarmFilesPath	d:\AlarmFiles	Path for the alarm files

Version history

v0.94

(c) ABORT's from the originating (BEGIN) side are encountered as well. Note that temporary file ("Sga-8025.SAW") is not compatible with previous versions.

v0.93

(c) "OK" result lines are no longer logged in Normal log level.
(c) Log files' name is changed from "SgaINCDRGen_YYYYMMDD.log" to "SgaINCDR_YYYYMMDD.log" (according to the module's name).
(c) Alarm files' name is changed from "SgaINCDRGen_Alarms_YYYYMMDD.txt" to "SgaINCDR_Alarms_YYYYMMDD.txt" (according to the module's name).

v0.91

(c) "No BEGIN has been seen for the above CONT/END." warnings are no longer logged, neither is E1 incremented in this case.
(n) New menu "Actions", with new menu items: "Flush CDR and error counters into log", and "Flush & reset CDR and error counters".
(c) "Go on / Pause" menu item is moved from menu "Options" to "Actions".
(n) Clear key (NumPad-5) clears highlight (selection) in log window.

v0.90

The IN CDR Assembler and KPI generator module("SgaINCDR")

Basic Operation

User Interface

The main menu

The bottom status-line

Details of the log

15:32:59.536 2005.11.30 21:49:52.461 E10/EN3<<< 2/203/713: CONT 960001CE 2C0001CF PC=00CB Invoke (ID:#2) / ConnectToResource

No BEGIN has been seen for the above ABORT.

2005.11.30 21:49:56.980 ....../E00>>> 2/713/208: SK=12 C5000147 30000 ms ---> OK

The output statistics file

The output alarm file

Configuration (SgaINCDSorter.ini) file settings

Version history

The IN CDR Assembler and KPI generator module
`("SgaINCDR")`

Configuration (`SgaINCDSorter.ini`) file settings