Unable to parse the inbound OFTP2 command ESID

Hello, I'm trying to configure OFTP2 connection with 2 of our clients. Unfortunatly in both cases I have this same error at the end of transmission (in attached file). Maybe someone has this same issues with it and can provide me some solution in this matter.
When I'm testing connection to our partners (Routing - test connection) everything seems to be ok, but when I'm trying to send test data this error appears, it dosesn't working in both directions. All clients and our ceriticates are installed.
Mendelson software - bulid 37
Please Help

Forum
OFTP2

Comments

Profile picture for user service
Permalink

JarekPEL,

the ESID command you received is not an OFTP2 command, it's an OFTP1 ESID. There exists a OFTP2 system that falls back into OFTP1 in error case and performs a protocol violation doing so, your partner seems to use it. To get more information about what your partners system tries to tell you please refer to the OFTP1 RFC and have a look at the ESID command.

But in my option the error message displayed by the mendelson OFTP2 and also included in your attached log file descibes the problem very detailled?

"This is not a problem of your mendelson OFTP2 system. It is a protocol violation performed by your partners OFTP2 system. It looks as if your partner is using a OFTP 1.x system or falls back to the OFTP1 protocol in an error case. If this problem happens during the connection attempt please check if you have transmitted the right connection password. Please also check your secure authentication challenge settings. Please also contact your partner to clarify this issue. (Hexdump: 10 00 00 07 46 30 33)"

Regards

Profile picture for user service
Permalink

JarekPEL,

please find attached the structures of the ESID commands in OFTP1 and OFTP2. The hex data your partner sent is "10 00 00 07 46 30 33".

As the first 4 bytes are just the stream transmission header the interesting part are the last 3 bytes, this is HEX "46 30 33", in ASCII: "F03". If you match this to the OFTP1 command as attached:

ESIDCMD = "F"
ESIDREAS = "03"

The reason code "03" means:

'03' User code not known

A Start Session (SSID) command contains an unknown or
invalid Identification Code.

Regards

File attachments
Permalink

I was able to make all config to work with one of my customers. The problem was in Password in routing section. When I set it on my own pass all started to work as expected.
Now I'm facing another problem, some of my clients are using older version of OFTP protocol, my system shows me in log details "SSID negotiation failed: OFTP version<2 not supported"
Is it possible to set up connection with them using some additional options at the start of this system??
Does the paid version has this option??

Permalink

SFID and SSID fields in configuration panel. One of my client wish to receive transmission with one SSID number and few SFID numbers each for different plant. At the moment when I'm trying to configure the new remote partner I can write the SSID and SFID number, unfortunaltly SFID number becomes SSID number when you press ok in that window. Is it possible to do such configuration in mendelson software? My client would like to receive SFIDDEST (SFID Start File [Outbound]) with his real SFID number insted of this he receive it own SSID number. I looks like SFID is always more important at the moment of configurartion and if it is present the SFID it is taken as a SSID number. Could you please do something with that. Is there some walkaround of this problem at this moment??

Profile picture for user service
Permalink

JarekPEL,

this is a normal routing setup, this is fully covered. Just setup the final receiver that could not be reached directly (->SFID) and connect via a gateway partner (->SSID) and you are done. The download package contains a file "readme.txt". This contains also a section about routing. Please read this, hopefully it helps.

Regards

File attachments