Hey team,
We noticed a change in the behavior of the Genesys AudioHook Monitor client around July 30th. The type field on the client's JSON messages started to appear duplicated at the end of the message, as in the examples below:
{"type":"close","version":"2","id":"...","seq":2,"serverseq":1,"position":"PT0S","parameters":{"reason":"error"},"type":"close"}
{"type":"open","version":"2","id":"...","seq":1,"serverseq":0,"position":"PT0S","parameters":{"organizationId":"...","conversationId":"00000000-0000-0000-0000-000000000000","participant":{"id":"00000000-0000-0000-0000-000000000000","ani":"","aniName":"","dnis":""},"media":[{"type":"audio","format":"PCMU","channels":["external","internal"],"rate":8000},{"type":"audio","format":"PCMU","channels":["external"],"rate":8000},{"type":"audio","format":"PCMU","channels":["internal"],"rate":8000}],"supportedLanguages":false,"customConfig":{},"inputVariables":{}},"type":"open"}
So far, I've only tested and verified this behavior during the connection probe phase. This doesn't match the examples in the AudioHook docs and breaks JSON parsers that don't like duplicate keys.
Was this an intentional change?
#Integrations
#AudioHook
------------------------------
Ryan Chimienti
------------------------------