Filter
Top Products
ASAI and Feature Interactions
12-50 Issue 7 May 1998
A Third Party Auto Dial or Third Party Make Call originates at the primary
extension number of a user. For a call to originate at the PCOL call appearance of
a primary extension, that user must be off-hook on the PCOL call appearance at
the time the request is received.
If a party_id query is requested while the PCOL is alerting or on hold, one party
member is reported for the group with the extension number specified as the
default extension.
If a call query is requested on an extension while the PCOL call is active, only one
call appearance is associated with the particular call_id.
Third Party Call Control should not be used in conjunction with the PCOL feature.
A PCOL group extension may not be specified as the party to be added in a
Single-Step Conference request.
Priority Calling
Calls originated via the Third Party Auto Dial or the Third Party Make Call
capability can be priority calls, if the adjunct specifies the
priority-call
option in the
Third Party Auto Dial request. The user can also originate a priority call by going
off-hook, dialing the feature access code for priority calling, and requesting a Third
Party Auto Dial or a Third Party Make Call capability.
Privacy-Manual Exclusion
This feature prevents any other user from bridging onto the call. Activation of
exclusion by any user (primary or bridged appearance, TEG or PCOL member)
prior to placing a call, causes the ECS to deny any other user from invoking a
Single-Step Conference, Third Party Auto Dial, or Third Party Make Call.
Ringback Queuing
Adjunct-routed or switch-classified calls are allowed to queue on busy trunks or
stations.
When activated, the call back call reports events on the same call_id as the
original call.
Send All Calls (SAC)
The adjunct can activate this feature by issuing a Request Feature capability. An
adjunct can request a Third Party Make Call or Third Party Auto Dial capability for
a station that has SAC activated.