How can I extract the different errors and reasons for rejection in an association?

[anibal2j]

Hi,

Just getting started with pynetdicom and I'd like to be able to extract the actual reasons for an association to not be established.

These are the ones that I know I'd like to extract (amongst others):

1. Invalid IP - timeout
2. Invalid port - connection refused
3. Bad calling AE
4. Bad called AE
5. Whatever reason is sent by the SCP

I can't figure out how to get the low-level error strings from the network layer for the first 2 errors. I see them in stderr when using ae.associate() but I can't extract them in code.

And for those cases where the connection is established, how do I extract the Reason I see the SCP sending?

Thanks a lot!

[scaramallion]

General connection failures and the timeouts are sort of available via the state machine and event 17. Actual reasons for the failures during the attempt to connect with a peer aren't generally available since they get caught here.

It should be possible to add a new intervention event and tie it to the connection attempt failure. I'm not sure how friendly that would be, you may end up having to parse the various exception types and/or OS specific messages.

And for those cases where the connection is established, how do I extract the Reason I see the SCP sending?

The Reason property is only available when the Association is rejected or aborted.

[anibal2j]

That line that you reference in transport.py (line 251) is exactly what I'm looking for. Wouldn't it be possible to store that information, i.e., the contents of exc to a state variable that the user can then extract from the object? I know the transport might be buried deep inside, and not easy to expose to the client, but this would be a really nice feature to have. I'm building a DICOM monitor service and I have all the errors due to DICOM misconfiguration, but I'm missing network errors. This means that I now have to use the regular networking library to do the same connection that pynetdicom is doing just to be able to extract whether I'm getting connection refused or connection timed out - which are very useful variables to know when I'm monitoring the network.

[scaramallion]

Yes, it would be a nice addition