It's great to hear from you, George. It's working, but in a different manner. The json payload just would not be registered as call.UUIdata in ascii format. The sender switched to hex and all is well. Once it's received, there's no difference.
Sr. Genesys Cloud Developer II
Tandem Diabetes Care, Inc.
Original Message:
Sent: 05-08-2025 10:40
From: George Ganahl
Subject: UUI over SIP trunk - valid UUI formatting for JSON content
There is an old thread talking about setup for passing UUI between and edge and an AudioCodes Mediant, using the proprietary AudioCodes UUI Field:
AudioCodesUUI Thread
From that thread,
Further feedback has been provided to us, and it's become apparent that the INBOUND INVITE, from the SBC, should include 'encoding=ascii' within the 'X-User-To-User' header.
The header should look something like 'X-User-To-User:1894317F;encoding=ascii'
Perhaps the SBC needs the same...
------------------------------
George Ganahl GCCX-AI, GCP, GCSME, ICCE, ICHD, etc.
Technical Adoption Champion
Genesys
Original Message:
Sent: 05-07-2025 17:25
From: Vikki Papesh
Subject: UUI over SIP trunk - valid UUI formatting for JSON content
Thank you, Jason.
I can't edit the original post now, but I've been beating my head on this for a while now.
Between flows in the same org, I can use the Architect step "Set UUI (for transfers)" and populate with json key:value pairs ex {"key1":"value1","key2":"value2"}, receive as uui data in Call.UUIdata, take the string and jsonparse into a json variable, then GetJsonObjectProperty to pull the matching values.
I need to replicate this over a BYOC trunk from an external system that is fronted with a SBC. However, when this entity SIP REFERs User-to-User string back to me, Genesys Cloud is not seeing it as proper UUI data even though it is in the SIP REFER header as User-to-User. In collaboration with the party on the other end of the line, we've tried a few dozen formats, from standard json, to escaped json, to quoted body, and yet I have not successfully received a single uui header that will populate Call.UUIdata. This is a time-critical issue; based on my internal testing the intake of data worked fine, but coming across this trunk is another story.
------------------------------
Vikki Papesh
Sr. Genesys Cloud Developer II
Tandem Diabetes Care, Inc.
Original Message:
Sent: 05-07-2025 16:39
From: Jason Kleitz
Subject: UUI over SIP trunk - valid UUI formatting for JSON content
Hey Vikki,
This would probably be a good question for the Genesys Cloud - Developer Community. I have moved your thread there so that the experts there can help you.
------------------------------
Jason Kleitz
Online Community Manager/Moderator
Original Message:
Sent: 05-07-2025 10:03
From: Vikki Papesh
Subject: UUI over SIP trunk - valid UUI formatting for JSON content
Greetings. When sending JSON in ascii format as UUI data between two flows on the same org, I can use standard JSON formatting and use Architect to cast the UUI string to JSON and then parse the key/value pairs. When I attempt to do the same thing via SIP trunk traversing an Audiocodes gateway, the JSON is not recognized as UUI data, even though it appears as proper unescaped JSON in the header's User-to-User field.
Call.UUIdata will populate if I encapsulate the whole string in quotes. But then it doesn't validate as json, so I am back to not working.
Is there another better or simpler way to send the JSON body so that it can be recognized by Architect?
#API/Integrations
#SIP/VoIP
------------------------------
Vikki Papesh
Sr. Genesys Cloud Developer II
Tandem Diabetes Care, Inc.
------------------------------