...
Message type | Meaning |
LoadAdapter | This message reports that the card is installed and loaded correctly. |
SIG-EVENT | Examples: The SIG-EVENT FFFF messages indicate a low-level problem, usually to do with cabling or the Diva card not successfully communicating with the NT1 or the switch. On occasions this message can be caused by a faulty Diva card configuration. |
D-X | "D" channel messages (uninterpreted), complete with LAPD and Q.931 headers. D-X=transmitted by the Diva card; D-R=received by the Diva card. |
MDL-ERROR | These are normally low-level D-channel protocol violations detected by the Diva card. They normally indicate a serious problem with the ISDN line, your ISDN supplier's equipment or the provisioning (configuration) of the line. More information on MDL Errors. |
B-X | "B" channel messages. If the content is PPP, some decoding and interpretation is done for you. |
SIG-X | These are basically signalling ("D" channel) messages, but come from a higher layer in the Diva code, and have some interpretation of the data, e.g. call SETUPs have all the information elements decoded so that you don't have to do it manually. These are the most interesting messages if you are quickly scanning through the trace looking for a problem |
CAPI20_GET | These are the CAPI_GET_MESSAGE and CAPI_PUT_MESSAGE operations from a CAPI 2.0 application using the Diva card. Some of the values are broken-out from the CAPI message structure, and the actual CAPI message type is decoded (e.g. LISTEN_REQ, INFO_IND, DATA_B3). The first few bytes of the message (if any) are decoded on the line below. |
EVENT | These messages often amplify failed operations on the Diva card, so they are a good source of information |
L1_UP | These messages indicate that the physical layer is established (or not) between the Diva card and the NT1 (network connection). |
...
STEP 1: Use the Diva Trace to find the message "LoadAdapter" in the Initialisation sequence.
To capture the initialisation sequence of the Diva board follow the instructions on the page How to take a Diva trace
This LoadAdapter message reports that the Diva board is installed and loaded correctly.
...
In this example, the first two lines show normal D-channel idle activity in both directions, and then at line 3, the network resets the LAPD level by sending a SAMBE. This unexpected reset is detected by the Diva card as an MDL error (according to the definitions for ISDN, for example in the ETSI specification). The type of the error is 'F', which means 'received SABME, Peer initiated re-establish'.