Movescu with Efilm 3.0.1

[sberkowi]

I am using Movescu in a script to automatically send studies from an instance of Efilm to another dicom device. This has worked successfully with Efilm 2.1.0 and 1.5.3. I am indebted to DCMTK, the great documentation, and this forum for initially getting me up and running. However, my institution has 'upgraded' to Efilm 3.0.1 and I now get an error when using Movescu. I have contacted their technical support and have not gotten very far. I was wondering if anyone else has had similar problems and has any solutions.

I am calling Movescu as follows to move a particular series specified by study and series UIDs:

Code: Select all

movescu -v -d --study -k 0008,0052="SERIES" -k 0020,000d="####" -k 0020,000e="####" -aet MESC_TAG -aem MESC_TAG -aec RADDSK8392 ##.##.###.### 4006

MESC_TAG is the AE of the destination dicom device, an instance of simple_storage (from the Wash U CTN). This AE is known to efilm, and I can verify and send to this device manually within efilm.

RADDSK8392 is the AE of efilm followed by its hostname and port.

Both efilm and simple storage are running on the same workstation at ports 4006 and 104 respectively.

Here is the error I receive from Movescu:

Code: Select all

Requesting Association
Association Accepted (Max Send PDV: 28660)
================================
Sending query
Move SCU RQ: MsgID 1
Request:

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0008,0052) CS [SERIES]                                 #   6, 1 QueryRetrieveLevel
(0020,000d) UI [1.2.840.113696.596650.500.1295580.20060502065426] #  48, 1 StudyInstanceUID
(0020,000e) UI [1.3.12.2.1107.5.2.30.25497.30000006050210004482800000315] #  56, 1 SeriesInstanceUID
C-Move RSP: MsgID: 1 [Status=Failed: UnableToProcess]
  AffectedSOPClassUID: =MOVEStudyRootQueryRetrieveInformationModel
  Data Set: Not Present
  Status Detail:

# Dicom-Data-Set
# Used TransferSyntax: LittleEndianImplicit
(0000,0902) LO [Unable to process!]                    #  18, 1 ErrorComment
Releasing Association

I have looked through the _DICOM.log for Efilm and seen the following:

Code: Select all

(4344) 09-07 23:25:31.30 MC3  W: Association Rejected
(4344) 09-07 23:25:31.30 MC3  W: Association automatically rejected:
(4344) 09-07 23:25:31.30 MC3  W: |  Codes: Result 0x01 Source 0x01 Reason 0x07
(4344) 09-07 23:25:31.30 MC3  W: |  Unacceptable Called_application_title: MESC_TAG
(4344) 09-07 23:25:31.30 MC3  W: |  Result code 1: Permanent Rejection
(4344) 09-07 23:25:31.30 MC3  W: |  Calling_presentation_address: unknown (##.##.###.###)
(4344) 09-07 23:25:31.30 MC3  W: |  Result source 1: UL service user
(4344) 09-07 23:25:31.30 MC3  W: |  Calling_application_title: RADDSK8392
(4344) 09-07 23:25:31.30 MC3  W: |  Result reason 7: Unacceptable Called AP Title
(4344) 09-07 23:25:31.31 [class CDICOMAssociation * Open()] Unable to open association, rejected by remote AE: MESC_TAG ##.##.###.###(4006)
(4344) 09-07 23:25:31.31 CMoveRoot::SendImages: Unable to open a DICOM Association. Error message = Association negotiation failed. See details in 'merge.log'.
(4344) 09-07 23:25:32.31 AssociationHandler: Timeout of MC_Wait_For_Association.

My inexperienced interpretation from this error is that the target AE is not known to efilm. However, this is not the case since I can successfully send to this AE from within the efilm software. Again, I have used Movescu like this on prior versions of efilm. I suspect the problem is in the new version but, their tech support has not had any insight. Any help is greatly appreciated.
--Seth B

[st80rules]

I don't think that setting the same aet and aem makes sense, it indicates the same source and target machines.

Norm

[sberkowi]

Thanks for the thought Norm but that's not the problem. Source machine is set by -aec.

From the movescu documentation:

Code: Select all

application entity titles:

  -aet  --aetitle  aetitle: string
          set my calling AE title (default: MOVESCU)

  -aec  --call  aetitle: string
          set called AE title of peer (default: ANY-SCP)

  -aem  --move  aetitle: string
          set move destination AE title (default: MOVESCU)

[st80rules]

Just a shot in the dark, but efilm seems to dislike the MESC_TAG name. Have you tried another name, without the underscore?

Norm

[nschafer]

I went ahead and tried to move from an Efilm 3.01 station at my office. I recived the same error message you listed. I checked the dicom log for Efilm (c:\program files\Merge Efilm\Efilm\Log\youraetitle_dicom) and found the following information:

Unable to open association, could not be negotiated with remote AE 'movescu' on xxx.xxx.xxx.xxx(4006): Failed to connect to remote host

The interesting thing here is that I had registered movescu in Efilm as port 104, but it was still trying to send to port 4006. Since I was sending to another computer this didn't pose a problem. I simply adjusted my command line to use port 4006 instead of 104 but since you are on sending from and to the same machine this would be a problem. I justed used movescu instead of storescp or another storage provider, but my thought is you may have the same issue. Check your logs.

Here's the command I used successfully:

Code: Select all

movescu -v -S +P 4006 -k 0008,0052=STUDY  -k 0020,000d=####### -aet movescu -aec AETITLE xxx.xxx.xxx.xxx 4006

Hope this helps,
Neal.

[sberkowi]

Thanks for the help Neal.

Interesting observation. I tried changing the port that Efilm is running on and then the error message in the Efilm dicom log changes to:

Unable to open association, could not be negotiated with remote AE 'MESC_TAG' on ##.##.###.###(3200): Failed to connect to remote host

It seems that Efilm thinks the remote device is always on the same port as it is running on.

I wanted to try sending to another machine to test if I could send to a different host, same port like you had success with.

However, when I try to use an AE on a different machine I get an error from movescu, and no update to the efilm logs:

(0000,0902) LO [Refused: Remote AE is not in the list.] # 38, 1 ErrorComment

The the new AE is definitely in the Efilm device list. Is there another list I'm missing?

I will also try getting back in touch with Merge tech support, as the reproducibility of this error makes it more likely that the problem is on their end.

Thanks for the help!

[sberkowi]

Efilm technical support has not been helpful. Efilm 3.0.1 uses a SQL database instead of Access which is used by 2.1.0. I thought that might be an issue since the remote devices are stored in this database. However, I switched Efilm 3.0.1 to use an Access database and still had the same behavior with Movescu. I will probably downgrade to Efilm 2.1.0 on my workstation, but there are many other workstations in my institution with the same problem, so this is a suboptimal solution.

Does anyone know any other command line tools that I could use to send a C-move command other than movescu?

Thanks,
Seth

[tom]

you can probaly try :

http://dicom.dvtk.org/modules/wiwimod/i ... u=products

i will by interested to know if you have success to connect to last version of efilm with dcmtk tools. it is strange ,it sound like a bug in efilm .. !!

never mind , it is not a command line tool sorry.