NCR NCT-type operations are activated by ASAI call processing when the Call Transfer or Third-Party Merge/Release operation is performed by a CTI application. This occurs in the following manner:
This is typically initiated by the CTI application user selecting an icon, menu item, or button to transfer an answered incoming ISDN call to another party over the PSTN.
Since the incoming ISDN call must be connected to a station user before the Call Transfer or Third-Party Merge/Release operation is requested, NCR can only initiate the call redirection if an NCT-type protocol is optioned on the trunk.
If a call arrives at an ASAI-monitored VDN, ASAI will send appropriate information in the ASAI disconnect event to notify the CTI application that the call has been redirected by NCR.
For the ASAI operations listed above to succeed, the following conditions must be in effect:
The Network Call Redirection field is set on the System Parameters Customer Options screen.
An NCR NCT-type protocol is administered for both the incoming and outgoing call ISDN trunk group.
The PSTN number that the CTI application uses to redirect an incoming ISDN call to another PSTN endpoint must be added to the ARS digit analysis screen in such a way that for the NCR MCI NCT and TBCT protocols, the second leg of the call transfer uses the same trunk group with a trunk that has the same D-channel as the incoming call. For the NCR ETSI ECT protocol, the CTI-initiated second call leg can be over a different trunk group with a different signaling group than the incoming call leg.
Note:
NCR-related AAR/ARS routing table administration is required for station transfer or conferencing with MCI trunks.
