Getting Started
Missed IBM TechXchange Dev Day: Virtual Agents? On-demand viewing is available here
This article explains the most commonly faced issues of document submission through different inbound channels. The possible solutions are also given to overcome the failures.
This document is meant for users troubleshooting transaction failures due to errors faced on document submission.
The following tables explains the error message, inbound channel and Issue and its solution based on Response Code
Legend as below:
Code: Response Code received on submission
2.The status of the XML Document is set to Inactive
3.Document attribute extraction for the system attributes , SenderID and RecieverID is mandatory. These are not set in the Document Attributes.
2.Set the status of the XML document to Active in Document page.
3.The extraction for the system attributes, SenderID and ReceiverID, has to be set in the document attribute page.
This is because some of the third party products unable to parse “X-Content-Type-Options” header which webmio adds before sending the sync MDN response
Below two solution will work
Ensure partner is using the correct NAT address . https://www.softwareag.cloud/site/nat-servers.html#/
Ensure partner should have whitelisted the B2BCloud’s ip address in their platform
Partner must trust the B2BCloud’s public certificates.
The supported SSL version in B2BCloud is TLS 1.2
The cipher suites supported by channel endpoints are as follows:
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 128 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 128 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 256 TLS_RSA_WITH_AES_128_GCM_SHA256 128 TLS_RSA_WITH_AES_128_CBC_SHA256 128 TLS_RSA_WITH_AES_256_GCM_SHA384 256 TLS_RSA_WITH_AES_256_CBC_SHA256 256
Ask the partner to check their proxy, firewall and DNS server.