Filter
Top Products
Appendix D – BRI Supplemental Services
441
As an example, to invoke Supplemental Service ‘X’, the cc_SndMsg( ) function
with msg_type = SndMsg_Facility could be used. The Information Element
would be defined in a data structure as follows:
ieblk.length = 11;
ieblk.data[0] = 0x1c; /* IE Identifier */
ieblk.data[1] = 0x09; /* Length of information */
ieblk.data[2] = 0x91; /* Protocol Profile */
/* information */
ieblk.data[3] = 0xa1; /* Component Type */
ieblk.data[4] = 0x06; /* Component Length */
ieblk.data[5] = 0x02; /* invoke tag id */
ieblk.data[6] = 0x01; /* invoke tag length */
ieblk.data[7] = 0x00; /* invoke id */
ieblk.data[8] = 0x02; /* operation tag */
ieblk.data[9] = 0x01; /* operation length */
ieblk.data[10] = 0x06; /* operation */
NOTE:
The information included in the Information Element is dependent on the
Supplemental Service being invoked.
The data sent to the switch would be formatted as follows:
87654321
Protocol Discriminator
Call Reference Value
Information
Information
Protocol Profile
Length of Information
IE Identifier
System-
Supplied
Data
User-
Supplied
Data
Message Type
Figure 12. Information Element Format
Information elements can also be sent using the cc_SetInfoElem( ) function,
which allows the BRI board to send application-specific information elements in
the next outgoing message. (For more information, see the cc_SetInfoElem( )
function description.)