cannot start to listen port to PACS

Bug reports for MicroDicom viewer
Post Reply
iv.evg
Posts: 3
Joined: Tue Apr 27, 2021 4:44 pm

cannot start to listen port to PACS

Post by iv.evg »

Dear all,
I tried several times to configure Microdicom to be connected to ORTHANC pacs.

The problem is somewhere in the Microdicom. For every port configuration it reports Cannot start to listen to port XXXX. I have other dicom viewers installed - configured on 11112, 4242 and 104 and all of them are working fine with my ORTHANC server. JSON file is configured correct. Firewall is properly configured.
Here are two screen shots.
MICRODICOM_screen_2.jpg
MICRODICOM_screen_2.jpg (592.97 KiB) Viewed 738 times
MICRODICOM_screen_1.jpg
MICRODICOM_screen_1.jpg (647.66 KiB) Viewed 738 times
Suggestion?

Regards
Ivan
microdicom
Site Admin
Posts: 324
Joined: Thu Jan 01, 1970 2:00 am
Location: Bulgaria
Contact:

Re: cannot start to listen port to PACS

Post by microdicom »

Hello,
Thanks for the screenshots. They help a lot for resolving this issue. I saw the following:
-Orthanc server is started on local machine(127.0.0.1) port 4242
-Error message "Couldn't start listening on port 4242" is shown ONLY when MicroDicom can't open the port for communication. This happen when this port is used by other application.
It say 4242!!! This port is already used by Orthanc server on local machine. You can't use the same port for MicroDicom application. You have to change it.

Also I notice one error. I can't clearly see on the screenshot, but you type "127.0._0.1". There is a white space. Maybe we have to read much better the user input. Bur for now remove this white space.

Please see the following screenshot how you have to make the settings in Orthanc and MicroDicom:
The IP of my Orthanc server is: 192.168.1.10 Port 4242
MicroDicom is used on the PC with IP:192.168.1.41 I use port 11112.
Attachments
mDicom_xLG2UXO5u6.png
mDicom_xLG2UXO5u6.png (23.62 KiB) Viewed 731 times
chrome_AU0nCKOEur.png
chrome_AU0nCKOEur.png (40.25 KiB) Viewed 731 times
iv.evg
Posts: 3
Joined: Tue Apr 27, 2021 4:44 pm

Re: cannot start to listen port to PACS

Post by iv.evg »

Thank you for the reply!
I tried all known DICOM ports - 11112 (default for MicroDICOM), 104 and 4242. One the same negative result.
The white space on the screen is only visual effect. It is clear 127.0.0.1.
Here is copy of the json for dicom modalities set-up:

"MicroDICOM" : [ "MICRODICOM", "127.0.0.1", 4242 ],
"RUBO" : [ "RUBOVIEWER", "192.168.67.52", 11112 ],
"OrthancU" : ["ORTHANC", "4x.xx.xx.44", 4242],
"OrthancAA" : ["ORTHANCAA", "8x.xx.xx.x8", 4242],
"MicroDICOM" : ["MICRODICOM", "8x.xx.xx.x9", 11112]

In both cases MicroDICOM does not want to start to listen DICOM port - 4242 and 11112.

Please, some help.
I.E.
iv.evg
Posts: 3
Joined: Tue Apr 27, 2021 4:44 pm

Re: cannot start to listen port to PACS

Post by iv.evg »

And one more result from experiments
I sent to MicroDICOM images from two ORTHANC servers.
It received them both when was in Network/Download from DICOM server screen but no one being in other modes.
May it is my misunderstanding whet MicroDICOM is in listening mode.
microdicom
Site Admin
Posts: 324
Joined: Thu Jan 01, 1970 2:00 am
Location: Bulgaria
Contact:

Re: cannot start to listen port to PACS

Post by microdicom »

Thanks for answer.
This message "Couldn't start listening on port X" just mean that this port is already opened on this machine.

But in the latest message that you wrote, you told us that you received image. Therefore it have to work.
I already wrote you e-mail on 4/27/2021, 11:59 PM. Please check your e-mail and we will continue the conversation over e-mail.

Thank you,
Post Reply