Normally in DICOM, the requester of an association becomes the SCU, and the acceptor becomes the SCP, but there are some situations (notably Storage Commitment), where this relationship needs to be reversed (or it is possible for both applications to adopt both roles).  In DicomObjects, this is achieved using these properties, and is only possible (for outgoing operations) using an association based on an explicit DicomConnection.
To propose reverse role negotiation, DicomContext items must be created explicitly, and the context’s RequestorSCURole (default true) should be set to false, and the RequestorSCPRole (default false) should be set to true.

When accepting associations, DicomObjects’ default action is to accept whatever roles are proposed by the requestor, but this may be over-ridden in the AssociationRequest event by modifying these properties of any of the proposed contexts.
Once an association is established, these properties become read-only, but still reflect the arrangement negotiated.
Please note that these properties are shared between all contexts with the same Abstract Syntax (SOP class), so changing one will change the value for any other matching contexts.

DicomContext Object  | DicomContext Members