McDewey

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

Page 437

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

Constants #define MAX_DEVICE_SIZE 49 #define MAX_DESTINATION_DIRECTORY_NUMBER 49 #define MAX_XML_DATA_SIZE 10000 Phone State Event When the capability of the device changes, a PHONE_STATE event is fired with an indication of what is changed. Parameters PHONE_STATE dwParam1 - PHONE_STATE dwParam2 - PHONESTATE_CAPSCHANGE (0x00040000) dwParam3 - CiscoPhoneCapsDevSpecificStatus - PHONECAPS_DEVSPECIFIC_HUNTGROUP_LOGIN_STATUS(0x00000001) dwParam4 - updated value of HuntGroup Login Status of the device The following enumerator is added: enum CiscoPhoneCapsDevSpecificStatus { PHONECAPS_DEVSPECIFIC_HUNTGROUP_LOGIN_STATUS = 0x00000001 }; where PHONECAPS_DEVSPECIFIC_HUNTGROUP_LOGIN_STATUS will notify the application about the successful change in the HuntGroup Login status of the device. Messages This section describes the line device specific messages that the Cisco Unified TSP supports. An application receives nonstandard TAPI messages in the following LINE_DEVSPECIFIC messages: • A message to signal when to stop and start streaming RTP audio. • A message that contains the call handle of active calls when the application starts up. • A message that indicates to set the RTP parameters based on the data of the message. • A message that indicates secure media status. The message type represents an enumerated integer with the following values: enum CiscoLineDevSpecificMsgType{ SLDSMT_START_TRANSMISION = 1, SLDSMT_STOP_TRANSMISION, SLDSMT_START_RECEPTION, SLDSMT_STOP_RECEPTION, Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 405 Cisco Device-Specific Extensions Constants

Page 437 content