Skip to main content
Version: 4.3.0

Troubleshooting Checklists

Checklist for Contacting b+s Support in Case of a Unexpected System Behavior​

  • Description of the impact
  • Detailed scenario description
  • Error messages/ print screens
  • Version information of all involved components
  • Configuration files of all involved components
  • Example of an occurrence:
  • Cisco CCE agent ID
    • Device extension
    • Timestamp
  • Log files of all involved components that cover the occurrence

Checklist for Contacting b+s Support in Case of a Component Crash​

  • Description of the impact
  • Detailed scenario description
  • Error messages/ print screens
  • Version information of all involved components
  • Configuration files of all involved components
  • Example of an occurrence:
    • Cisco CCE agent ID
    • Device extension
    • Timestamp
  • Log files of all involved components that cover the occurrence
  • Minidump file (*.mdmp) of the crashed component
  • All binaries (executables, dynamic linked libraries etc.) and symbol files (*.pdb) of the crashed component
Attention

For unexpected system behavior as well as for component crashs, always provide logs of the b+s Harmony Agent Adapter component. If you encounter a media related issue, also include logs from b+s Harmony Routing Adapter. Ensure that the correct trace masks are set for troubleshooting.

Last updated on