I don't think there is anything you can do about this. CORS is Cross-Origin Resource Sharing and is really a policy or security mechanism that shares information between the provider and the receiver during SMS transmission. Only Genesys (or their upstream provider) can fix this. You need to submit a ticket with this information, the conversationID, and the to and from numbers. Remember that the Genesys SMS API is essentially sending this to their back-end broker and asking them to send the SMS to the end provider. Report this and let us know what the result was.
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.comhttps://www.ttecDigital.comhttps://RobertWC.Blogspot.com------------------------------
Original Message:
Sent: 09-27-2023 13:58
From: Jason Tran
Subject: SMS Error on Delivery on behalf of a Queue
Been having issue with are test org where the SMS won't sent using any of are numbers assigned to the call routing. Doesn't work without one either. I'm seeing CORS failure in the network logs but not seeing any indication why this is happening. It worked in the past before when we are sending SMS on behalf of a queue
#Omni-ChannelDesktop/UserInterface
------------------------------
NA
------------------------------