|
From: Mathieu M. <mat...@gm...> - 2010-10-12 15:50:09
|
Did you get DCMTK command line working with this dcm4che server ? If so send us the command line that work with dcmtk and the one that does not in GDCM. Thanks ! On Mon, Oct 11, 2010 at 7:08 PM, Paulo Henrique Junqueira Amorim <pau...@gm...> wrote: > Hi, > > I sent the following command to dcm4chee: > > C:\Documents and > Settings\phamorim\Desktop\gdcm_git_BIN\bin\Release>gdcmscu.exe > 200.144.114.143 11112 --echo > Process: Event:0, State:0 > Process: Event:1, State:3 > Process: Event:3, State:4 > > In the server log (DCM4CHEE) the following message appears: > > 14:02:10,359 INFO [ServerImpl] handle - > Socket[addr=/200.144.114.65,port=1186,localport=11112] > 14:02:10,375 INFO [FsmImpl] > Socket[addr=/200.144.114.65,port=1186,localport=11112] > 14:02:10,375 INFO [FsmImpl] received AAssociateRQ > appCtxName: 1.2.840.10008.3.1.1.1/DICOM Application Context Name > implClass: 1.2.826.0.1.3680043.2.1143.107.104.103.115.2.1.0 > implVersion: GDCM 2.1.0 > calledAET: ANY-SCP > callingAET: GDCMSCU > maxPDULen: 16384 > asyncOpsWindow: > pc-1: as=1.2.840.10008.1.1/Verification SOP Class > ts=1.2.840.10008.1.2/Implicit VR Little Endian > 14:02:10,375 INFO [FsmImpl] sending A-ASSOCIATE-RJ > result=1 - rejected-permanent > source=1 - service-user > reason=7 - called-AE-title-not-recognized > 14:02:10,437 INFO [FsmImpl] closing connection - > Socket[addr=/200.144.114.65,port=1186,localport=11112] > 14:02:10,437 INFO [ServerImpl] finished - > Socket[addr=/200.144.114.65,port=1186,localport=11112] > > > What was strange that every time I send the port changes, thus has no way of > registering the port in dcm4chee. > > is that right?? > > -- Mathieu |