/mcp• CiscoAddrRemoveFromTerminalEv—Gets sent when the following conditions occur: • A user removes a Terminal/Device from the user controlList that contains a SharedDN. In other words, if a user has a shared address in a control list, and one of the devices with same address gets removed, this event gets sent. • An EM(extension mobility) user logs out from the terminal that had a profile that contains a SharedDN. This event notifies applications that one of the terminals is removed from an existing Address. • A new SharedDN (SharedLine) is removed from a device in a control list. Interface getTerminal() returns the terminal that gets removed from the address. Interface getAddress() returns the address from where the terminal gets removed. The following changed or new behaviors exist for a SharedLine: • Behavior changes for CiscoAddress event include • JTAPI applications will receive multiple CiscoAddrInServiceEv for shared line addresses. Applications can use CiscoAddrInServiceEv.getTerminal() to get the terminal on which address goes in service. • JTAPI applications receive multiple CiscoAddrOutOfServiceEv for shared line addresses. Applications can use CiscoAddrInServiceEv.getTerminal() to get terminal on which address goes out of service. • The address state goes in service when a first shared line goes in service; for example, when the first CiscoAddressInServiceEv gets received. • The address state goes out of service when the last shared line goes out of service; for example, when the last CiscoAddressOutOfServiceEv gets received. • For an incoming call, all the line appearances of a shared line ring. To applications, this gets presented as one active call (callActiveEv), one Connection(ConnCreatedEv), and multiple terminalConnection(TermConnCreatedEv one each for each shared line). • Calls get presented to all terminals. When a call is in a ringing state, the state of the terminal connection equals Ringing. When a the shared line answers, the terminalConnection state goes to an active state, while other terminalConnections on the shared line go to a passive state, and callControlTerminalConnection for all the shared lines at this point go into a bridged state. When a call is put on hold, all the terminal connections go into an active state, and callControllTerminalConnection goes to a held state. At this point, any terminal can retrieve the call. The retrieving terminal terminalConnection remains in an active state, and callControlTerminalConnection goes to a talking state while all other shared terminals terminalConnections go into a passive state. Simultaneously, CallControlTerminalConnection changes from a held state to a bridged state. • A shared line can make a call to another shared line of the same DN. In this scenario, the call includes only one connection and multiple terminal connections. • When a shared line makes a call to another shared line of the same DN, the post condition for this equals only one connection. • For a shared line connection with two active terminalConnections (such as barge), Connection.Disconnect() does not result in disconnected connection. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 166 Features Supported by Cisco Unified JTAPI Shared Line Support