/mcpCiscoAddrAddedToTerminalEv CiscoAddrRemovedFromTerminalEv. JTAPI exposes getLoginType () on CiscoTerminal to indicate if the terminal is part of the Home or Visiting cluster when a user does an Extension Mobility login or logout. Accordingly, return value will be CiscoTerminal.NO_LOGIN, CiscoTerminal.NATIVE_LOGIN or CiscoTerminal.VISITOR_LOGIN. Home Cluster is the Cisco Unified Communications Manager cluster from which the traveling EMCC user starts. This is the user's home cluster where the user profile resides. Visiting Cluster is the Cisco Unified Communications Manager cluster which the traveling EMCC user visits. This is also the cluster that owns the phone at which the user does Extension Mobility login. Interface Changes CiscoProvEv, on page 481, CiscoTerminal, on page 617 Message Sequences Extension Mobility Cross Cluster, on page 978 Backward Compatibility This feature is backward compatible. Extension Mobility Username Login The Extension Mobility Login Username enables applications to get the Extension Mobility login username from the API provided on CiscoTerminal. Interface Changes CiscoTerminal, on page 617 Message Sequences Extension Mobility Login Username, on page 1126 External Call Control External Call Control enables Cisco Unified Call Manager (Cisco Unified Communications Manager) to route calls based on enterprise policies and presence-based routing rules of individual users. When call intercept is enabled, Cisco Unified Communications Manager queries the designated web services hosting the enterprise policies or user rules and routes the calls following the routing decisions returned. Starting from Release 8.0(1), JTAPI supports wildcard routepoins, as well as translation patterns. Interface Changes CiscoCall, on page 332, CiscoConnection, on page 386, CiscoAddress, on page 289 Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 93 Features Supported by Cisco Unified JTAPI Extension Mobility Username Login