The Send Codeset 6/7 LAI IE field is independent of the Supplementary Service Protocol and UUI Treatment settings to allow additional flexibility. Communication Manager can have a mix of trunk groups set with non-QSIG or QSIG protocol and with service-provider or shared settings. Calls interflowed over the shared non-QSIG trunk groups contain the data items to be forwarded with the call in the UUI IE while calls interflowed over the non-QSIG service-provider trunk groups do not contain the data items, except for ASAI which can always be sent in UUI. Calls interflowed over the QSIG trunk groups always have MSI user information, except for ASAI where the transport method depends on the UUI treatment setting.

When a call is LAI interflowed over a non-QSIG service-provider trunk group, the Send Codeset 6/7 LAI IE field being active results in just the LAI IE being forwarded with the call in a SETUP message. When interflowed over a non-QSIG shared trunk group, setting the Send Codeset 6/7 LAI IE field to y includes a codeset 6/7 LAI IE in the SETUP message in addition to the same LAI information included as shared data in the UUI IE. You can set the LAI information fields to blank on the Priorities screen to exclude the data items from the UUI IE. When interflowed over a QSIG service-provider or shared trunk group with the Send Codeset 6/7 LAI IE field active, the LAI information is included as both MSI and in the LAI IE. However, in this case there is no mechanism to eliminate the duplication of data if the codeset 6/7 LAI IE is required.

The combinations can be used when calls are LAI interflowed to Communication Manager previous to the switch with existing ASAI applications using ASAI provided UUI that cannot be using the LAI IE. Note that codeset 6/7 IEs are not defined for QSIG and other vendor switch treatment of calls with a LAI IE is undefined can be ignored, blocked, or misinterpreted.

When the trunk group is set to non-QSIG and shared or to QSIG with service-provider or shared, do not set the Send Codeset 6/7 LAI IE field to y due to the overhead of sending duplicate information. In some cases, the configuration can exceed the SETUP message or user information byte count limits for the network and result in the user information being dropped. Also, transport can cost more in networks which charge for user transport by quantity of bytes transported. An administration warning message displays when the combination is set for the trunk group. In fact the combination is not recommended except in very limited cases where a mix of early and later switches can be reached over the same trunk group, using a public or switched private network, using LAI, and where BSR or UCID is not active or is being used and the data that must be forwarded with the call can be limited to that supported by the network.

The Send Codeset 6/7 LAI IE field must not be set to y with trunk groups where calls will be interflowed over public networks or virtual private networks that do not support codeset 6/7 transport. In such cases, the codeset 6/7 IE is not forwarded or the calls cannot be routed by the network. This can happen in some international situations, notably over networks in Germany.