Cannot process certain MDN from trading partner

You are here

Cannot process certain MDN from trading partner

4 posts / 0 new
Last post
sjtai
sjtai's picture
Cannot process certain MDN from trading partner

Hi, I was doing some tests with b25 earlier. I sent a message to a trading partner successfully (HTTP 200 responded) but had problem with the MDN from the trading partner.

I've attached the log with this post. The trading partner ID, URL and file name have been changed to hide the real identity of the trading partner.

We checked the MESSAGELOG table and the MDN record was not created.

We've tested m-e-c AS2 with another trading partner who is using SeeBeyond and the test was successful. The trading partner that we are having problem with is using Cyclone.

Does anyone have any idea what caused the "Missing header value" error?

AttachmentSize
mdn_log.txt1.64 KB
heller
heller's picture

sjtai,

sjtai wrote:

The received sync MDN seems not to be in right format. Missing header value "as2-to".

as2-from and as2-to indicate the sender as2 id and receiver as2 id of every message or signal in as2.

Please have a look at http://www.ietf.org/rfc/rfc4130.txt:

rfc4130 wrote:

The AS2-To and AS2-From header fields MUST be present in all AS2 messages and AS2 MDNs whether asynchronous or synchronous in nature, except for asynchronous MDNs, which are sent using SMTP.

Anyway compatibility to any other AS2 system is important. Could you please send me the header data of the MDN, we will add this for the next release?

Regards
Heller

sjtai
sjtai's picture

This is not a new trading partner. We have been exchanging messages with them for a few years using another AS2 implementation.

When the error was reported, no file was generated, so I can't provide the header data of the MDN at the moment. I'll add some filters to the HTTP request chain and update you when I have gathered more info.

sjtai
sjtai's picture

We found out that the problem was caused by incorrect sender ID. This is a configuration problem. m-e-c AS2 worked perfectly after the problem was fixed.