Applies to Sinch Contact Pro from version FP18 onwards
There is an issue with Sinch Contact Pro and Conversation API or Sinch SMS integration, such as:
Log reading with blv.exe
|HTTP 401 forbidden when sending message in the SMS Server log||This is most likely a configuration mistake in System Configurator > System Management > Messaging Services so check the procedure and re-create the configuration.|
|HMAC256, CryptImportKey failed. Error: 0x3C24A58 Could not validate x-sinch-webhook-signature||This log entry indicates that validation of connection has failed. Delete the connection and create it again in System Configurator > System Management > Messaging Services. You can also try to shorten webhook and access key password provided in Sinch Customer Dashboard.|
|ERR> SMSApp: Unable to initialize session object! Check parameters from datasource|
The most likely reason is that the SMS Server mode isn’t HTTP in System Configuator > System Management > Modules > SMS Server > SMS Interface > Session Object.
Change the setting to HTTP, restart the SMS Server, and try again.
|Received HTTP status code 400 when sending rich content to customer.|
Messaging protocol in Conversation API for sending rich content has changed. If you have either FP17 or FP18 version, to fix the issue, install the hotfix:
Remote service of type […] not found
In addition to this, Communication Panel shows Configuration missing.
This is a configuration error. Authentication ID and queue address (the part before @) are not matching. They should be the same. For example in case of direct Facebook integration:
|Attachments are missing|
|Rich content files are not received by the WhatsApp client from the outgoing WhatsApp message.||Check that you have GoDaddy root certificate installed on the application server running the SMS Server component. To try out that the public URL is reachable, copy the URL from the SMS Server log and paste it to the browser.|
|Conversation Attached Data (CAD) is not visible in Communication Panel.|
Check from the visitor facing ECF Web Server logs that CAD WhatsApp is added to a chat
If the chat arrived with CAD and is provided with CAD keys, the issue is in Sinch Contact Pro. Check the Chat Server logs.
Error in SMS Server log, problem started after 15/06/2023: ERROR_WINHTTP_CANNOT_CONNECT
Reason: there was an update made to Conversation API that changed the allowed ciphers. Please find a list of supported ciphers below:
Preferred TLSv1.3 128 bits TLS_AES_128_GCM_SHA256 Curve 25519 DHE 253
Accepted TLSv1.3 256 bits TLS_AES_256_GCM_SHA384 Curve 25519 DHE 253
Accepted TLSv1.3 256 bits TLS_CHACHA20_POLY1305_SHA256 Curve 25519 DHE 253
Preferred TLSv1.2 256 bits ECDHE-RSA-CHACHA20-POLY1305 Curve 25519 DHE 253
Accepted TLSv1.2 128 bits ECDHE-RSA-AES128-GCM-SHA256 Curve 25519 DHE 253
Accepted TLSv1.2 256 bits ECDHE-RSA-AES256-GCM-SHA384 Curve 25519 DHE 253