5.3.1. Setting Information Elements
The information elements (IEs) sent to the network must conform to the switch-specific recommendations. Use the assumptions described in the following paragraphs when constructing IEs. See also Section 2.31, gc_SetInfoElem( ).
Assumption 1
Variable length IEs must be provided in ascending order in the Public part, as shown in Table 39.
Network Specific Facilities 0x20 Display 0x28 Signal 0x34 Assumption 2
A single byte IE (with the exception of a LOCKING Shift IE) can be placed anywhere in the message. This includes Type 1 (NON-LOCKING Shift) and Type 2 elements. The NON-LOCKING shift should cause the code shift in the forward direction only. For example, when in codeset "3," the NON-LOCKING shift should add an element in codeset "4." See Table 40 for Type 1 settings and Table 41 for Type 2 settings.
Network Specific Facilities 0x20 0 Shift 0x9E 6 (NON-LOCKING) IPU 0x76 6 Display 0x28 0 Signal 0x34 0
Network Specific Facilities 0x20 0 Sending Complete 0xA1 0 (Single Byte IE) Display 0x28 0 Signal 0x34 0 Assumption 3
A LOCKING Shift IE must be placed after all the IEs when a lower codeset is included. A NON-LOCKING Shift IE or another LOCKING Shift IE of a greater codeset value can follow the IE. See Table 42 for two options for setting LOCKING Shift IEs.
Assumption 4
User-supplied IEs (with the exception of CHANNEL_ID_IE, see below) take precedence over the Firmware-defined IEs, even those that are in private IE parts.
Assumption 5
The CHANNEL_ID_IE will always be taken from the Firmware-defined section.
Assumption 6
When Single Byte IEs and NON-LOCKING Shift IEs occur in both the User-supplied and Firmware-defined sections, the value is taken from the User-defined section. However, this value will be inserted at the position defined by the firmware when the firmware has a specific requirement for the position.
Click here to contact Telecom Support Resources
Copyright 2003, Intel Corporation