communication-problems with efilm/iq-view and tcpsrv_e

Questions regarding the DCMPRINT library, a DCMTK add-on that implements a DICOM Print Management SCP and SCU

Moderator: Moderator Team

Post Reply
Message
Author
mlehr
Posts: 4
Joined: Wed, 2007-08-22, 16:17

communication-problems with efilm/iq-view and tcpsrv_e

#1 Post by mlehr » Fri, 2007-08-24, 09:33

Hello all,

I am currently evaluating the tcpsrv_e programm (the commercial DCMPRINT), running on SuSe Linux.
If the programm would work, our customer would by it.

I can print from tcpprt_e on a client-pc to tcpsrv-e without any problems.
Also the dcmprscu can print.

But efilm or iq-view are not able to communicate with tcpsrv_e.
efilm says: "There where problems initializing the print session"

Perhaps someone can help.

Regards
Martin

This is the log of tcpsrv_e:
[ASSOCIATION NEGOTIATION BEGIN]
Calling AE Title : EFILM
Called AE Title : DCMPRINT
Responding AE Title : DCMPRINT
Application Context : StandardApplicationContext
Presentation Context 89 : BasicGrayscalePrintManagementMetaSOPClass
Transfer Syntax : LittleEndianImplicit
Accepted, Transfer Syntax: LittleEndianImplicit
ASSOCIATION ACKNOWLEDGED
[ASSOCIATION NEGOTIATION END]

[SENDING MESSAGE]
[BEGIN MESSAGE DUMP]
Message type : N-EVENT-REPORT request
Message ID : 2
Affected SOP class UID : PrinterSOPClass
Affected SOP instc UID : 1.2.840.10008.5.1.1.17
DICOM data stream : not present
Event Type ID : 1
[END MESSAGE DUMP]
[DATASET DUMP BEGIN]
[DATASET DUMP ENDED]
DIMSE Command To Send:

# Dicom-Data-Set
# Used TransferSyntax: Unknown Transfer Syntax
(0000,0000) UL 0 # 4, 1 CommandGroupLength
(0000,0002) UI =PrinterSOPClass # 22, 1 AffectedSOPClassUID
(0000,0100) US 256 # 2, 1 CommandField
(0000,0110) US 2 # 2, 1 MessageID
(0000,0800) US 257 # 2, 1 DataSetType
(0000,1000) UI =PrinterSOPInstance # 22, 1 AffectedSOPInstanceUID
(0000,1002) US 1 # 2, 1 EventTypeID
DIMSE sendDcmDataset: sending 112 bytes
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (72 bytes), presID=89
DIMSE Command Received:

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(0000,0002) UI =BasicFilmSessionSOPClass # 22, 1 AffectedSOPClassUID
(0000,0100) US 320 # 2, 1 CommandField
(0000,0110) US 11 # 2, 1 MessageID
(0000,0800) US 258 # 2, 1 DataSetType

[RECEIVING MESSAGE]
[BEGIN MESSAGE DUMP]
Message type : N-CREATE request
Message ID : 11
Affected SOP class UID : BasicFilmSessionSOPClass
Affected SOP instc UID : not present
DICOM data stream : present
[END MESSAGE DUMP]
DIMSE receiveFileData: 48 bytes read (last: YES)
[DATASET DUMP BEGIN]

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(2000,0000) UL 36 # 4, 1 FilmSessionGroupLength
(2000,0010) IS [1] # 2, 1 NumberOfCopies
(2000,0020) CS [MED] # 4, 1 PrintPriority
(2000,0030) CS [PAPER] # 6, 1 MediumType
[DATASET DUMP ENDED]

[SENDING MESSAGE WITH DATASET]
[BEGIN MESSAGE DUMP]
Message type : N-CREATE response
Message ID responded : 11
Affected SOP class UID : BasicFilmSessionSOPClass
Affected SOP instc UID : 1.2.276.0.7230010.3.1.4.2831165478.14544.1187943188.17
DICOM data stream : present
Status : 0x0
[END MESSAGE DUMP]
[DATASET DUMP BEGIN]

# Dicom-Data-Set
# Used TransferSyntax: Unknown Transfer Syntax
(2000,0010) IS [1] # 2, 1 NumberOfCopies
(2000,0020) CS [MED] # 4, 1 PrintPriority
(2000,0030) CS [PAPER] # 6, 1 MediumType
(2000,0040) CS [MAGAZINE] # 8, 1 FilmDestination
(2000,0050) LO [Remote DICOM Printserver Session #4] # 36, 1 FilmSessionLabel
(2100,0160) SH (no value available) # 0, 0 OwnerID
[DATASET DUMP ENDED]
DIMSE Command To Send:

# Dicom-Data-Set
# Used TransferSyntax: Unknown Transfer Syntax
(0000,0000) UL 0 # 4, 1 CommandGroupLength
(0000,0002) UI =BasicFilmSessionSOPClass # 22, 1 AffectedSOPClassUID
(0000,0100) US 33088 # 2, 1 CommandField
(0000,0120) US 11 # 2, 1 MessageIDBeingRespondedTo
(0000,0800) US 1 # 2, 1 DataSetType
(0000,0900) US 0 # 2, 1 Status
(0000,1000) UI [1.2.276.0.7230010.3.1.4.2831165478.14544.1187943188.17] # 54, 1 AffectedSOPInstanceUID
DIMSE sendDcmDataset: sending 144 bytes
DIMSE sendDcmDataset: sending 104 bytes
DIMSE receiveCommand
Association release requested by peer.

Marco Eichelberg
OFFIS DICOM Team
OFFIS DICOM Team
Posts: 1225
Joined: Tue, 2004-11-02, 17:22
Location: Oldenburg, Germany
Contact:

#2 Post by Marco Eichelberg » Mon, 2007-08-27, 08:15

My first guess would be that the print client does not implement Event Reports correctly, which is not unusual unfortunately. In the configuration file for the DCMPRINT print server, tcpsrv.cfg, there is a section named [Compatibility] with various settings that enable work-arounds for problems with certain Print SCUs. In this case, I would change the setting "SuppressEventReports" to YES:

Code: Select all

; Print SCP: Never send N-EVENT-REPORT messages (required for stupid SCUs)
; Optional setting, default is NO
SuppressEventReports = YES
Save the file, restart the print server, and retry.

mlehr
Posts: 4
Joined: Wed, 2007-08-22, 16:17

#3 Post by mlehr » Tue, 2007-09-11, 15:12

Yes, this was the solution!

Thank you very much!

Regards, Martin

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest