McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 1191

↗ View in doc context
page
1191
source
cucm/v15/jtapi-dev-guide/jtapi-dev-guide.md
chunk_id
cucm::v15::jtapi-dev-guide::jtapi-dev-guide::1195

Call info Result Action NA Application should get String “John” OpenProvider, User “John” EMLogin to Terminal B, add observer, application calls CiscoTerminal.getEMLoginUserName() at Terminal B Note Application verifies if EM login has been done by invoking CiscoTerminal.getLoginType(). NA Application should get String “John” User “John” EMLogin to Terminal B, OpenProvider, add observer to Terminal B, Application calls CiscoTerminal.getEMLoginUserName() at Terminal B Note Application verifies if EM login has been done by invoking CiscoTerminal.getLoginType(). Terminal A is in control list of user and configured with the Extension Mobility logout profile of user Kerry. The Kerry profile is configured with logout username as Kerry. There is another profile with login username of John. Call info Result Action NA NA Application should get String John. Application should get String Kerry. User John logs into Terminal A, OpenProvider and add observer to Terminal A. Application calls CiscoTerminal.getEMLoginUserName() at Terminal A. John logs out at Terminal A. Application calls CiscoTerminal.getEMLoginUserName() at Terminal A. Note Application verifies if EM login has been done by invoking CiscoTerminal.getLoginType(). Calling Party IP Address The following are some examples of call scenarios. Basic Call Scenario • JTAPI application monitors party B • Party A is an IP phone • A calls B Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1127 Message Sequence Charts Calling Party IP Address

Page 1191 diagram