KamoCRM

Refuse a phone extension past the organization's licenses

FeatureVOIPService
Shipped
October 23, 2026 at 12:10 AM UTC
Author
Kamo
Commit
65a11f0

Owner rule 2026-10-22: per-user add-ons bill the licenses purchased; how many extensions may be in use is limited only by them. Before an extension is put into use, BillingService's **************** is asked (X-Internal-Auth); a refusal is a 409 carrying its plain-language sentence (LicenseCapAdvice), e.g. "All 10 of your 3rd-party phone licenses are in use. Add licenses in Billing to assign another extension." Enforced, before anything is written: - PUT /api/voip/member/{id}/config (member phone settings), naming the extension the member holds now so a move on a 3rd-party system is free - POST **************** (new extension; KamoPBX counts every active one, 3rd-party only an assigned one) - PUT **************** when the result is ACTIVE - AI voice line provisioning (NOT_READY / LICENSE_LIMIT) An extension already counted is never refused, nothing existing is unassigned, and a BillingService outage fails OPEN with a warning.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing