Hi DevTeam

I've installed the latest and can confirm DTMF is working. There is still an issue with the app crashing if you send it a bad callId though. The crash happens with the same 'The thread tried to read from or write to a virtual address for which it does not have the appropriate access'. Bad being null or a callid that is no longer in session.

Not the end of the world but it replying on the pipe with the error message would be preferable.


Thanks

That's great! Thanks Dev Team

Sorry, i think the exception log doesn't populate until you reopen the program. Here is the entry that was generated for that crash.

2020-10-01 09:55:29.546 E An unhandled Exception has occurred
Exception: Avaya.UCC.Utils.NativeException: The thread tried to read from or write to a virtual address for which it does not have the appropriate access


Regards

Hi DevTeam

Thanks for your reply.

Yep, its the External App API for call control. I've PM'd you the crash log from Workplace. My app doesn't receive a response from Workplace before it crashes. The logs show it getting the request and then breaking some time after validating the call id.

Regards

I found you have to use a dedicated pipe to register and listen for events. The streamreader runs on a separate thread waiting for the stream to update.

The second pipe writes your actions and parses the single return message. I've lost track of the different iterations I've made of the submit and parse process.

The attached should work if you update the un and phone fields. Let me know if your dtmf submission crashes workplace.

Hi

I'm running Win10 Pro, using .net to interface with the Avaya IX Workplace 3.11 named pipe api. We have Avaya IPO R11.0.4.3.



Regards

Hi,

I've been integrating the named pipe api into our application and i've hit a wall when it comes to DTMF calls. I'm able to use register, unregister, createcall, getcalls and hangup without issue. DTMFRequest causes Workspace to crash.

I send a request: {"vnd.avaya.clientresources.call.DTMFRequest.v1.1": {"dtmfstring":"0", "callId" : "1", "transactionId" : "1234" }}\0

The exception log gets the following:
2020-09-24 18:19:23.670 E An unhandled Exception has occurred
Exception: Avaya.UCC.Utils.NativeException: The thread tried to read from or write to a virtual address for which it does not have the appropriate access

I've tried it on v3.9 and the new 3.11. The call is active and I can manually send dtmf tones by using the interface.

Is there something I'm missing?