/mcpInfo Events Action 8881000:: Event: CiscoAddrOutOfServiceEv irvCTIRD2:: Event: CiscoTermOutOfServiceEv P1: ProvOutOfServiceEv Stop CTI Manager where P1 is connected to. And this active RD will be clear out automatically from CTI/CCM side. Note that no CiscoProvTerminalRemote DestinationChangedEv will be sent to application because it is the same active RD that application previously set. P1: ProvInServiceEv irvCTIRD2:: Event: CiscoTermInServiceEv 8881000:: Event: CiscoAddrInServiceEv Start this CTI Manager. And JTAPI will automatically reset the same RD1 as active again seamlessly. CTI Remote Device Use Cases Group 5 Use Cases Group 5 (CTIRD Transfer/Conference/Multiple-Calls Call Scenarios) Pre-conditions on Use Cases group 5 below with default jtapi.ini settings, unless specified explicitly (Note: The CTI Ports have Auto-Accept enabled): • Provider is IN_SERVICE state. • Device A (CTI Remote Device - Name: "irvCTIRD2", Line A (DN: 8889000)) • Remote Destination 1 (Name: "IRVCell1", Number: "916267829523", Active RD: true) • Device B (CTI Port - Name: "irvCTIPort4", Line B (DN: 8884000)) • Device C (CTI Port - Name: "irvCTIPort5", Line B (DN: 8884000)) • Device D (CTI Port - Name: "irvCTIPort6", Line D (DN: 8886000)) • Device E (CTI Remote Device - Name: "irvCTIRD3", Line E (DN: 8889001)) • Remote Destination 1 (Name: "IRVHome1", Number: "916268210080", Active RD: true) Scenario 5-1 (Direct Transfer on CTI Remote Device to CTI Port) D calls A with GC1 as GCID of call; A calls B with GC2 as GCID of call. Set A as transfer controller, and then transfer call from GC2 to GC1. Application is observing all A, B, D. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 860 Message Sequence Charts CTI Remote Device Use Cases Group 5