Parsed Command Information

Timing Information

Timing information is reported first and usually takes the form:

hr:min:sec.fracts.sequence

For example: 11:12:25.512934.0000827C

The sequence field counts each event added to the history entries and is unique over all history buffers. Gaps in the sequence numbers occur when events occur in other history buffers. Sequence numbers are displayed in hex and wrap at 0xffffffff.

Event Descriptions

Each line gives information about some event that took place within the driver. If a packet is sent or received, a line specifies the direction. All or some of the packet data are displayed, and as much as possible is parsed and displayed.

Interactions between applications and the driver are usually via ioctl commands, which are shown starting with the word Ioctl.

Parsed Command Information

In both Bfv API debug mode output and dump history output, commands appear parsed. In the history output, it appears after a message saying whether the packet was sent or received, the packet data, and a length value preceded by the letter 'L'. In Bfv API debug mode output, it appears after a '>'(greater then symbol) or '<' (less than symbol); indicating sent or received.

The commands in a packet appear one at a time (usually just one per packet). Indented under each command are all of its tagged values (often just called tags). List tags contain their own tags which are further indented. For example.

(01)ADMIN (08) EVENT (03) FW_DOWNLOAD_FINISHED

(79)CURRENT_STREAM [01: Fix Uns Short Unitless] 0000

(09)DOWNLOAD_RESULT [01: Fix Uns Short Unitless] 0000

November 2009

98

Page 98
Image 98
Dialogic 6.2 manual Parsed Command Information, Timing Information, Event Descriptions