...
This is one of the most claimed incidents to occur. This Incident troubleshooting must be confronted only if the incident definition and description hasn't pointed out any operational requirements violation. "User can't call" cause is equally divided into client/server misconfigurations and connection issues.
| Warning | ||
|---|---|---|
| ||
Please keep in mind that a call can fail due a reason that doesn't depends on the client Please note that this troubleshooting workflow only applies if no specific error messages are written by the PrivateGSM (e.g. License problems, user offline or doesn't exist, etc...). In these cases an error message should appear on the client screen, so check any message before to proceed to troubleshoot an incident of this kind. See TODO: insert section |
User can't call
First Level
...
If the other party is connected and registered then escalate to the second level.Anchor
Second Level
We can receive an escalation request either for a User's remote party configuration check or for a PrivateServer status check.
...