Hello,
I've been working with storescp using the provided storescp.cfg file trying to negotiate transfer syntaxes. I have read asconfig.txt but I'm afraid I'm too dense to really understand it in regards to what I'm trying to do.
What I would like to do is that on a per modality basis, negotiate a transfer syntax that I prefer and if the preferred transfer syntax is unavailable, fall back to something else. As an example, for a CT I would like to receive it in 'JPEGLossless:Non-hierarchical-1stOrderPrediction', if the sender isn't capable of this, fall back to 'LocalEndianExplicit.'
If you could shed some light on how I could do this, or even an example, I would greatly appreciate it.
storescp and negotiating transfer syntaxes
Moderator: Moderator Team
-
- DCMTK Developer
- Posts: 2505
- Joined: Tue, 2011-05-03, 14:38
- Location: Oldenburg, Germany
- Contact:
As far as I remember, the order of transfer syntaxes defined for a certain presentation context is significant. In other words, the storescp (when used with a configuration file) prefers the first transfer syntax of a presentation context that matches the SCU's proposal.
Please note that I haven't tested the above configuration.
Code: Select all
[[TransferSyntaxes]]
[Uncompressed]
TransferSyntax1 = LocalEndianExplicit
TransferSyntax2 = OppositeEndianExplicit
TransferSyntax3 = LittleEndianImplicit
[PreferredTransferSyntaxes]
# the first one is preferred (if offered by the SCU)
TransferSyntax1 = JPEGLossless:Non-hierarchical-1stOrderPrediction
TransferSyntax2 = LocalEndianExplicit
TransferSyntax3 = LittleEndianImplicit
[[PresentationContexts]]
[MyStorageSCP]
PresentationContext1 = VerificationSOPClass\Uncompressed
PresentationContext2 = CTImageStorage\PreferredTransferSyntaxes
[[Profiles]]
[MyProfile]
PresentationContexts = MyStorageSCP
Who is online
Users browsing this forum: Ahrefs [Bot], Bing [Bot] and 1 guest