Gateway issues

[caze.frazao]

Hi,

There three things happening with our facilities that I'd like some help:
First is that some X-ray studies that have over 6 images, just upload 3 or four of them. Sometimes, if you send the study again the rest of images are uploaded, but most of time they are not. Is there any restriction of number of images by study?

The other problem is that some of our facilities have a poor internet upload band. Therefore we expect studies would take longer to reach onepacs web server. However, they don't get there ever. Any ideas why does it happen or how to solve it?

And the third one is the most weird for me. Some times a study, which is being sending by a facility which gateway is working properly, does not appear at the web server. I've checked and those studies are at the gateway, but I don't know why they don't get at the web server. I've already tried to erase them from the gateway and send them again, and still they are not uploaded. Other studies are uploaded with no problems but those keep not coming. And it happens at different facilities which uses different CR brands (Carestream, Fuji and Agfa). Is there anything else I should try to make it work?

Thanks.

[caze.frazao]

Anyone?

[jeremy]

Hello
1. The OnePacs Gateway will not re transmit studies that it has already received. You can resend an existing study using the following instructions
https://onepacshelp.com/display/T5/Manu ... cs+Gateway

2. Suspect that the connection is timing out.
You adjust the timeout by using the instructions below.
Configure the MoveScu
Log into the admin console: http://localhost:8080/jmx-console
Select service=MoveScu
Set AcceptTimeout to a reasonable value in milliseconds (ex. 10000).
Set DIMSETimeout to a reasonable value in milliseconds (ex. 6000000).
Apply Changes
Configure the QueryRetrieveSCP
Log into the admin console: http://localhost:8080/jmx-console
Select service=QueryRetrieveSCP
Set AcceptTimeout to a reasonable value in milliseconds (ex. 10000).
Set DIMSETimeout to a reasonable value in milliseconds (ex. 6000000).
Apply Changes
Configure the DcmServer
Log into the admin console: http://localhost:8080/jmx-console
Select service=DcmServer
Set RequestTimeout to a reasonable value in milliseconds (ex. 10000).
Set DIMSETimeout to a reasonable value in milliseconds (ex. 6000000).
Apply Changes

3. Not really enough information. One possibility is that the study, series, or instance UIDs defined conflict in some way. You could try to anonymize the study, series, and instance UIDs and try to resend to see if that helps.

[caze.frazao]

Jeremy,

Thanks for your reply. I'll try to follow your orientations.
I've just seen your reply. I was waiting to receive an e-mail when this post had been replied, but I didn't. That's why I'm thanking you just now.

Cheers.