Events: QSIG

	Event Structure	What is a BOP event ?...
	QSIG decoding	by using Clarinet Event-Editor with a filter ...
	Protocol stack	Which protocol specifications to be defined in the current filter ?...
	Standards	ETSI ETS 300 172
	Options	Changing the display format in the current filter ?...

qsig_decod.gif (9519 octets)

Event information	Date:	Date of the event (end of BOP frame) in the format: hh:mm:ss/xxx.y
	N	The interface number which identifies the Clarinet-interface connected to the host.
	Link type	TS: Signalling Link Transmit direction RS: Signalling Link Receive direction TD: Data Link Transmit direction RD: Data Link Receive direction
	Dx	The decoding level as specified in the filter (protocol stack).
Protocol fields	QSIG	Pro-Id CallRef <PDU type> Ctrl

Pro-Id

Protocol discriminator 08h.

CallRef

Call reference in the following format: Ref:(x,yy yy)

O (origin) or D (destination).

yy or yy yy

reference number in hexadecimal; 2 octets in PRI (E1 or T1).

<PDU_type>

Type of message.

Ctrl

Attached IE's are displayed according to the the display mode selected in the filter :

Identified mode	IE:(c/xx) len:y >> designation value
Detailed mode	IE:(c/xx) len:y >> designation octet 3 : ...... octet i : bkl field ...... octet j : info octet n : ......
Data field length = 0	no IE display

ASN.1 decoding of an IE content can be displayed either in detailed or BER mode.

Codeset.

IE code (octet 1).

Length of IE content (from octet 3).

designation

Designation of IE according to the standard.

value

Only with Identified mode, IE content (from octet 3) in hexadecimal.

bkl_field

Only with Detailed mode, every field is displayed with its bit configuration within the relevant octet and its meaning according to the standard.

info

Only with Detailed mode, conveyed information.

qsig_stack.gif (7239 octets)

updated: 27-Feb-04