Improve MPPS forwarding capacities

[albertosaez]

We're trying to reuse the MPPS our central storage is receiving, by re-resending them to a dose managmente system.

But we're facing two limitations with the current capacities of dcm4chee-arc :

• No capacity to filter which MPPS will be forwarded and which no. The solution to use different receiving aetitles is not possible as we will have to reconfigure all of the modalities.

• No whay to change the "sending aetitltle" of the MPPS when forwarding, nor other customization like the ones are in the study exporter

Is there any plan to inlcude any of this capacities in the dcm4chee-arc ?
Meanwhile, ... could you suggest any other tool impromve management of the MPPS forwarding ?

Thanks,

Alberto.

[gunterze]

Opened #3219

Masquerading of the sending AET is already configurable by Network Extension attribute:

Name	Type	Description (LDAP Attribute)
Masquerade Calling AE Title(s)	string	AE Title used for initiating network associations, masquerading the actual AE Title for this Network AE - optional prefix [<Called AE Title>] limits the masquerading to association to a particular AE Title (dcmMasqueradeCallingAETitle)

Attribute Coercion is currently only supported on receive of N-CREATE/N-SET requests, which is also reflected in outgoing N-CREATE/N-SET requests. But you can't configure Attribute Coercions only applied on outgoing N-CREATE/N-SET requests dependent on MPPS attributes or the MPPS destination.