在echoscu中称为AE标题未识别错误

时间:2018-02-07 01:13:46

标签: dicom dcmtk

我试图测试dcmqrscp的连接性。 我使用以下命令启动dcmqrscp。

dcmqrscp --config C:\Dicom\config\dcmqrscp.cfg

请找到我使用的以下配置文件。

NetworkTCPPort  = 11113
MaxPDUSize      = 16384
MaxAssociations = 16

HostTable BEGIN

acme1           = (ACME1, localhost, 1234) 
acme2           = (ACME2, localhost, 5678)
acmeCTcompany   = acme1, acme2

HostTable END

VendorTable BEGIN

"Acme CT Company"   = acmeCTcompany

VendorTable END

AETable BEGIN

ACME_STORE   C:\Dicom\echo   RW (100, 1024mb)   acmeCTcompany

AETable END

我在运行dcmqrscp命令之前也创建了C:\ Dicom \ echo。 以下echoscu命令用于测试dcmqrscp的连接: echoscu -d localhost 11113 -aec ACME_STORE -aet ACME1

但是我收到以下错误:

D: $dcmtk: echoscu v3.6.0 2011-01-06 $
D:
D: Request Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ =====================
D: Our Implementation Class UID:      1.2.276.0.7230010.3.0.3.6.0
D: Our Implementation Version Name:   OFFIS_DCMTK_360
D: Their Implementation Class UID:
D: Their Implementation Version Name:
D: Application Context Name:    1.2.840.10008.3.1.1.1
D: Calling Application Name:    ACME1
D: Called Application Name:     ACME_STORE
D: Responding Application Name: resp. AP Title
D: Our Max PDU Receive Size:    16384
D: Their Max PDU Receive Size:  0
D: Presentation Contexts:
D:   Context ID:        1 (Proposed)
D:     Abstract Syntax: =VerificationSOPClass
D:     Proposed SCP/SCU Role: Default
D:     Proposed Transfer Syntax(es):
D:       =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation:  none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response:  none
D: ======================= END A-ASSOCIATE-RQ ======================
I: Requesting Association
D: Constructing Associate RQ PDU
F: Association Rejected:
F: Result: Rejected Permanent, Source: Service User
F: Reason: Called AE Title Not Recognized

我的观察之一:在正常的回声操作中,数据字典被正确加载。但在上面的echoscu日志中,我们找不到任何数据字典加载操作。

你能帮我解决一下这个问题。

2 个答案:

答案 0 :(得分:3)

您是否还确保目录C:\ Dicom \ echo是可写的?如果将“acmeCTcompany”(“AE表”中的最后一列)更改为“ANY”,它是否有效?在任何情况下,我也会使用-d( - debug)启动dcmqrscp以查看更多详细信息。

答案 1 :(得分:1)

我会发表评论,因为这可能对将来有所帮助。我认为以下方案是由不正确的主机配置导致的,遗憾的是我现在无法检查。

当echoscu连接到dcmqrscp时,后者会收到以下参数的关联:callingPresentationAddresscallingAPTitlecalledAPTitle。第一个参数只是echoscu的唯一主机地址。

如果 echoscu和dcmqrscp都在同一台Windows计算机上运行,则callingPresentationAddress设置为hostname的值。可以通过ipconfig /all部分中的Windows IP Configuration获取该值:

>ipconfig /all

Windows IP Configuration 
  Host Name . . . . . . : MY_PC
  Primary DNS Sufix . . :
  Node Type . . . . . . : Hybrid
  IP Routing Enabled. . : No
(...)

应在HostTable部分的dcmrscp配置文件中设置相同的值:

HostTable BEGIN
acme1           = (ACME1, MY_PC, 1234) 
(...)
HostTable END