NOTE: If you use SightCall in an integrated environment (custom integration, Salesforce, Zendesk, etc.), then refer to this article for the steps to gather Coredump log in an integrated environment.
The following steps explain how to gather a Coredump log:
Note: These steps should be performed soon after experiencing the issue and the call has ended (hang up the call if it's not ended).
- Open a browser tab or window and connect to the SightCall console with your credentials.
If you are having issues connecting to SightCall console, please wait a few minutes before moving to the next step so that there is enough log data to analyze.
- Put your mouse pointer over the Person / Human icon on the top-left corner of the console (next to your login ID) and press C key on the keyboard. The entire top bar will appear transparent for a moment and will come back to normal afterwards.
- A Coredump log has been automatically generated and can be accessed on a local directory described in this article. It's usually either C:\Users\xxxxx\AppData\Roaming\SightCall\ or
- Send the Coredump log file to your Support Request with a detailed explanation of the issue.
Alternatively, you can also gather Coredump log with the following steps:
- In the upper right corner, select the gear icon to access the settings.
- Select Coredump.
- You should see a popup message: Logs have been copied to clipboard.
At this point, the log file is in your computer cache (clipboard memory) as if you copied a text (Ctrl+C) from some document.
- Open a Text Editor application such as Notepad, TextEdit, etc., and paste (Ctrl+V) the content of the clipboard.
- Save the content as text (.TXT) file - DON'T SAVE IT AS .RTF FILE and attach it to your Support Request with a detailed explanation of the issue.