195.5 Technical Clarification

The following standard trace points and their corresponding trace object types are defined for message tracing:

OS calls ON_P_SEND_MESSAGE_N, ON_P_SEND_MESSAGE_I, ON_P_SEND_MESSAGE_P, ON_P_SEND_MSG_N_NO_FREE, ON_P_SEND_MSG_I_NO_FREE, ON_P_SEND_MSG_P_NO_FREE with object type SD

OS calls ON_P_RECEIVE_MESSAGE and ON_P_ACCEPT_MESSAGE, with object type RCV

LAN trace point in the trace interface procedure in LAN subsystem.This LAN trace interface procedure is called by the various LAN layers with corresponding object types: ETHRV, ETHSD, TCP, TPI, IPDSD, IPDRV

If an error is detected during tracing, the tracer enters in the trace buffer a data record with an error indication. In the case of the display commands with TYPE=ALL these error indications are visible; they are indicated by the fact that a hexadecimal number is specified as the object type.

This hexadecimal number consists of 2 bytes:

•

first Byte indicates the type of Error

–

first hexadecimal digit indicates Group of conditions, which is affected


1st digit of 1st byte	meaning
0	insignificant
1	Error in Group 1
2	Error in Group 2
3	Error in Group 3
4	Error in Group 4

–

second hexadecimal digit is an Error code


2nd digit of 1st byte	meaning	comment
1	nr. of comparison positions incorrect	the tracer administration variables have been destroyed
5	Message length incorrect	an inadmissible message token was transferred to the tracer
6	Offset incorrect for token	an inadmissible message token was transferred to the tracer
8	Trace point inadmissible	the tracing routine was branched to from a point which does not coincide with the scheduled trace points
A	Number of condition groups incorrect	the tracer’s administration data has been (number of condition groups implausible) destroyed

•

second Byte indicates involved Object type


errorcode 2nd byte	object type	comment
00	SD	an attempt was made to trace the message contents for a SEND_MESSAGE call
01	RCV	an attempt was made to trace the message contents for a RECEIVE_MESSAGE call
07	TIME	an attempt was made to trace time information
16	TPI	an attempt was made to trace the data of the TPI LAN layer
17	TCP	an attempt was made to trace the data of the TCP LAN layer
1A	IPDSD	an attempt was made to trace the data of IP Dual Port Ram Send
1B	IPDRV	an attempt was made to trace the data of IP Dual Port Ram Receive
1C	ETHSD	an attempt was made to trace the data of a protocol header of the outgoing frame in the ethernet driver
1D	ETHRV	an attempt was made to trace the data of a protocol header of the incoming frame in the ethernet driver

In the subsystem LAN there are 4 tracepoints:


TPI:	This tracepoint makes it possible for the user to protocol and analyze connection specific one ( the relevant) part of the interface between the LAN subsystem and its users (OS,CMS) . The activation of this tracepoint supplies instructive informations for clearing if an error occurs inside or outside of the LAN subsystem.
TCP:	Via this tracepoint, again connection specifically, the calls to the protocol layer TCP itself and their processing can be watched. This tracepoint will supply necessary advisories for analyzing lost connections or problems concerning the build up of connections, keepalive functions, resource problems and so on.
ETHSD, ETHRV:	For analyzing protocol data (Ethernet, IP, TCP, ICMP, ARP) the tracepoint ETHSD can be used for outgoing packages and the ETHRV for incoming packages. Both tracepoints provide exactly these (protocol) data, which were sent to or received from LAN. The Ethernet driver has no memory for connections, therefore the tracepoints are not connection specific. Further the protocolling of user data at this points it does not make sense, because TCP does NOT work message oriented.

OpenScape 4000 V10, Volume 1: AMO Descriptions, Service Documentation, Issue 5, ID: P31003H31A0S107057620

© 09/2025 Mitel Networks Corporation. - All rights reserved.
Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG. All other trademarks herein are the property of their respective owners.