Issue receiving from one machine

[Daniel Carrion]

Hi there

Just wondering if you could assist with a situation I'm running into with using ruby-dicom to receive transmissions from one particular unit. I see messages like this:

I, [2016-05-29T01:39:40.370174 #8900]  INFO -- RECEIVER: Connection established with:  172.27.101.122  (IP: 172.27.101.122)
I, [2016-05-29T01:39:40.372174 #8900]  INFO -- RECEIVER: Accepted all 8 proposed contexts in the association request.
I, [2016-05-29T01:40:57.982174 #8900]  INFO -- RECEIVER: Connection established with:  172.27.101.122  (IP: 172.27.101.122)
I, [2016-05-29T01:40:57.984174 #8900]  INFO -- RECEIVER: Accepted all 8 proposed contexts in the association request.
I, [2016-05-29T01:42:18.051174 #8900]  INFO -- RECEIVER: Connection established with:  172.27.101.122  (IP: 172.27.101.122)
I, [2016-05-29T01:42:18.053174 #8900]  INFO -- RECEIVER: Accepted all 8 proposed contexts in the association request.
I, [2016-05-29T01:43:58.105174 #8900]  INFO -- RECEIVER: Connection established with:  172.27.101.122  (IP: 172.27.101.122)
I, [2016-05-29T01:43:58.107174 #8900]  INFO -- RECEIVER: Accepted all 8 proposed contexts in the association request.
I, [2016-05-29T01:46:00.372174 #8900]  INFO -- RECEIVER: Connection established with:  172.27.101.122  (IP: 172.27.101.122)
I, [2016-05-29T01:46:00.378174 #8900]  INFO -- RECEIVER: Accepted all 8 proposed contexts in the association request.
I, [2016-05-29T01:47:00.442174 #8900]  INFO -- RECEIVER: Connection established with:  172.27.101.122  (IP: 172.27.101.122)
I, [2016-05-29T01:47:00.443174 #8900]  INFO -- RECEIVER: Accepted all 8 proposed contexts in the association request.

Followed by timeout abort messages:

E, [2016-05-29T01:48:58.107174 #8900] ERROR -- RECEIVER: No answer was received within the specified timeout period. Aborting.

Timeout currently set to 300.

If I look at the ruby process it's thrashing CPU for a long time before I manually kill it off. I see memory util jump up then back down as it cycles.

Any advice on the best way to troubleshoot this? For the moment I'll switch back to dcm4che toolkit to receive these particular transmissions.

Regards

Daniel

[Daniel Carrion]

See attached "good_sample.txt" showing successful receipt by dcm4che SCP instance. Hopefully this helps...

[Daniel Carrion]

Thanks to Christoffer I've been able to work through this.

We found through the packet capture that there was a abstract syntax (private) in the proposal that ruby-dicom didn't support:

Abstract Syntax: 1.2.840.113619.4.30  - GE Advance (PET) Raw Data Storage

Adding the UID to DICOM library and adding the abstract syntax solved this. E.g.:

DICOM::LIBRARY.add_uid(DICOM::UID.new('1.2.840.113619.4.30', 'Private Storage', 'SOP Class', ''))
s = DServer.new(104, :host_ae => "MY_DICOM_SERVER")
s.add_abstract_syntax('1.2.840.113619.4.30')
s.start_scp("C:/Temp")

Thanks again Christoffer for your assistance with this one. 

Regards

Daniel