Search found 11 matches

by pim_philipse
Mon, 2008-10-06, 07:59
Forum: DCMTK - General
Topic: User Identity Negotiation
Replies: 9
Views: 13478

We did some analysis on the "experimental" code from the snapshot, and came up with the following suggestions for improvement: 1: memory leak in destructor, second field is not deleted // Destructor, frees memory of primary and secondary field UserIdentityNegotiationSubItemRQ::~UserIdentit...
by pim_philipse
Fri, 2008-10-03, 07:04
Forum: DCMTK - General
Topic: User Identity Negotiation
Replies: 9
Views: 13478

Hi Michael, dcm4chee can send the types 1 and 2. In the following example it appears that their dcmsnd is satisfied with the transaction, and the SCP accepts the user name as well, so this looks promising. If I hack the SCP to send a non-empty response on receiving a type 2 request, dcmsnd reports U...
by pim_philipse
Thu, 2008-10-02, 14:03
Forum: DCMTK - General
Topic: User Identity Negotiation
Replies: 9
Views: 13478

User Identity Negotiation

I found code for this purpose in the 20081001 snapshot. The only problem is that the server is unable to send a response. So please consider this submission: DCUSERID.H: /** Informs the server whether a positive response was requested. * @return OFTrue if a response was requested */ OFBool isPosResp...
by pim_philipse
Tue, 2008-09-23, 13:06
Forum: DCMTK - General
Topic: movescu - DVTk issue
Replies: 5
Views: 7428

The blank (0020,000d) is only used when calling findscu.exe. In the command line that you posted, it is not even clear which of possibly multiple studies you are after. So again, first get the study UID with findscu --study -k 0008,0052=STUDY -k 0010,0020=patID -k 0020,000d and for each response, ca...
by pim_philipse
Tue, 2008-09-23, 09:13
Forum: DCMTK - General
Topic: movescu - DVTk issue
Replies: 5
Views: 7428

cross-posted on the DVTk forum... From PS 3.4-2008 C.4.2.2.1 Baseline Behavior of SCU An SCU conveys the following semantics with a C-MOVE request: — The SCU shall supply a single value in the Unique Key Attribute for each level above the Query/Retrieve level. For the level of retrieve, the SCU shal...
by pim_philipse
Tue, 2006-10-17, 10:32
Forum: DCMTK - General
Topic: Problem retriving worklist to Syngo US machine
Replies: 2
Views: 4138

My guess is that the device rejects the C-FIND responses because of missing type 1 fields: (0040,0007) LO (no value available) # 0, 0 ScheduledProcedureStepDescription (0040,0009) SH (no value available) # 0, 0 ScheduledProcedureStepID ... (0040,1001) SH (no value available) # 0, 0 RequestedProcedur...
by pim_philipse
Mon, 2006-07-24, 07:01
Forum: DCMTK - General
Topic: problem findscu
Replies: 9
Views: 11980

Try

... -k 0008,0052=PATIENT ...

So no quotes, and upper case.
The only time quotes are useful is when they will prevent metacharacters like space and ^ from being eaten by cmd.exe, but then they should surround the entire argument, like

... -k "0010,0010=ALMA TADEMA^LAURENS"

Pim.
by pim_philipse
Mon, 2006-04-10, 08:52
Forum: DCMTK - General
Topic: Socket Problem with imagectn
Replies: 12
Views: 15284

And what happens in the following scenario?

"client" running storescp -v 10001
CTN VM: echoscu -v Dell28-2 10001

Pim.
by pim_philipse
Mon, 2006-04-10, 08:14
Forum: DCMTK - General
Topic: Socket Problem with imagectn
Replies: 12
Views: 15284

HostTable BEGIN vgstd = (xxxxx, Dell28-2, 10001) HostTable END I've never used imgctn, but this is what I read in ctnconf.txt: <ctnconf.txt> 1.2. Host Table (AE Title/Presentation Address Mapping) The Host Table part must be enclosed with the keywords "HostTable BEGIN" and "HostTable...
by pim_philipse
Mon, 2006-04-10, 07:12
Forum: DCMTK - General
Topic: Socket Problem with imagectn
Replies: 12
Views: 15284

Are you running movescu on the same machine as imagectn? Then you must decide which one is allowed to listen on port 104. By default, movescu will try to use 104 for incoming assocaitions (even if the move destination is another AET!) so use the --port switch to select another value (and adapt the i...
by pim_philipse
Wed, 2005-10-26, 07:00
Forum: DCMTK - General
Topic: movescu error, while findscu and echoscu works fine
Replies: 6
Views: 10274

Since you didn't specify the --port where movescu should listen on for the moved instances, it will use port 104, which happens to be used by the server as well. So specify a different port always. Make sure the scp knows about this port. Incidentally, even if the move destination AET is not MOVESCU...