as2 message to partner: 403 Forbidden # null

[Former Member]

Hello,

This is for outbound scenario. Messages are flowing from Supplier to Partner via Seeburger AS2.

We have been informed  from one of our customer/partner that they have changed the IP address at their end.

We are using the hostname in the Integration Direct, in receiver communication channel for example www.xyz.com and
its configured via a proxy for example http-proxy.supplier.com.

Before customer changing the Ip, everything was working fine. but After he informed that he has changed the IP,
the messages are failing in seeburger Monitor with the below error.

"
State Error on send, will be retried
Status Description Could not deliver as2 message to partner: 403 Forbidden # null
"

I am not sure where to change the new IP. I dont see any document on this.

Can you please guide me on this. I guess it has to be changed in firewall or proxy..but not sure how to proceed furhter.
Is anyone faced this type of issue earlier. Can anyone guide on this how to proceed further.

Thanks in Advance

Regards
Venkatesh

[Former Member · Accepted solution]

Hi Venkatesh,

IP will be added in two locations

1) /etc/host files in the PI box. ( Unix team will do this)

2) firewall team will add the new IP for the configured host file in the receiver CC

Cheers

Hidayat

[Former Member · Accepted solution]

Thanks Hidayat, You suggestion looks logically correct

Do you have nay document with screen shot for the 2nd step ie, "

2) firewall team will add the new IP for the configured host file in the receiver CC"

Thanks in Advance

Regards

Venkatesh

[Former Member · Accepted solution]

Hi Venkatesh,

its just a firewall rule . if you contact your firewall team then they will do the needful

Cheers

Hidayat

[S0003485845]

Hi,

if the code 403 is received, it means that you already have been able to reach the AS2-Adapter on your partners side, but that no SenderAgreement ( referring to the correct AS2-IDs ) could be found (which could have different reasons).

So I agree with the statements of Satish..

Greetings

[Former Member]

Hi Venkatesh.. 

This error may have different reasons:

a) You or your partner has entered an incorrect AS2 ID for one of the involved parties.

b) A valid sender agreement is missing.

c) There are more then one AS2 sender agreements with the same sender AND receiver party.

d) The corresponding inbound channel is set to inactive.

Thanks,

Satish.