McDewey

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

Page 113

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

• Abandoned -indicates a previously parked call is disconnected while waiting to be retrieved. • Reminder -indicates the park monitoring reversion timer for the parked call has expired. • Forwarded -indicates the parked call has been forwarded to the configured Park Monitoring Forward No Retrieve destination, or if the FNR destination is not configured, the call is forwarded back to the parker. When Cisco TSP receives the LINE_PARK_STATUS event, it maps the existing CALLINFO structure with the fields received from LINE_PARK_STATUS event. The application then retrieves the updated structure by invoking lineGetCallInfo. The mapping of the fields in the LINE_PARK_STATUS event to the LINECALLINFO structure is as follows: Description LINECALLINFO-- LINE_PARK_STATUS Identifies the line handle to which this message applies hline LineHandle Identifies the global call handle to which this message applies. dwcallid GCID A unique ID that identifies a particular parked call dwRedirectingName TransactionID Identifies the call reason. dwReason CallReason Parked, retrieved, abandoned, reminder, forwarded -indicates the status of the parked call. dwBearerMode Park Status The park slot DN. dwCallerID ParkSlotDN The partition of the park slot DN. dwCallerIDName ParkSlotPartition The parked party DN. dwCalledID ParkedPartyDN The partition of the parked party DN. dwCalledIDName ParkedPartyPartition To maintain the existing behavior of the Park feature for the Cisco Unified IP Phones running SIP, you can set the value of the Park Monitoring Forward No Retrieve Destination timer equal to the existing Call Park Duration timer and leave the Park Monitoring Forward No Retrieve Destination blank. To override the Park Monitoring feature for the Cisco Unified IP Phones running SIP, turn off the DEVSPECIFIC_PARK_STATUS message flag by using the lineDevSpecific SLDST_SET_STATUS_MESSAGES request. Interface Changes See Set Status Messages, on page 355. Message Sequences See Park Monitoring, on page 896. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 81 Features Supported by TSP Park Monitoring