McDewey

Expected events Action Events on P1:1000: Call 3: LINE_NEWCALL and LINE_CALLSTATE with state = LINECALLSTATE_CONNECTED Call Info : Caller = 4000, Called = 1002, Connected = 4000, dwReason = Direct, dwOrigin = Internal Note There is no notification at P1:1111 after the call has been pickup. Application sends CciscoLineDevSpecificPickUpCallFromPickupGroup with CallPickup option on P1:1000 CallPickupGroup Changed for a Device on AdminPage Pickup group P1:9999 is configured Expected events Action Line Open Successful LineIntialize OpenLines – 1000:P1 CallPickUp Group DN and Partition Information will be sent to application LineGetDevCaps with Extension Version – 000A0000 on 1000:P1 Line_Reply with success. LINE_CREATE event will sent to Application for P1:1111 Application sends CciscoLineDevSpecificRegisterCallPickupGroupForNotification with DN and Partition info of PickUpGroup P1:1111 Changed CallPickUp Group DN and Partition Information will be sent to application Now from Admin page change the CallPickupGroup of 1000:P1 line to None or some other group P1:9999 LineGetDevCaps with Extension Version – 000A0000 on 1000:P1 CallPickUpGroup Partition or DN Information Updated Expected events Action Line Open Successful LineIntialize OpenLines – 1000:P1 CallPickUp Group DN and Partition Information will be sent to application LineGetDevCaps with Extension Version – 000A0000 on 1000:P1 Line_Reply with success. LINE_CREATE event will sent to Application for P1:1111 Application sends CciscoLineDevSpecificRegisterCallPickupGroupForNotification with DN and Partition info of PickUpGroup P1:1111 Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 509 Message Sequence Charts CallPickupGroup Changed for a Device on AdminPage