echoscu Responding Application Name confusion

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
robertsdavidb
Posts: 17
Joined: Thu, 2012-09-27, 09:12

echoscu Responding Application Name confusion

#1 Post by robertsdavidb »

I started an instance of storescp like this.

Code: Select all

storescp -d -aet MYSCP 1104
And I echoscu it like this.

Code: Select all

echoscu -d -aet MYSCU -aec CALLEDSCP <host> <port>
storescp acks the association request with this message.

Code: Select all

D: ====================== BEGIN A-ASSOCIATE-AC =====================
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:    1.2.276.0.7230010.3.0.3.6.0
D: Their Implementation Version Name: OFFIS_DCMTK_360
D: Application Context Name:    1.2.840.10008.3.1.1.1
D: Calling Application Name:    MYSCU
D: Called Application Name:     CALLEDSCP
D: Responding Application Name: MYSCP
D: Our Max PDU Receive Size:    16384
D: Their Max PDU Receive Size:  16384
D: Presentation Contexts:
D:   Context ID:        1 (Accepted)
D:     Abstract Syntax: =VerificationSOPClass
D:     Proposed SCP/SCU Role: Default
D:     Accepted SCP/SCU Role: Default
D:     Accepted Transfer Syntax: =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-AC ======================
But, echoscu receives the ack like this ..

Code: Select all

D: ====================== BEGIN A-ASSOCIATE-AC =====================
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:    1.2.276.0.7230010.3.0.3.6.0
D: Their Implementation Version Name: OFFIS_DCMTK_360
D: Application Context Name:    1.2.840.10008.3.1.1.1
D: Calling Application Name:    MYSCU
D: Called Application Name:     CALLEDSCP
D: Responding Application Name: CALLEDSCP
D: Our Max PDU Receive Size:    16384
D: Their Max PDU Receive Size:  16384
D: Presentation Contexts:
D:   Context ID:        1 (Accepted)
D:     Abstract Syntax: =VerificationSOPClass
D:     Proposed SCP/SCU Role: Default
D:     Accepted SCP/SCU Role: Default
D:     Accepted Transfer Syntax: =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-AC ======================
My confusion is with the Responding Application Name. The responding AE is "MYSCP", but echoscu shows it as "CALLEDSCP" instead (which doesn't actually exist).

J. Riesmeier
DCMTK Developer
Posts: 2503
Joined: Tue, 2011-05-03, 14:38
Location: Oldenburg, Germany
Contact:

Re: echoscu Responding Application Name confusion

#2 Post by J. Riesmeier »

Thank you for the report. This seems to be related to the following issue: http://support.dcmtk.org/redmine/issues/375

robertsdavidb
Posts: 17
Joined: Thu, 2012-09-27, 09:12

Re: echoscu Responding Application Name confusion

#3 Post by robertsdavidb »

Thanks for the quick reply.

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 1 guest