We also able to connect now after upgrading to AES 10.2 version, now got stuck on "Monitor deviceID"
Step-0:connect websocket with basic credentials
Step-1-: Start applciationsession with basic credentials
Step-2: Get deviceID with Bearer details
Step3: monitor deviceid (Payload structure for this method unclear); tried with multiple options and taken reference from DMCC API's ; so far not helpful.
Feedback with sample payload would be really helpful.. Secondly any reference client to understand the sequence/payloads/documentation would be helpful. Thanks in advance!
WTI provides both a REST and Websocket mechanism to interact with Avaya Aura Communication Manager, via Avaya Aura Application Enablement Services. It replicates functions that are provided by DMCC and TSAPI. Using WTI, an application can perform several functions. These can be grouped into two categories - Call Control (aka
What are you using to connect and send the payload? Are you creating your own application using C# and .NET 8 for example? Or just Postman or Insomnia api calls?
I know this is a bit old.. but I was going to try to play around with the wti socket api. I've got the Wti Rest api's working with no issues.. but I cant' seem to figure out what the url is for the socket connection. I'm currently just trying to use Insomnia to post as socket request. Firstly, how do I verify that our AES even has the wti socket running? I see the "Web Telephony Interface(WTI) Service" running and I can create a session etc. When I try to establish a session using sockets.. I get nothing. No error and even an indication its tried to connect. I've tried both "ws://ourtestaes/api/wti/session" and this "wss://ourtestaes/api/wti/session"... and I get nothing back. Are there any headers I need to set? Thanks for any help!!
Comment