XDR MT Test 13

[Vijetha Nayak]

XDR MT test returns Success when failure is expected in the ETT tool 

below is the response and the recipient should be badad...@gfail.com but I see our from address in <direct:recipient>

[2024-03-28T05:15:40.940-0700] [Payara 4.1] [INFO] [] [com.mirth.mail.mdn.NotificationUtil] [tid: _ThreadID=854 _ThreadName=pool-25-thread-6] [timeMillis: 1711628140940] [levelValue: 800] [[
  handleEdgeDSNInfoSend: Sending message disposition: <direct:messageDisposition xmlns:direct="urn:direct:addressing"> <direct:recipient>mailto:xdr...@qagtab.mirthmail.com</direct:recipient> <direct:disposition>failure</direct:disposition> </direct:messageDisposition>]]

Logs from our end :

       at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:374)
        at com.sun.ejb.containers.BaseContainer.__intercept(BaseContainer.java:4734)
        at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4722)
        at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:212)
        ... 10 more
Caused by: ERROR=NoTrustedRecipients

        at org.nhindirect.stagent.DefaultNHINDAgent.processMessage(DefaultNHINDAgent.java:1312)
        at org.nhindirect.stagent.DefaultNHINDAgent.processOutgoing(DefaultNHINDAgent.java:1250)
        ... 56 more
]]

Could you please help us understand more on this testcase or are we missing out anything 

Below is the response in the tool :

<ns3:RegistryResponse status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success" xmlns="urn:ihe:iti:xds-b:2007" xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"/>

[Kim Poletti]

Hi - Thanks for reaching out. This has been logged for review and a member of the team will reach out in the near future.

[Vijetha Nayak]

Any update on this ? i see Success in the response for XDR MT Test 13

 <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" xmlns:env="http://www.w3.org/2003/05/soap-envelope"><S:Header><wsa:Action xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://www.w3.org/2005/08/addressing" s:mustUnderstand="1">urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-bResponse</wsa:Action><wsa:RelatesTo xmlns:wsa="http://www.w3.org/2005/08/addressing">9c124fa8-65c0-4eb4-bbc9-551473331f82</wsa:RelatesTo></S:Header><S:Body><rs:RegistryResponse xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success"/></S:Body></S:Envelope>]]

And also see this in our logs 

<direct:messageDisposition xmlns:direct="urn:direct:addressing">
<direct:recipient>mailto:xdr...@qagtab.mirthmail.com</direct:recipient>
<direct:disposition>failure</direct:disposition>
</direct:messageDisposition>

Is the value here <direct:recipient>mailto:xdr...@qagtab.mirthmail.com</direct:recipient>  expected to be badad...@gfail.com

[Kim Poletti]

Hello,

Could you please send us the steps you are performing so we can reproduce on our end?

Thank you,

Kim

[Vijetha Nayak]

XDR MT Test 13: To address: [Staff]
Grab the end point wsdl :
https://qagtab.mirthmail.com:8333/XDR/XDSbRepositoryWSService
Direct from address and Outgoing Direct: xdr...@qagtab.mirthmail.com[Organization]
Click on Run
Wait for sometime
Click on Pending refresh

Status changes to Waiting validation and here the response is "Success"

