The ACSE Implementation name field now derives from acseItem (used for UIDs), but it isn't an UID.
Issue #291
closed
The ACSE Implementation name field now derives from acseItem (used for UIDs), but it isn't an UID. This causes the ACSE negotiation to fails when the implementation name does not contain any number.
Also, non numeric chars are removed from the implementation name.
Comments (4)
-
reporter
-
reporter
Addresses
#291. Updated changes log→ <<cset 240371d1e6603d251324938e7cd23e7f1f24bfe7>>
-
reporter
- changed status to resolved
Resolves
#291(The ACSE Implementation name field now derives from acseItem used for UIDs, but it isn't an UID) as per SOP FIXBUG/2→ <<cset 52ff9c0cf9433e8beb0f1ee4d3fce5cdaad64c27>>
-
reporter
- changed status to closed
Closed in 4.5.6.1
- Log in to comment
Addresses
#291. Modified ACSE implementation name from UID to text, changed log level in tests to check the value sent to DCMTK→ <<cset c7963c9f690cf0030efa6aa70c8f096703751f03>>