Door phone error codes (mpbx-api-telephony)
Returned by /api/v1/door-phones/... and /api/v1/me/door-phones. Guide:
Door phones.
| Code | HTTP | Meaning | What to do |
|---|---|---|---|
MPBX-DOOR-INVALID | 400 | A field is not valid: no such device or schedule in the company, a relay code that is not DTMF, a URL that is not http/https or carries credentials, a dtmf method without a code or an http method without a URL, more than 100 doors. | Fix the field named in errors. |
MPBX-DOOR-NOT-FOUND | 404 | No such door phone in this company. | Check the id (GET /door-phones). |
MPBX-DOOR-DUPLICATE | 409 | The device is a door phone already. | Change that door instead (PUT /door-phones/{id}). |
MPBX-DOOR-NOT-IN-CALL | 403 | You are not in a call with the door (ringing or answered), and you are not an administrator with devices:write; or the door opens by DTMF and there is no call to press it in. | Answer the door's call first. |
MPBX-DOOR-OUTSIDE-HOURS | 403 | Outside the open hours of the door's schedule only an administrator may open it. | Ask an administrator, or change the door's open_schedule_id. |
MPBX-DOOR-NOT-SUPPORTED | 409 | The door has no open action (open_method: none), or no still image (snapshot_url). | Set it up in PUT /door-phones/{id}. |
MPBX-DOOR-UNREACHABLE | 502 | The door did not answer, answered with an error or not with an image, did not take the relay code, or the outbound guard refused its address (private addresses need the operator's MPBX_DOOR_PHONE_ALLOW_ADDRS). | Check the door's URL, credentials and network; see the guide. |