Check the “Inbound Association History”

  • Confirm the presence of an entry for the selected modality
  • If there is no entry for the selected modality, the connection request is not getting to Compass
  • A networking or configuration issue is the most likely cause, often resolved if the following is done:
    • Check the firewall settings
    • Check the IP address and port to which the modality is sending
    • Confirm these settings in Compass
    • Verify on the Compass main screen that “DICOM Input” is running

Look for a non-Accepted entry

  • An entry in the “Inbound Association History” shows a result other than “Accepted”
  • Match the entry in the Result column with one of the following results:
    • “Bad Calling Title”: the modality’s AE title is invalid
      • Check the Source AE title on the Source tab
      • Verify that the “Source Enabled” checkbox is checked
    • “Bad Called Title”: one of the Compass AE titles is invalid
      • Check the Compass AE title on the Source tab
      • Verify that the “Source Enabled” checkbox is checked
    • “No Requested Contexts Accepted”: no context ID (combination of image type and transfer syntax) was accepted
      • Check the Compass list of supported SOP classes on the System tab
      • Check the list of enabled transfer syntaxes on the Source tab
    • “Max Concurrent Associations for Source Exceeded”: too many concurrent connections were attempted
      • Check the “Max Simultaneous” checkbox on the Source tab

Check filters on the Source

  • Check filters specified on the Source
  • Verify that there is not a filter that tries to modify a tag that is missing in the C-Echo from the Source
    • For example, if a filter that attempt to modify the Accession Number tag, but a preliminary C-Echo from the Source does not contain an Accession Number, the connection will be rejected
    • Verify that filters that attempt to modify a tag check first for the existence of that tag