phoneDevSpecific Key:Mute

leonardo-acquisti — Mon, 18 Mar 2024 09:54:03 GMT

Hi,

I've successfully sent a device specific XSI command to a phone using JTAPI:

var str = "<CiscoIPPhoneExecute><ExecuteItem Priority=\"0\" URL=\"Key:Mute\"/></CiscoIPPhoneExecute>";

terminal.sendData(str.getBytes());

Our application must use Windows TAPI for call control, I was unable to find the correct structure that shall be sent to the tapi function

https://learn.microsoft.com/en-us/windows/win32/api/tapi/nf-tapi-phonedevspecific

I tried several buffer structure, could you explain me how the parameter block shall be filled?

Checking at the Cisco TSP logs I found the following logs:

10:21:35.275 |-->SelsiusTSP::TSPI_phoneDevSpecific(0xC7E7EC50)
10:21:35.275 |-->CSelsiusTSPDeviceList::IsValidTapiPhoneHandle()
10:21:35.275 | CSelsiusTSPDeviceList::IsValidTapiPhoneHandle() Found mapping for device(0xC7E7EC50) to deviceHandle(0x000002B0)
10:21:35.275 |<--CSelsiusTSPDeviceList::IsValidTapiPhoneHandle()
10:21:35.275 |-->CSelsiusTSPDevice::PhoneDevSpecific(): [0x000002B0]
10:21:35.275 | CSelsiusTSPDevice::PhoneDevSpecific(): [0x000002B0] *ERROR* Dev Specific Ext unavailable : Ext Ver = 0x00000000
10:21:35.275 |<--CSelsiusTSPDevice::PhoneDevSpecific(): [0x000002B0]

thaks

Leonardo

Re: phoneDevSpecific Key:Mute

dstaudt — Wed, 20 Mar 2024 18:49:12 GMT

The logs seem to suggest that the application has not negotiated an appropriate phone device API version.
See: phoneNegotiateAPIVersion
The minimum version seems to be 0x00030000 , see: CCiscoPhoneDevSpecificDataPassThrough

topic Re: phoneDevSpecific Key:Mute in Call Control

phoneDevSpecific Key:Mute

Re: phoneDevSpecific Key:Mute