Release instead of Abort when network_timeout expires

Hello!

I’m using the default network_timeout, which is 60 seconds. After 60 seconds of inactivity, the association aborts

I: Aborting Association
D: Abort Parameters:
D: ============================ BEGIN A-ABORT PDU =============================
D: Abort Source: DUL service-user
D: Abort Reason: No reason given
D: ============================= END A-ABORT PDU ==============================

Is there a way to set the association to get released, rather than aborted, after the timeout expires?

[scaramallion]

I’ve added the Association.network_timeout_response attribute - if you set it to "A-RELEASE" then it’ll do the normal association release instead of abort when the network timeout expires.

[GreasyAvocado]

I agree with what you wrote, that’s also how I see it:

release is for “friendly” disconnects while a network timeout is an “unfriendly”

In the meantime we’ve implemented a timeout mechanism in Python, based on this: https://stackoverflow.com/questions/2281850/timeout-function-if-it-takes-too-long-to-finish We now count the time since the association was last active, and properly releases it if it’s been idle for 50 seconds (before the 60 seconds timeout of network_timeout).

If it would be possible to achieve the same natively with pynetdicom, by adding a config option, that would be amazing! It would save us all the timeout logic 😃