[2024-04-04T04:38:30.870-0700] [Payara 4.1] [FINE] [] [com.mirth.mail.ejb.MessageBean] [tid: _ThreadID=806 _ThreadName=pool-34-thread-7] [timeMillis: 1712230710870] [levelValue: 500] [CLASSNAME: com.mirth.kana.lib.logging.Logger] [METHODNAME: log] [[
  Raw Message: Received: from localhost (localhost [127.0.0.1])
        by appliance-6f8fcaae8b06f4c7 (Postfix) with ESMTPSA id CBCA6168685
        for <badad...@gfail.com>; Thu,  4 Apr 2024 04:38:30 -0700 (PDT)
Date: Thu, 4 Apr 2024 04:38:30 -0700 (PDT)
From: xdr...@qagtab.mirthmail.com
To: badad...@gfail.com
Message-ID: <2138280715.494.1712230710836@localhost>
Subject: XDM/1.0/DDM Originated Message
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="----=_Part_493_1325979931.1712230710670"
X-XDR-MESSAGE-ID: urn:uuid:16B1F786A329B5E73F1712230710235
X-XDR-MESSAGE-METADATA-LEVEL: minimal
Disposition-Notification-Options: X-DIRECT-FINAL-DESTINATION-DELIVERY=optional,true
Disposition-Notification-To: xdr...@qagtab.mirthmail.com

------=_Part_493_1325979931.1712230710670
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Please find the attached XDM file.
------=_Part_493_1325979931.1712230710670
Content-Type: application/zip; name=16B1F786A329B5E73F1712230710235-xdm.zip
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
        filename=16B1F786A329B5E73F1712230710235-xdm.zip

[Vijetha Nayak]

Any update on this as we are blocked from setting up the environment for certification 

[Katie Crenshaw]

Hi - this testing is part of the server maintenance that is still ongoing. We will post an update when services resume. Thank you for your patience. 

[Vijetha Nayak]

XDR MT Test 13 is always showing the registry response as "Success"

is this synchronous response type?

How do we get an Asynchronous response type? We have waited for more than 15mins but it still shows the response Success

attached the logs for reference 

Any help is appreciated 

[Vijetha Nayak]

Hi Team,

Any help on this query is appreciated

Regards,

Vijetha

[Sai Valluripalli]

The sync response you see is the successful response from your server that the XDR from ETT has been received by your server. 

After you receive the XDR, you need to send a failure MDN in XDR back to the ETT endpoint displayed on the test case as the direct to is a bad address and your system can't deliver to this address.

[Cibi Krishnan]

Hello Team,

Need a bit more assistance on this test case XDR MT 13

Steps

1.  ETT will send a message via XDR to the SUT.

2. SUT received and log an error in the system, see below

From: ckri...@qagtab.mirthmail.com
To: badad...@gfail.com
Subject: XDM/1.0/DDM Originated Message
Date: Date: Mon, 20 May 2024 01:53:05 -0700 (PDT)
Message ID: <1904274852.98.1716195185221@localhost>

Caused by: ERROR=NoTrustedRecipients

3. MDN event recorded in the SUT, see below

Event Type: MDN Information Send

Event Data: Sending Edge DSN info to Endpoint for MDN: https://ett.healthit.gov:11084/xdstools/sim/edge-ttp__32mu2/rep/xdrpr

4. Find the attachment - Received by the tool post clicking on Pending Refresh 

5. The document section has the below content, please confirm if this is the expected behavior.

<direct:messageDisposition xmlns:direct="urn:direct:addressing"> <direct:recipient>mailto:ckri...@qagtab.mirthmail.com</direct:recipient> <direct:disposition>failure</direct:disposition> </direct:messageDisposition>

Address used for the below configuration is "ckri...@qagtab.mirthmail.com"

Outgoing (ETT --> SUT) Direct From Address: 

[Sai Valluripalli]

You should send this back to the ETT - and see it when you click logs.

<direct:messageDisposition xmlns:direct="urn:direct:addressing">
<direct:recipient>mailto:xdr...@qagtab.mirthmail.com</direct:recipient>
<direct:disposition>failure</direct:disposition>
</direct:messageDisposition>

In general If the response is synchronous, then it will be a Registry Response failure.

If the response is asynchronous, you will send an XDR message with a

payload like:
<direct:messageDisposition><direct:recipient>mailto:ent...@direct.example.org</direct:recipient><direct:disposition>failure<direct:disposition><direct:reasonForFailure>reason</direct:reasonForFailure></direct:messageDisposition>

(The reasonForFailure is optional.)

--
You received this message because you are subscribed to the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edge-test-too...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/5f355251-f821-4ec5-beb4-c92c49a10aaan%40googlegroups.com.

[Cibi Krishnan]

Which address needs to be in the <direct:recipient>mailto:</direct:recipient> field?

[Sai Valluripalli]

You can find this information if you click more info on the test case

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/e97d870a-48ff-40aa-b4a3-2b062bce85dan%40googlegroups.com.

[Cibi Krishnan]

Thank You, please clarify my below question.

Attached is the MDN received and find below the base64 encoded information below, confirm if the "Response" tab information is correct. 

<ns4:Document id="8b3d7ce2-b064-4a20-874e-166842517c68">PGRpcmVjdDptZXNzYWdlRGlzcG9zaXRpb24geG1sbnM6ZGlyZWN0PSJ1cm46ZGlyZWN0OmFkZHJlc3NpbmciPiA8ZGlyZWN0OnJlY2lwaWVudD5tYWlsdG86YmFkYWRkcmVzc0BnZmFpbC5jb208L2RpcmVjdDpyZWNpcGllbnQ+IDxkaXJlY3Q6ZGlzcG9zaXRpb24+ZmFpbHVyZTwvZGlyZWN0OmRpc3Bvc2l0aW9uPiA8L2RpcmVjdDptZXNzYWdlRGlzcG9zaXRpb24+</ns4:Document>

Decoded
<direct:messageDisposition xmlns:direct="urn:direct:addressing"> <direct:recipient>mailto:badad...@gfail.com</direct:recipient> <direct:disposition>failure</direct:disposition> </direct:messageDisposition>

Response Tab

Content-Type: multipart/related; boundary=MIMEBoundary112233445566778899; type="application/xop+xml"; start="<do...@ihexds.nist.gov>"; start-info="application/soap+xml" Content-Length: 4 nullContent-Type: application/soap+xml --MIMEBoundary112233445566778899 Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml" Content-Transfer-Encoding: binary Content-ID: <do...@ihexds.nist.gov> <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"><S:Header><wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:s="http://www.w3.org/2003/05/soap-envelope" s:mustUnderstand="1">urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-bResponse</wsa:Action><wsa:RelatesTo xmlns:wsa="http://www.w3.org/2005/08/addressing">37406e91-93cc-4710-98c9-439e9ff1d1a0</wsa:RelatesTo></S:Header><S:Body><rs:RegistryResponse xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success" /></S:Body></S:Envelope>

[Sai Valluripalli]

The response tab should have the MDN. Not sure why it is base64 encoded.

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/91ae2432-1ce1-408e-9fb5-99dbcd45d925n%40googlegroups.com.

[Cibi Krishnan]

The MDN is attached, please have a look. Please help me understand more. Thanks 

[Kim Poletti]

Hello,

Do you have any further questions or is this issue resolved?

Thanks,

Kim