Working movescu with same --port and port number. Bad?

Compilation and installation of DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
normandrobert
Posts: 3
Joined: Mon, 2020-10-26, 13:51

Working movescu with same --port and port number. Bad?

#1 Post by normandrobert » Tue, 2021-05-04, 22:58

movescu below works fine. Is port number reuse (11112) below problematic? Having to go through FWs so some ports closed or one way. Wish to know if it is an issue before asking anyone to change networking.

Also does anyone know about this warning below?
"RECV: W: DcmItem: Invalid Element (0002,0010) found in data set"
AGFA archive.

Merci.

movescu -v -P -aet SRIHDIRS --port 11112 -aec ONDR01IDCSAS -k QueryRetrieveLevel="IMAGE" -k SOPInstanceUID="1.2.840.113619.2.323.550149264542.1509468041.18" 138.218.233.66 11112 -od /home/user/incoming
I: Requesting Association
I: Association Accepted (Max Send PDV: 16340)
I: Sending Move Request (MsgID 1)
I: Request Identifiers:
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0008,0018) UI [1.2.840.113619.2.323.550149264542.1509468041.18] # 48, 1 SOPInstanceUID
I: (0008,0052) CS [IMAGE] # 6, 1 QueryRetrieveLevel
I:
I: Received Move Response 1 (Pending)
I: Sub-Association Received
I: Sub-Association Acknowledged (Max Send PDV: 16340)
I: Received Store Request (MsgID 1, US)
RECV: W: DcmItem: Invalid Element (0002,0010) found in data set
...................................................................................................................................
W: DICOM file already exists, overwriting: /home/user/incoming/US.1.2.840.113619.2.323.550149264542.1509468041.18
I: Received Final Move Response (Success)
I: Releasing Association

Michael Onken
DCMTK Developer
Posts: 1815
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: Working movescu with same --port and port number. Bad?

#2 Post by Michael Onken » Wed, 2021-05-05, 08:24

Hi,

DICOM datasets, i.e. actual DICOM objects (CT image, Structured Report, etc.) never contain tags from group (0002,...) since those are reserved for the DICOM meta header which is part of the DICOM file format.

When you transfer DICOM file (in file format) to a network destination, you have to cut off the meta header (0002,xxxx tags) from the file and only transfer the dataset. So movescu just warns you that the sender forgot to remove those (0002,....) tags for network transfer. This is a violation against the DICOM standard, however, I guess that most receivers (like movescu) can handle it.

The smallest group number that can appear in dataset is (0008,xxxx). Therefore, the first tag in a dataset is often Specific Characterset (0008,0005).

Best regards,
Michael

normandrobert
Posts: 3
Joined: Mon, 2020-10-26, 13:51

Re: Working movescu with same --port and port number. Bad?

#3 Post by normandrobert » Wed, 2021-05-05, 16:20

Merci Michael
I was also/primarily concerned about port number re-use. Do you have a comment on that? :roll:
Regards
Normand

Michael Onken
DCMTK Developer
Posts: 1815
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: Working movescu with same --port and port number. Bad?

#4 Post by Michael Onken » Wed, 2021-05-05, 16:51

Ah, yes, sorry, I read over that one.

Not 100% sure if I understand the question, but:

You cannot use the same port on the same system, so in that regard you cannot "re-use" a port. So if 138.218.233.66 is yourself then you should use a different port at the "--port 1112" option. Make sure the PACS has configured you with the port you provide to the "--port" option.

Otherwise, 11112 is one of the two typical DICOM ports (the other one being 104) and people tend to use those, so its a good choice in general.

Best,
Michael

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest