Maintenance state of Communication Manager endpoints

ASAI is not informed of and does not report the maintenance state (in service/out of service) of any Communication Manager endpoints via a domain control.

Communication Manager Attendant Console monitoring by ASAI (CTI)

The Communication Manager Attendant Console cannot be monitored by ASAI (CTI), and recording functions are not possible.

QSIG Interactions

• ASAIFor ISDN trunks administered with Supplementary Service Protocol b (also referred to as QSIG-enabled), ASAI is not able to track calls with supplementary UUI information. ASAI does not support QSIG path replacement. If any of the QSIG optional parameters are enabled on the Communication Manager QSIG Optional Features form, ASAI can not keep track of the call.

  Device, Media, and Call Control (DMCC) does not support the extensions of digits in length.

• CVLANBecause the CVLAN service is implemented using ASAI, CVLAN support for this feature is also incomplete.

• TSAPIThe TSAPI service does not properly handle certain call scenarios involving QSIG trunks.

• JTAPIBecause JTAPI is an interface to TSAPI, JTAPI does not properly handle certain call scenarios involving QSIG trunks.

Bridging

• ASAIA bridged call appearance is selected for a single-step conference by Communication Manager only if there are no regular call appearances available at the added station. Other than that, bridging is not supported with either single-step conference or phantom calls.

  Note:

  For a given call appearance, ASAI can only administer configurations with up to 16 bridged appearances and other Communication Manager group features in total.

• CVLANBecause the CVLAN service is implemented using ASAI, CVLAN support for this feature is also incomplete.

• TSAPIBecause the TSAPI service is implemented using ASAI, TSAPI support for this feature is also incomplete.

• JTAPIBecause JTAPI is an interface to TSAPI, JTAPI support for this feature is also incomplete.

Answering a call from an extension that is already present in an outgoing call

• ASAIIf a user tries to answer a call from an extension that is already present in an ongoing call through a different line appearance, it will fail with the following error:

  RESOURCE_BUSY

  To resolve this issue, the user first needs to put the current call on hold and then the other call can be answered on another line appearance.

• CVLANBecause the CVLAN service is implemented using ASAI, CVLAN support for this feature is also incomplete but it works with HOLD API.

• TSAPIBecause the TSAPI service is implemented using ASAI, TSAPI support for this feature is also incomplete but it works with HOLD API.

• JTAPIBecause JTAPI is an interface to TSAPI, JTAPI support for this feature is also incomplete but it works with HOLD API.

• TWSThis cannot be achieved with TWS as TWS does not support HOLD API.

Call Park

• ASAI A call may be parked manually at a station by using the call park button (with or without the conference and transfer buttons), or by using the feature access code and the conference or transfer buttons. When a call is parked using the call park button (without either the conference or the transfer buttons) no event reports are generated. When the call is unparked, a Connected Event Report is generated with the calling and called numbers indicating the station on which the call had been parked, and the connected number is that of the station unparking the call. If the call remains active at the parking station (via conference), no changes occur to the listening disconnected paths as a result of parking. If the call drops from the parking station (via transfer), its paths are disconnected from everyone on the call. A single-step conference request will be denied if the call is parked.

• CVLAN Because the CVLAN service is implemented using ASAI, CVLAN support for this feature is also incomplete.

• TSAPI Because the TSAPI service is implemented using ASAI, TSAPI support for this feature is also incomplete.

• JTAPI Because JTAPI is an interface to TSAPI, JTAPI support for this feature is also incomplete.

Meet-me Conference feature

The Meet-me Conference feature is not supported in AE Services.

Limitation of Event Notification for Bridge parties

Event Notification for bridge parties is supported up to 20 bridges per principal station in AE Services.