Statuses and forwarding error codes (mpbx-api, mpbx-forwarding)
Raised when a user edits their statuses and forwarding rules or asks for a preview (W3-TEL-04). Messages name fields and ids; they never contain call content. Guide: Statuses and forwarding.
| Code | Kind | Meaning | What to do |
|---|---|---|---|
MPBX-FWD-SESSION-REQUIRED | permission_denied | Statuses and forwarding are changed from a signed-in session, not with an API key (a forward sends calls elsewhere, so a key does not change it, not even its owner's). | Sign in as the user. |
MPBX-FWD-NO-EXTENSION | not_found | The preview needs your extension and you have none. | Ask an administrator to give you an extension. |
MPBX-FWD-INVALID | invalid_argument | The status failed validation: a name that is empty, longer than 40 characters or has control characters; a ring timeout outside 5 to 300 seconds; two rules for the same caller class and condition; a number that is not digits (an external or mobile number is 3 to 20 digits with an optional leading +, an extension 1 to 16 digits); a rule that forwards to your own extension; a mobile number that is not a number; a temporary status with both or neither of duration_secs and until, shorter than a minute or longer than 30 days; a status schedule that maps no office-hours state to a status, or maps a status that is not yours. The answer lists each problem with its field. | Fix each listed field. |
MPBX-FWD-TARGET-UNAVAILABLE | invalid_argument | The target kind cannot be used yet: forwarding to voicemail is not available (the call engine cannot yet deposit a message for a call nobody answered). | Use an extension, an external number, the mobile number or busy. |
MPBX-FWD-UNKNOWN-EXTENSION | invalid_argument | A rule forwards to an extension that does not exist (or is disabled) in your company. | Pick an existing extension. |
MPBX-FWD-STATUS-NOT-FOUND | not_found | No such status of yours. Another user's status, or another company's, is the same as a missing one. | Check the id. |
MPBX-FWD-NAME-TAKEN | conflict | Another status of yours has this name (case-insensitively). | Choose another name. |
MPBX-FWD-TOO-MANY | conflict | You already have 20 statuses. | Delete one first. |
MPBX-FWD-BUILT-IN | conflict | A built-in status (Available, Away, Do not disturb, Lunch, Business trip) cannot be deleted. | Rename it or change its rules instead. |
MPBX-FWD-STATUS-CURRENT | conflict | The current status cannot be deleted. | Switch to another status first. |
MPBX-FWD-UNKNOWN-SCHEDULE | invalid_argument | A status schedule names an office-hours schedule the company does not have (W6-TEL-01). | Pick one of available_schedules from GET /me/status/schedule, or leave schedule_id out to follow the schedule that serves you. |
MPBX-FWD-SCHEDULE-NOT-FOUND | not_found | You have no status schedule to remove (W6-TEL-01). | Nothing to do. |
What a caller hears
These are not API errors: they are the SIP answers of a call to an extension whose status forwards it.
| Answer | When |
|---|---|
486 Busy Here | The status forwards to busy (Do not disturb), or the extension is busy and no busy rule applies. |
480 Temporarily Unavailable | No device is registered and no not_registered rule applies, or the ring timeout passed with no no_answer rule, or a forward cannot be carried out (the dial plan refused the number for the forwarding user, no trunk is reachable, the mobile number is missing, forwarding to voicemail). |
482 Loop Detected | The forwards came back to an extension already visited, or the chain is longer than five. |