calling-AE-title-not-recognized

1,602 views
Skip to first unread message

Dragev

unread,
Aug 16, 2016, 4:06:42 AM8/16/16
to dcm4che

Hi!

I apologize if this topic has already been covered somewhere in this forum, but I couldn't find topics with the same issue.
I'm new to dcm4chee and encountered the following error:

10:44:23,237 INFO  [AbstractScuService] Open association to AN_PARNU64523 url:dicom://AN_PAR...@192.168.126.100:104 Ciphers:[]
10:44:23,241 INFO  [EchoService] Try to bind socket to callingAE:dicom://MIRTHWL@localhost:11112 hostname:localhost
10:44:23,241 INFO  [EchoService] Socket bound to localhost
10:44:23,245 INFO  [Association] Association(8) initiated Socket[addr=/192.168.126.100,port=104,localport=56695]
10:44:23,246 INFO  [PDUEncoder] AN_PARNU64523(8): A-ASSOCIATE-RQ AN_PARNU64523 << MIRTHWL
10:44:23,246 INFO  [Association] AN_PARNU64523(8) >> org.dcm4che2.net.pdu.AAssociateRJ: A-ASSOCIATE-RJ[result=1, source=1, reason=3]: permanent calling-AE-title-not-recognized
10:44:23,246 ERROR [EchoService] Echo dicom://AN_PAR...@192.168.126.100:104 failed
org.dcm4che2.net.pdu.AAssociateRJ: A-ASSOCIATE-RJ[result=1, source=1, reason=3]:
 permanent calling-AE-title-not-recognized
        at org.dcm4che2.net.PDUDecoder.nextPDU(PDUDecoder.java:186)
        at org.dcm4che2.net.Association.run(Association.java:881)
        at java.lang.Thread.run(Thread.java:745)
10:44:23,246 INFO  [Association] AN_PARNU64523(8): close Socket[addr=/192.168.126.100,port=104,localport=56695]


It seems as if I have not configured the AE-title AN_PARNU64523, however under service=AE I can invoke the "get AE configuration" with the argument "AN_PARNU64523". This gives me the following result:
"dicom://AN_PAR...@192.168.126.100:104"

Can anyone help me with this problem?

cavit altindag

unread,
Aug 18, 2016, 1:29:35 AM8/18/16
to dcm4che
I am not sure but probably you should check your server identification. Which is under xmbean attributes.

Jose Luis Stegmaier

unread,
Jan 2, 2018, 9:52:44 AM1/2/18
to dcm4che
The caracter "_" and java are not good together


El martes, 16 de agosto de 2016, 5:06:42 (UTC-3), Dragev escribió:

Hi!

I apologize if this topic has already been covered somewhere in this forum, but I couldn't find topics with the same issue.
I'm new to dcm4chee and encountered the following error:

10:44:23,237 INFO  [AbstractScuService] Open association to AN_PARNU64523 url:dicom://AN_PARNU64523@192.168.126.100:104 Ciphers:[]

10:44:23,241 INFO  [EchoService] Try to bind socket to callingAE:dicom://MIRTHWL@localhost:11112 hostname:localhost
10:44:23,241 INFO  [EchoService] Socket bound to localhost
10:44:23,245 INFO  [Association] Association(8) initiated Socket[addr=/192.168.126.100,port=104,localport=56695]
10:44:23,246 INFO  [PDUEncoder] AN_PARNU64523(8): A-ASSOCIATE-RQ AN_PARNU64523 << MIRTHWL
10:44:23,246 INFO  [Association] AN_PARNU64523(8) >> org.dcm4che2.net.pdu.AAssociateRJ: A-ASSOCIATE-RJ[result=1, source=1, reason=3]: permanent calling-AE-title-not-recognized
10:44:23,246 ERROR [EchoService] Echo dicom://AN_PAR...@192.168.126.100:104 failed
org.dcm4che2.net.pdu.AAssociateRJ: A-ASSOCIATE-RJ[result=1, source=1, reason=3]:
 permanent calling-AE-title-not-recognized
        at org.dcm4che2.net.PDUDecoder.nextPDU(PDUDecoder.java:186)
        at org.dcm4che2.net.Association.run(Association.java:881)
        at java.lang.Thread.run(Thread.java:745)
10:44:23,246 INFO  [Association] AN_PARNU64523(8): close Socket[addr=/192.168.126.100,port=104,localport=56695]

It seems as if I have not configured the AE-title AN_PARNU64523, however under service=AE I can invoke the "get AE configuration" with the argument "AN_PARNU64523". This gives me the following result:

p.p...@synedra.com

unread,
Jan 3, 2018, 8:38:01 AM1/3/18
to dcm4che
No, this is definitely not the issue. AE titles commonly contain underscores, and neither dcm4che nor Java are known to have problems with them. Maybe you mean something else, or a very specific case? Care to elaborate?
Reply all
Reply to author
Forward
0 new messages