/mcpwhich is observable and controllable in a third-party manner. Instead, a CiscoRouteTerminal is a logical telephony endpoint that may be associated with any application that wants to route calls and terminate media. Unlike a CiscoMediaTerminal, a CiscoRouteTerminal can have multiple active calls at the same time. Typically, applications use CiscoRouteTerminals to queue calls until an agent is available to service them. CiscoRouteTerminals are CTI Route Points on Cisco Unified Communications Manager. Note Terminating media is a three-step process as follows: 1. The application registers its media capabilities with this Terminal by using the CiscoRouteTerminal.register method. 2. The application adds an observer that implements the CiscoTerminalObserver interface by using the Terminal.addObserver method. 3. The application must call addCallObserver on the CiscoRouteTerminal or the CiscoRouteAddress to receive and answer calls. Applications will receive a CiscoMediaOpenLogicalChannelEv for each call or whenever media is stopped and needs to be reestablished. Applications must supply an IP address and port number by using the setRTPParams method on CiscoRouteTerminal. Important—All applications written for or prior to CiscoJtapiClient Release 1.4 must be modified to register with CiscoRouteTerminal.NO_MEDIA_TERMINATION type if the applications are not interested in media termination. Note Multiple applications can register with same RoutePoint as long as they are registered with the same media capabilities and registration type. All applications, if registered with CiscoRouteTerminal.DYNAMIC_MEDIA_REGISTRATION, will receive CiscoMediaOpenLogicalChannelEv when they add a callObserver, but only one application will be able to invoke setRTPParams. Applications that are interested in media termination must add a CallObserver on the RouteAddress or on the CiscoRouteTerminals. Applications must not register with Dynamic type and add a registerRouteCallBack. Applications should only use registerRouteCallBack if they are not interested in media termination. Applications must not add a registerRouteCallBack and a callObserver at the same time. Interface History Description Cisco Unified Communications Manager Release Number Added these modes to the activeAddressingMode: • CiscoTerminal.IP_ADDRESSING_MODE_IPv6 • CiscoTerminal.IP_ADDRESSING_MODE_IPv4_v6 7.1(1 and 2) Superinterfaces CiscoObjectContainer, CiscoTerminal, javax.telephony.Terminal Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 543 Cisco Unified JTAPI Extensions Superinterfaces