4.3.1. Retrieving Nonstandard Data From Protocol Messages
The following messages use nonstandard data:
- Setup (H.245)
- Facility (Q.931)
- H.245 message with nonstandard data (H.245)
Table 9 indicates when nonstandard information (object ID and data) should be retrieved for each type of message.
Table 9. Retrieving Nonstandard Data and ID from Messages
|
Message Elements
|
Message Type
|
When Information can be Retrieved
|
How to Retrieve the Information
|
| Nonstandard Object ID and Data |
Setup message (H.245) |
When GCEV_OFFERED is received. |
Use gc_Extension( ) with the GETINFO extension ID. |
| Nonstandard Object ID and Data |
Facility (Q.931) |
When GCEV_EXTENSION event is received. |
Retrieve the message information from the metaevent associated with the GCEV_EXTENSION event. |
| Nonstandard Object ID and Data |
H.245 message with nonstandard data (H.245) |
When GCEV_EXTENSION event is received. |
Retrieve the message information from the metaevent associated with the GCEV_EXTENSION event. |
- Note: The nonstandard object ID and data associated with a Setup message should be retrieved immediately after the corresponding event since there is the possibility of the arrival of a facility message that could override the nonstandard object ID and data values.
