/mcpdisconnect the IVR or CTI port that streams the media. When the second call is disconnected, an event is sent to observers on the agent and receives an event to end the media. This feature is available only on phones that have BIBs. The majority of Cisco Unified IP Phones have BIBs, but the feature may not be available in various older or lower-end phone models. Administrators must enable the BIB for the device and configure it using the Cisco Unified Communications Manager Admin panel. Whenever a request to addMediaStream is made, JTAPI blocks the request until the IVR device answers the call or CTI responds with a timeout error. Due to this, the JTAPI thread that invoked the addMediaStreamRequest cannot answer its own call, because it is blocked waiting for the request to finish. Applications intending to use this feature must ensure that one of the following is applicable: • The IVR DN is configured to auto-answer incoming calls • A separate JTAPI thread or application is set up to answer on the IVR DN Interface changes See CiscoTerminalConnection, on page 636, CiscoFeatureReason, on page 408, CiscoJtapiException, on page 416, CiscoMediaStreamStartedEv, on page 431, CiscoMediaStreamEndedEv, on page 432 Message Sequences See Agent Greeting, on page 762 Backward Compatibility This feature is backward compatible. • This is a new feature and has no impact on existing features. • There are two new events for this feature, but they are only generated if the application observes the addresses in which the feature is invoked. • The odd call model for the IVR call, with only one connection, can have implications for applications that look at the number of connections for any of their logic. • Feature interaction is not supported on IVR calls. For example, invoking features such as redirect and creating a conference from the IVR call are not supported. • The IVR call is intended to stream media. Applications invoke features on the IVR call at their own risk and there are no event flows or call diagrams for any feature interaction on the IVR calls. AES 256 Algorithm IDs From release 10.5(2) Cisco Unified Communications Manager now supports the following encryption algorithm IDs: • CiscoMediaEncryptionAlgorithmType • CiscoMediaEncryptionAlgorithmType.AES_128_COUNTER_80 • CiscoMediaEncryptionAlgorithmType.F8_128_COUNTER_32 Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 34 Features Supported by Cisco Unified JTAPI AES 256 Algorithm IDs