Event Reporting and
“shared”. The UUI for ASAI is packed within the shared UUI before it is sent over an ISDN trunk, and is unpacked at the other end.
This is transparent to the ASAI adjuncts, with two exceptions:
1.If the maximum size UUI allowed on the ISDN trunk is exceeded, then the lower priority data items will be dropped. Whether or not this means that ASAI UUI is dropped depends on the priorities of the data items. These priorities are administered on each trunk group form. Each item stored in shared UUI uses two extra bytes.Therefore, if the ISDN trunk group is administered to allow a shared UUI length of 32 bytes then the ASAI UUI will be limited to 30 bytes instead of 32.
2.If a service provider, or customer equipment other than a DEFINITY ECS (R6.3 or later) will be interpreting the contents of the UUI IE, then the trunk group used to place those calls should have its UUI IE Treatment set to
For more information, see the Section, ‘‘Integrated Services Digital Network (ISDN),’’ in Chapter 12, ‘‘ASAI and Feature Interactions.’’
reason for redirection
The reason the call has been presented and is alerting at a station. Only applies to calls redirected by ECS or by ASAI from the original destination.
II-digits
Information Identifier (II) Digits provide information about the originating line for the call.
UCID (Universal Call ID)
Starting with Release 6, UCID is included in the Alerting Event Report only if it exists in the DEFINITY ECS and the “Send UCID to ASAI”4 field is administered to ‘y’. It is a unique tag assigned to each ECS call.
NOTE:
This event report is not guaranteed for each call, such as an outbound call that is not
4.The field “Send UCID to ASAI” is administered on the
