Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dicom Listener Source Connector cannot receive incomming messages from a different IP #2073

Closed
rbeckman-nextgen opened this issue May 11, 2020 · 3 comments
Milestone

Comments

@rbeckman-nextgen
Copy link
Collaborator

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

If you have a Dicom sender sending to a Dicom listener on the same instance of mirth connect it will work properly. But if you are trying to send dicom messages to a Dicom listener from any different IP then it will not pick up the message. Telnet commands from the remote IP to the dicom port are refused. Netstats from the server show the dicom port as active. Case 19311. Reproduced locally by the help desk.

Imported Issue. Original Details:
Jira Issue Key: MIRTH-2116
Reporter: hdmoscm
Created: 2012-03-15T07:44:18.000-0700

@rbeckman-nextgen rbeckman-nextgen added this to the 2.2.2 milestone May 11, 2020
@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

The default listener address is 127.0.0.1. This should be changed to 0.0.0.0 to listen on all interfaces. This change has already been made on some connectors, but it looks like the DICOM listener actually enforces that 127.0.0.1 is for localhost only.

Imported Comment. Original Details:
Author: jacobb
Created: 2012-03-15T11:39:40.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

Changed default DICOM Listener address in Mirth Connect 2.x to 0.0.0.0 so that it listens on all interfaces instead of 127.0.0.1. This was already fixed in Mirth Connect 3.0 by implementing the Listener Properties in MIRTH-2250.

Imported Comment. Original Details:
Author: jacobb
Created: 2012-11-09T13:21:59.000-0800

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

In 3.0 this was fixed by making DICOM use the overall Listener Settings, which now has a default of 0.0.0.0. In 2.2.2 this was fixed by changing the default value to 0.0.0.0.

Imported Comment. Original Details:
Author: jacobb
Created: 2012-12-20T18:49:43.000-0800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant