Dialogic Global Call IP Benutzerhandbuch
258
Dialogic Corporation
{
case IPPARM_TSM_CONTENT_EVENT:
printf("\tReceived TSM in message type: %s\n",
parm_data_ext.value_buf);
break;
case IPPARM_TSM_CONTENT_EVENT:
printf("\tReceived TSM in message type: %s\n",
parm_data_ext.value_buf);
break;
case IPPARM_TUNNELEDSIGNALMSG_CONTENT:
printf("\tReceived extension data (TSM) Msg Content: %s\n",
parm_data_ext.value_buf);
break;
printf("\tReceived extension data (TSM) Msg Content: %s\n",
parm_data_ext.value_buf);
break;
case IPPARM_TUNNELEDSIGNALMSG_PROTOCOLOBJID:
printf("\tReceived extension data (TSM) PROTOCOL_OBJID:
%s\n", parm_data_ext.value_buf);
break;
printf("\tReceived extension data (TSM) PROTOCOL_OBJID:
%s\n", parm_data_ext.value_buf);
break;
case IPPARM_TUNNELEDSIGNALMSG_ALTERNATEID:
printf("\tReceived extension data (TSM) TUNNELPROTOCOL_ALTID:
%s\n", parm_data_ext.value_buf);
break;
printf("\tReceived extension data (TSM) TUNNELPROTOCOL_ALTID:
%s\n", parm_data_ext.value_buf);
break;
// Additional cases for optional NSD
...
...
}
}
}
4.19
Retrieving User-to-User Information Elements from
H.323 Messages
H.323 Messages
Various ITU-T recommendations specify User-to-User Information Elements (UU-IE), which may
be contained in a number of different call control messages. The Global Call H.323 call control
library allows applications to receive UU-IE in six types of H.225 messages: Setup, Call
Proceeding, Alerting, Connect, Release Complete, and Facility. The library does not provide
facilities to set and send a UU-IE in an outgoing call control message. UU-IE is retrieved and
passed to the application in raw (ASN.1) format; it is the application’s responsibility to convert the
information from ASN.1 format as appropriate.
be contained in a number of different call control messages. The Global Call H.323 call control
library allows applications to receive UU-IE in six types of H.225 messages: Setup, Call
Proceeding, Alerting, Connect, Release Complete, and Facility. The library does not provide
facilities to set and send a UU-IE in an outgoing call control message. UU-IE is retrieved and
passed to the application in raw (ASN.1) format; it is the application’s responsibility to convert the
information from ASN.1 format as appropriate.
The ability to receive UU-IE from incoming H.225 messages is implemented as an optional feature
that is disabled by default for backwards compatibility. The ability to receive UU-IE can only be
enabled when starting the system; once enabled, the feature cannot be disabled without restarting
the system. The feature can be enabled for any virtual board by setting a specific bitmask value in a
field of the appropriate
that is disabled by default for backwards compatibility. The ability to receive UU-IE can only be
enabled when starting the system; once enabled, the feature cannot be disabled without restarting
the system. The feature can be enabled for any virtual board by setting a specific bitmask value in a
field of the appropriate
data structure.
When the UU-IE retrieval feature is enabled, Global Call uses the metaevent mechanism to forward
the UU-IE to an application along with the state change event associated with the supported H.225
message type (or an Extension event in the case of a Facility message). The UU-IE content is
handled as a Global Call parameter element in the extension data that is associated with the
metaevent.
the UU-IE to an application along with the state change event associated with the supported H.225
message type (or an Extension event in the case of a Facility message). The UU-IE content is
handled as a Global Call parameter element in the extension data that is associated with the
metaevent.