Admin IP allow-list error codes (mpbx-api-ops)
Raised by the allow-list check in front of the API and by GET/PUT /api/v1/system/admin-ip-allowlist
(W7-PLAT-01b; SEC-NET-003). Guide: Admin IP allow-list.
| Code | Kind | Meaning | What to do |
|---|---|---|---|
MPBX-NET-ADMIN-IP-DENIED | forbidden (403) | The request came from an address that is not on the admin allow-list. It is refused before authentication, so the answer says nothing about the credential. | Connect from an allowed address (or through the VPN), or ask the install owner to add the address. |
MPBX-NET-ALLOWLIST-LOCKOUT | invalid_argument (400) | The list you are saving does not contain the address you are connecting from, so it would lock you out. | Add your own address (the console has a button for it) and save again. |
MPBX-NET-ALLOWLIST-INVALID | invalid_argument (400) | An entry is not an IPv4 or IPv6 address or CIDR block, the list has more than 64 entries, the scope is not system or api, or the list is enabled but empty. | Fix the named field. |
Storage quota
Storage usage and quotas (GET /api/v1/system/storage/companies,
PUT /api/v1/system/storage/companies/{company_id}/quota) use the common codes: an unknown company
is MPBX-NOT-FOUND, a quota outside 1 to 2^60 bytes or a warn percent outside 1 to 99 is
MPBX-INVALID-ARGUMENT with the field named, and a stale If-Match is 412
(MPBX-PRECONDITION-FAILED). Guide: Storage quotas.
SIP edge security (/api/v1/system/sip-edge/..., FU-W2SIP03-L1)
| Code | Kind | Meaning | What to do |
|---|---|---|---|
MPBX-NET-SIP-LIST-INVALID | invalid_argument (400) | An entry of the SIP allow or deny list is not an IPv4 or IPv6 address or CIDR block, or a list has more than 256 entries. | Fix the named field. |
MPBX-NET-SIP-BAN-INVALID | invalid_argument (400) | The ban names no IPv4 or IPv6 address (networks belong on the deny list), or its length is not 60 to 2592000 seconds. | Fix the named field. |
MPBX-NET-SIP-BAN-ALLOWLISTED | invalid_argument (400) | The address is on the SIP edge allow list, which is never banned. | Take it off the allow list first, or put it on the deny list. |
Geo blocking (W10-OBS-01; SEC-NET-006)
Raised by the geo-blocking check in front of the API and by GET/PUT /api/v1/system/geo-blocking.
Guide: Geo blocking.
| Code | Kind | Meaning | What to do |
|---|---|---|---|
MPBX-NET-GEO-BLOCKED | forbidden (403) | The request came from a country the geo-blocking rule refuses. It is refused before authentication. | Connect from an allowed country (or through the VPN), or ask the install owner to change the rule. |
MPBX-NET-GEO-LOCKOUT | invalid_argument (400) | The rule you are saving would block the address you are connecting from. | Take your own country out of the deny list (or put it in the allow list) and save again. |
MPBX-NET-GEO-INVALID | invalid_argument (400) | The mode is not off, deny or allow, a country is not a two-letter code, the scope is not system or api, there are more than 300 countries, or an allow rule lists none. | Fix the named field. |
MPBX-NET-GEO-NO-DATABASE | invalid_argument (400) | A rule was saved while no IP-to-country table is loaded, so it could not block anything. | Set [geo] database in the configuration file and restart. |