/mcpBackward Compatibility This feature is not backward compatible and existing applications can be affected with the introduction of this new feature. That is, when mid-call feature(s) is involved, there can be recording retrigger(s) with multiple recording sessions within a single call, applications need to coordinate these recording sessions accordingly. This new change of behavior applies to both Gateway-based recording as well as Phone/BIB-based recording. For detailed information about these interface changes, see the following topics: • CiscoJtapiException, on page 416 • Related Documentation, on page 289 • CiscoCall, on page 332 • CiscoProvider, on page 492 • CiscoProviderCapabilities, on page 504 • CiscoProviderCapabilityChangedEv, on page 506 • CiscoProviderObserver, on page 508 • CiscoRecorderInfo, on page 511 • CiscoTerminalConnection, on page 636 • CiscoTermConnRecordingTargetInfoEv, on page 594 Redirect JTAPI 1.2 specifies that one of the preconditions of the CallControlConnection.redirect() method specifies for the state of the connection to be in either the CallControlConnection.OFFERING or the CallControlConnection.ALERTING state. Cisco Unified JTAPI also allows a connection in the CallControlConnection.ESTABLISHED state to get redirected. The redirect() method includes the following overloaded form in the CiscoConnection interface. It allows applications to specify the behavior that is desired when a failure occurs while a call is redirected and specifying the calling search space, or resetting the original called field. Applications choose the desired behavior, by passing one of the following INT parameters in the overloaded redirect method from the CiscoConnection interface: • Redirect drop on failure—When a call is directed to a busy or an invalid destination, Cisco Unified Communications Manager can either drop the call if the redirect fails or leave the call at the redirect controller. The JTAPI application can then take corrective action, such as redirecting the call to another destination. The option for the redirect mode parameter follows: • CiscoConnection.REDIRECT_DROP_ON_FAILURE • CiscoConnection.REDIRECT_NORMAL • Calling Address search space—Redirect uses the calling search space parameter to indicate which callingSearchSpace is used. Applications can either use the calling party search space or the redirect controller search space. The parameter options for this scenario follow: • CiscoConnection.CALLINGADDRESS_SEARCH_SPACE Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 147 Features Supported by Cisco Unified JTAPI Redirect