McDewey

TAPI structures TAPI messages Action LINEDEVCAPS::DevSpecific Remote Destination Info: unicodeRDName = "Mobile" RDNumber = "91486271309" isActiveRD = 0x00000001 unicodeRDName = "Office" RDNumber = "4089022131" isActiveRD = 0x00000000 IsMyAppLastToSetActiveRD = 0x00000001 LineGetDevCaps() returns success LineGetDevCaps() with dwDeviceID = LineDeviceId of Line-A. Event on Line A : Line INSERVICE EVENT Event = LINE_LINEDEVSTATE dwParam1 = LINEDEVSTATE_OUTOFSERVICE Line INSERVICE EVENT Event = LINE_LINEDEVSTATE dwParam1 = LINEDEVSTATE_INSERVICE Set RD -Mobile to ACTIVE RD and then Stop Call Manager on the node of Secondary CTI Manager ActiveRD configuration is not changed/ not RESET Same as for CTI Remote Device other than dwLineTypes and DeviceProtocolType Info. dwLineTypes = (0x00000000) DeviceProtocolType = DeviceProtocolType_SIP (0x02) Variation : Test the same on CSF device [CSF -Line-A''] CTI/CCM Manager FailOver Scenario - Active RD Set by Other Application Precondition: same as UseCase 1 TSP is configured with Primary and Secondary CTI Manager Other Application has set the ACTIVE RD on the Device and Application is connected to Secondary CTI Manager TAPI structures TAPI messages Action Lines are Enumerated LineInitializeEx Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 595 Message Sequence Charts Message Sequence Charts