Retrieve UUI on Refer Scenario

Hello everyone,we're doin a sip refer back from an external sip trunk "Generic BYOC Carrier" but the UUI data is been lost.
Our CallFlow and configurations:
So we bought an spanish DID number from Genesys

The calls from this DID get Routed as inbound on the Trunk “PureCloud Voice – AWS”.
We have this DID pointin the call to the inbound Script “teste”
Our teste script just do a transfer to the external number 44445

We have an site with an Route to send an invite to our “External SIP TRUNK” for 44445.

The External trunk sends a call to an external IVR that plays a prompt and refers the call back to the DID “+1195111”.
image
Refer-To: sip:+1195111@XXXX.byoc.mypurecloud.XX?User-To-User=00456d70747944617461%3Bencoding%3Dhex

“+1195111”. is an internal number that sends the call to the inbound script “test” which just set an Variable with the UUI Variable value,but on interactions im not able to see the UUI value we also tried a loto f diferente stuff like sending to a queue but on the Agent Script and the Queue script we also can’t find the UUI been set.

This Whole configuration was done based on the documentation on https://developer.genesys.cloud/blog/2021-09-03-transferring-calls-to-external-using-byoc/#data-as-user-to-user-information done by @Jerome.Saint-Marc
Can anyone help us understand if this is a limitation on calls been generated by the trunk “PureCloud Voice – AWS”, an missconfiguration on our genesys side or something we doin wrong on the external trunk refer.

PS:i couldn't upload the prints i had with the configurations but i can assure we have UUI passing enable on external trunk group ,if anyone wants extra information please ask me and and i will send the prints

Hello,

Are you sure of the setting on your IVR for User-To-User and encoding=hex?

The fact that it appears as Refer-To: <sip:+1195111@XXXX.byoc.mypurecloud.XX?User-To-User=00456d70747944617461%3Bencoding%3Dhex> in your screenshot

And not: Refer-To: <sip:+1195111@XXXX.byoc.mypurecloud.XX?User-To-User%3B00456d70747944617461%3Bencoding%3Dhex>
Or: Refer-To: <sip:+1195111@XXXX.byoc.mypurecloud.XX?User-To-User=00456d70747944617461;encoding=hex>

makes me think there could be an issue at this level (Genesys Cloud reading it maybe as 00456d70747944617461%3Bencoding%3Dhex - instead of understanding the split)

I don't have ways to test and force such value in my REFER message.

Regards,

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.