![]() The host server (obtained either as the result of the DNS lookup, or by using the domain part of the dialed alias) could not be found.Ĭonference host ended the conference with a DTMF commandĪ Host participant ended the call using a DTMF command. If this issue persists, you may wish to send a snapshot to your Pexip authorized support representative. Pexip Infinity received an Unexpected Response (503) when trying to place the call. See Participants cannot join a conference due to insufficient capacity.Ī Host participant attempted to transfer another participant from the current meeting to another meeting, but failed.Ĭall failed - please contact your administrator The system you are trying to reach is over capacity. ![]() Note that if the client encounters a node in maintenance mode while performing an SRV lookup, it will not attempt to contact any other nodes. The Conferencing Node is in maintenance mode. ![]() The system you are trying to reach is temporarily unavailable. The PIN that was entered did not match the Host (or Guest, if configured) PIN.Īll Proxying Edge Nodes in the location are out of capacity. The PIN you entered is invalid - please try again. To assist administrators with troubleshooting, the associated admin-facing message (which appears in the admin log, and when viewing historical information about a participant) is also given.įor help with general issues that may occur when using Connect app clients within your deployment, see Connect apps. The table below lists the specific messages that may be presented to Connect app users, along with their meaning and suggested resolution (where appropriate). Troubleshooting Connect app error messages
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |