OnePacs Forums

I am trying to use the DICOM send option from the Onepacs workstation to connect to syngo plaza. I have gone through the online documentation and added the server with its details (host name, AE title, port no.). I have also added onepacs workstation as a network partner in plaza with the AE title and port no. mentioned in the Dicom server details of onepacs. When I verify the connection with echo i get a failure. Upon trying to send a file from onepacs to plaza I get the error message (association rejected). Please assist me in setting up this functionality on my onepacs workstation

What is the full text of the failure messages you receive both during c-echo and when you try to send an image?

I have sent the error logs from the poller and workstation to the administrator through internal messsge in onepacs.

Ok I will review the logs.

FIrst it would still be helpful if you would post the precise text of the error message you receive into this issue.

Also, the best way to get logs for troubleshooting is described here:

http://wiki.onepacsforums.com/doku.php? ... debug_logs

What you sent will also work, but the above will be less trouble and may provide more information.

Looking at the logs, the logs indicate that the remote host is refusing the connection.

Therefore I think at this point what you need to do is look in the logs for the remote host (that you're trying to send to) and have the vendor for that host help you.

Double check that the AE title is entered correctly (and is case-sensitive). One thing that is tricky in DICOM sometimes is that the c-echo may not be case sensitive, but making an association to send images can be. So something could echo OK but you might not be able to send to it.

If you have double checked and the AE title for the OnePacs gateway is entered correctly in the remote host, we'll have to refer you to the support people for the system you're trying to send to, as the logs indicate that OPW is trying to send the images but the remote host you are trying to connect to is refusing the connection. So I don't think there's much more we can do on our end to trouble shoot this. Good luck