[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Fields in the H.248 Messages

Each H.248 message contains the following fields:

TRACE_TIMESTAMP
[BEGIN #SEQNUM  TIMESTAMP  5-TUPLE  DIRECTION  MSG_SIZE]
MegacoMessage
[END #SEQNUM]

The following is a sample ServiceChange message:

Oct 10 09:32:28
[BEGIN #778  Oct 10 09:32:28  UDP:10.50.40.100:2944->172.16.1.1:2944  TX  168]
AU=0x00000000:0x00000000:0x000000000000000000000000
!/1 [10.50.40.100]:2944
T=1{
C=-{
SC=ROOT{
SV{MT=RS,RE="901",AD=2944,PF=JNPR_PGCP/1,V=3,20071010T09322800}}}}
[END #778]

Table 16 describes the fields in H.248 messages.

Table 16: Description of Fields in H.248 Messages

Field	Description
TRACE_TIMESTAMP	Time the messaged was captured. The timestamp is in the format HH:MM:SS.mmmmmm
BEGIN	Constant string BEGIN that indicates the beginning of a message.
#SEQNUM	Sequential number of the message used to correlate the BEGIN header with the END footer.
TIMESTAMP	Date and time of the message. Time is displayed in the format HH:MM:SS.mmmmmm
5-TUPLE	UDP or TCP packet’s 5-tuple (transport protocol, source address and port, destination address and port). Used to identify the VPG and the PGC that exchanged the message.
DIRECTION	Direction message was sent from the VPG: TX for an outgoing H.248 message. RX for an incoming H.248 message.
MSG_SIZE	Size of message in bytes excluding transport protocol (UDP/TCP/IP) overhead.
MegacoMessage	Captured data including the interim authentication header (if any).
END	Constant string END that indicates the end of a captured message.

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]