- Shipped
- August 30, 2026 at 1:03 AM UTC
- Author
- Kamo
- Commit
- c3de663
Starting a text threw IllegalStateException when neither the member nor the instance had an outbound number, which Spring turned into a 500 with a stack trace. Every client then showed its own blanket failure — the phone said "Could not start conversation. Check the number and try again", blaming the number the member had just typed for a gap in their OWN account. A member told that retypes the number forever and concludes texting is broken. Both unprovisioned branches answer 409 with a machine code and a sentence that names what is missing and who can fix it: no phone service for the organization, or no number assigned to this member. A PBX extension is not one — it places calls but has no number a text can come from — so a member with a working softphone can still have nothing to text from, which is exactly the case that produced the report. Seen on a live org: both provider instances carry an empty main_phone_number and the member's config an empty from_phone_number beside extension 8000.