Page History

...

If the other party is connected and registered then escalate(DRAFT) User can't call - professional to the second level.

We can receive an escalation request either for a User's remote party configuration check or for a PrivateServer status check.

In the former case we need we have to understand if check the User's account has been created remote party activities on the related server. If it's, then we assure it's registered as well and (most important) we must check if his/hers virtual number has a similar entry assigned to another user: is the user duplicated? If all this checks pass fine, then we can only escalateserver in order to discover some conflict, such as a  virtual number duplication and eventually try to solve the conflicts.

In the latter case we  we need to first perform a Server services' check.  If the Services pass the tests, than we can focus on the Check Network Status, to understand if some communication issue are causing the Incident. If nothing arise, then we go for a deeper look using the client logs and, at last, we escalateperform some tests on the PrivateServer status: Network and PSAM 3.3 Check Server Services.

If all of the above are fine, the final possibility of a bug in the client become feasible, thus we check the client logs and then we escalate to the third level.