McDewey

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

Page 568

↗ View in doc context
page
568
source
cucm/v15/tapi-dev-guide/tapi-dev-guide.md
chunk_id
cucm::v15::tapi-dev-guide::tapi-dev-guide::582

Expected events Action OutofService for the line P1:1111 INService for the line P1:1111. Note There will not be any notification for the existing calls. Stop Primary CTI Manager GroupCallPickup Configuration Service parameter “Auto Call Pickup Enabled” is enabled. Pickup group P1:1111 is configured and opened P1:1000, P1:1001, P1:1002 are all in pickup group P1:1111 P1:2000, P1:2001, P1:2002 are all in pickup group P1:2222 P1:4000 and P1:4001 are configured Expected Action Line Open Successful LineIntialize OpenLines – 1000:P1 LineGetDevCaps with Extension Version – 000A0000 on P1:2000CallPickUp Group DN and Partition Information will be sent to application.(P1:2222) LineGetDevCaps with Extension Version – 000A0000 on P1:2000 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 LineOpen Successful LineOpen with new DeviceID LINE_APPNEWCALL LINE_CALLSTATE with State = LINECALLSTATE_UNKNOWN to Application on Line P1:1111 P1:4000 calls P1:1002 LINE_CALLINFO dwCallState : PickupCallState (0x10000000) dwCallerId : 4000 dwCalledID : 1002 dwCallorigin: Internal dwCallReason : Direct Check for all fields of Calling and Called Information LineGetCallInfo Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 536 Message Sequence Charts GroupCallPickup

Page 568 diagram