Overview
Troubleshooting
- Define history and scope
- Was the supervisor able to receive calls yesterday?
- Any prior tickets or recent changes to the account?
- Are they the only supervisor to be affected?
- Data Collection and Troubleshooting
- Define the situation
- A call is offered to the XCS Supervisor, they pick up – what happens?
- How do they pick up? On the phone? On the XCS app?
- A call is offered to the XCS Supervisor, they pick up – what happens?
- Does a call not get offered to the supervisor?
- Define the situation
- What is the endpoint?
- Check the endpoint in OCOM – any errors?
- Can you call the endpoint directly without involving XCS?
- Verify the endpoint is working as expected independent of XCS
- Which XCS Supervisor is the end user using?
- If a 64-bit client, the user cannot use an Internal VoIP phone, recommend switching over to a 32-bit client
- Make sure the endpoint is selected correctly in the XCS Supervisor client
- Look in the lower right corner of the app, next to the current time
- Have the supervisor go into a non-Ready state (Back Office, Offline, Handle Outgoing, Break) and click on the endpoint in the lower right-hand corner of the Supervisor app to change the endpoint
- Look in the lower right corner of the app, next to the current time
- If it says “No Phone Connected”, attempt to change the endpoint to the correct endpoint
- HPBX: endpoints such as physical desk phones, UC-One
- Use Broadsoft user ID
- Private: endpoints including cellphones (similar to Remote Office)
- Internal VoIP phone: XCS as an endpoint (answer calls on the PC)
- HPBX: endpoints such as physical desk phones, UC-One
- Obtain XCS Supervisor client logs
- Can this be replicated?
- If so, how?
- (optional) Obtain XCS credentials or permission to reset credentials to test
- Escalation to Support Center
- Note the history and scope
- Note call examples if any
- Attach XCS logs
- Note any testing done
- Note if the behavior can be replicated
- Note any XCS creds obtained