OpenPeppol Test

[jianweng11]

Dear @phax and expert,

We are currently performing the eDELIVERY TEST SUITE – AS4 Message Reception test and encountered the following error
We would like to check how this issue can be resolved and whether it is related to the OpenPeppol SML?
I am using Phase4 v4.5.4. Kindly help.

Testbed Message:
Transaction (with instance identifier PSG001189-8-20260822T074348) to testing AP (sender: 9922:OPTBCNTRLP1001, receiver: 0195:SGUEN200618345W) was rejected, with reason; Direct transmission failed.

HTTP status: 200.

Error description: [OUTGOING-SBDH-117] Failed to send Peppol message via AS4: AS4_ERROR_MESSAGE_RECEIVED.

Error description value 1: [OUTGOING-SBDH-117] AS4 Error: Failed to resolve SMP address via DNS for the provided receiver - PEPPOL:NOT_SERVICED

Phase 4 Log:

[ERROR] 2026-08-22 07:43:49.961 : @9f8bbdba-752c-48bc-950c-a1be41c0fd2b - [f9f732dd-8982-476d-810e-0c04ff95d378@phase4.openpeppol.testbed] Failed to resolve SMP address via DNS for the provided receiver
[com.helger.smpclient.url.SMPDNSResolutionException: Participant DNS name 'uzkvops2j6eiboi5ng5q7ytg7j3tzhkxochtx2iacfso6ayvaspq.iso6523-actorid-upis.participant.sml.test.tech.peppol.org' is not registered [HOST_NOT_FOUND]; ErrorCode=PARTICIPANT_NOT_REGISTERED]
at com.helger.smpclient.url.AbstractBDXLURLProvider.getSMPURIOfParticipant(AbstractBDXLURLProvider.java:375)
at com.helger.smpclient.url.ISMPURLProvider.getSMPURIOfParticipant(ISMPURLProvider.java:76)
at com.helger.smpclient.peppol.SMPClientReadOnly.(SMPClientReadOnly.java:117)
at com.helger.phase4.peppol.servlet.Phase4PeppolReceiverConfiguration.getOrCreateSMPClientForRecipient(Phase4PeppolReceiverConfiguration.java:271)
at com.helger.phase4.peppol.servlet.Phase4PeppolServletMessageProcessorSPI.processAS4UserMessage(Phase4PeppolServletMessageProcessorSPI.java:1069)
at com.helger.phase4.incoming.AS4RequestHandler._invokeSPIsForIncoming(AS4RequestHandler.java:900)
at com.helger.phase4.incoming.AS4RequestHandler._handleIncomingSoapMessageAndInvokeSPIs(AS4RequestHandler.java:1796)
at com.helger.phase4.incoming.AS4RequestHandler.lambda$handleRequest$5(AS4RequestHandler.java:2170)
at com.helger.phase4.incoming.AS4IncomingHandler.parseAS4Message(AS4IncomingHandler.java:423)
at com.helger.phase4.incoming.AS4RequestHandler.handleRequest(AS4RequestHandler.java:2188)
at com.helger.phase4.servlet.AS4XServletHandler.handleRequest(AS4XServletHandler.java:235)
at com.helger.phase4.servlet.AS4XServletHandler.handleRequest(AS4XServletHandler.java:264)
at com.helger.xservlet.handler.simple.XServletHandlerToSimpleHandler.onRequest(XServletHandlerToSimpleHandler.java:239)
at com.helger.xservlet.AbstractXServlet._invokeHandler(AbstractXServlet.java:347)
at com.helger.xservlet.AbstractXServlet.service(AbstractXServlet.java:530)
at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:710)
at com.helger.xservlet.AbstractXServlet.service(AbstractXServlet.java:586)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:132)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:59)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:111)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:165)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:77)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:535)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:115)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:86)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:782)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:71)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:347)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:406)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:71)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:1307)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:2036)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:74)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:949)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:483)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:74)
at java.base/java.lang.Thread.run(Thread.java:1474)

Thanks.

[Vishnu209]

Hi @jianweng11,

From the log, Phase4 is failing during SML/SMP discovery for the receiver participant:

0195:SGUEN200618345W

The relevant error is:

PARTICIPANT_NOT_REGISTERED

I checked the SMP and this participant is currently not registered there. Therefore, Phase4 cannot resolve the receiver's SMP address and returns PEPPOL:NOT_SERVICED.

Could you please verify that 0195:SGUEN200618345W is registered in the SMP before retrying the test?

[phax]

Thanks @Vishnu209 :-)

[jianweng11]

Dear @Vishnu209 and @phax ,

Yes, we are not register in SMP because this is OpenPeppol testbed and the document mentioned that no SMP participant registration is required.

We are trying to register for SG SMP. However, the document type is not available for OpenPeppol testbed testing in SG SMP.

Was there any config to temporary passthrough the validation for C3 receiver when receiving the document in AS4?

[phax]

Well, during the start of the test case you provide a predefined participant ID. This participant ID must be registered in a test SMP you have under control. So it seems like you accidentally used 0195:SGUEN200618345W there...???

[jianweng11]

Dear @phax,

Thanks for your assistance.

Initially, the country’s Peppol Authority required us to complete the conformance test before applying for the AP application. However, we did not have our own SMP and were unable to register the Peppol ID with SMP for testbed testing.

We resolved this by registering the Peppol ID with the old SG SMP using another AP’s SMP before proceeding with the Testbed. (The new SG SMP does not have the required BIS document types for the Testbed, which was the reason we had to use the old SG SMP)

This issue has now been resolved, and we were able to proceed with and complete the conformance testing successfully.

Thanks.