Lucent Technologies Definity Enterprise Communications Server 555-230-220 User Manual
ASAI and Domain Control
Issue 7 May 1998
5-27
return_ack
This parameter enables the ECS to acknowledge the request
made by the adjunct. It can be set to “yes” for
acknowledgement or “no” for no acknowledgement. The
default is “no.”
made by the adjunct. It can be set to “yes” for
acknowledgement or “no” for no acknowledgement. The
default is “no.”
priority_
calling
calling
[optional] If present, a priority call is placed if the destination
is a local extension. If the priority flag is specified for an
off-ECS destination, the call is denied. The default is
non-priority.
is a local extension. If the priority flag is specified for an
off-ECS destination, the call is denied. The default is
non-priority.
uui_info
[optional] If an ASAI adjunct provides UUI in a Third Party
Auto Dial, then the ECS stores that UUI with the call.
Auto Dial, then the ECS stores that UUI with the call.
UUI from an Auto Dial Call will be sent in any ISDN SETUP
message for the call, in the Alerting and Call Offered Event
Reports, and in a Route Request, if one is made.
message for the call, in the Alerting and Call Offered Event
Reports, and in a Route Request, if one is made.
The UUI IE sent over an ISDN trunk can contain more data
than the UUI IE sent to ASAI. This happens when the ISDN
trunk group is administered with supplementary service
protocol other than B and the UUI IE Treatment is set to
“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.
than the UUI IE sent to ASAI. This happens when the ISDN
trunk group is administered with supplementary service
protocol other than B and the UUI IE Treatment is set to
“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.
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
“service-provider”. This sends the UUI as specified by
the ASAI application, without change.
contents of the UUI IE, then the trunk group used to
place those calls should have its UUI IE Treatment set to
“service-provider”. This sends the UUI as specified by
the ASAI application, without change.
For more information, see the Section, ‘‘Integrated Services
Digital Network (ISDN),’’ in Chapter 12, ‘‘ASAI and Feature
Interactions.’’
Digital Network (ISDN),’’ in Chapter 12, ‘‘ASAI and Feature
Interactions.’’