/mcp• IP Address of A is available to JTAPI application monitoring party B Consultation Transfer Scenario • JTAPI application monitors party C • Party B is an IP phone • A talking B • B initiates a consultation transfer call to C • IP Address of B is available to JTAPI application monitoring party C. Consultation Conference Scenario • JTAPI application monitors party C • Party B is an IP phone • A talking B • B initiates a consultation conference call to C • IP Address of B is available to JTAPI application monitoring party C. Redirect Scenario • JTAPI application monitors party B and party C • Party A is an IP phone • A calls B • IP Address of A is available to JTAPI application monitoring party B • Party A redirects B to party C ( • Calling IP address is not available to JTAPI application monitoring party B (not a supported scenario). • Calling IP address of B is provided to JTAPI application monitoring party C. CiscoJtapiProperties 1. Set Socket Connect Timeout to 5 seconds; Plug out the Ethernet cable for PRIMARY CTI Manager and do a normal provider open. Expected Result: Socket Connect to Primary CTI Manager should fail in not more than 5 secs 2. Set Socket Connect Timeout to 5 seconds; Plug out the Ethernet cable for PRIMARY CTI Manager, set security options to True and do a secured provider open. Expected Result: Socket Connect to Primary CTI Manager should fail in not more than 5 secs (Socket Connect timed-out in ~5 seconds, though it took some additional time initially for verifying security certificates) 3. Set Socket Connect Timeout to 0 seconds; Plug out the Ethernet cable for PRIMARY CTI Manager, set security options to true and do a secured provider open. Expected Result: Socket Connect to Primary CTI Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1128 Message Sequence Charts CiscoJtapiProperties
