Capture the reason why failed to establish association

[evergreen-shankar]

Hi, I have an application which performs C-ECHO, C-FIND, C-STORE and C-MOVE. I would like to capture the reason when the association fails while performing these tasks. I have tried with following codebase.

from pynetdicom.sop_class import VerificationSOPClass
from pynetdicom import AE

# Initialise the Application Entity
ae = AE()

# Add a requested presentation context
ae.add_requested_context(VerificationSOPClass)

# Associate with peer AE at IP 127.0.0.1 and port 11112
try:
    assoc = ae.associate('127.0.0.1', 11112)
    if assoc.is_established:
        print("Association established successfully!")
    elif assoc.is_rejected:
        msg = ('{0}: {1}'.format(
            assoc.acceptor.primitive.result_str,
            assoc.acceptor.primitive.reason_str
        ))
        print(msg)
    elif assoc.is_aborted:
        # Capture the aborted reason
        pass
    else:
        # Capture the any other reason why failed to establish association
        print("Failed to establish association.")
except Exception as e:
    print("Failed to establish association. Reason:", e)

[scaramallion]

Troubleshooting associations

[evergreen-shankar]

Using the above link only i have copied and handled for rejected but when i used the same for aborted then primitive value is coming None and there is no result and reason value.

In my case failure reason is

I: Requesting Association
E: Association request failed: unable to connect to remote
E: TCP Initialisation Error: [WinError 10061] No connection could be made because the target machine actively refused it
I: Aborting Association

How to capture the error TCP Initialisation error

[scaramallion]

Those can't be captured except through the logging...

Hmm, I suppose I could add another event for TCP connection failures?

[evergreen-shankar]

Oh, It will be great if implementation is added and we can extract the reason for abort same way how it is available for reject

[scaramallion]

You need to look at the A-ABORT-RQ message if you want the abort reason, although I doubt you'll find them very useful. DICOM has no facility for aborters to send a "I am aborting this because of X" message.

The top-line A-ABORT primitive only has the abort source.

[evergreen-shankar]

You are right. I have looked at A_ASSOCIATE but it throws error for this assoc.dul.acceptor.