- Shipped
- September 6, 2026 at 8:10 PM UTC
- Author
- Kamo
- Commit
- 2c862c6
Telnyx sells SIP trunking, DIDs and messaging, and an organization can buy those halves independently. The case this is for: DIDs and texts bought from Telnyx, with the calls answered by the customer's own FreePBX. Collapsing it into one entry would force those to be the same decision, so TELNYX is appended to both VoipProviderType and BulkTextProviderType. Both enums are EnumType.ORDINAL, so both appends are at the end. The bulk-text one had that property documented in its javadoc and enforced by nothing; it now has the same ordinal test the phone enum has, asserted where somebody adding a provider is already being made to stop and think. Telnyx bills THIRD_PARTY: the org holds its own Telnyx account and pays Telnyx per minute and per message, so what Kamo bills for is the integration. An unassigned Telnyx line costs nothing, which is right — a telephony credential with no member behind it is one we are doing nothing with. No version bump. 17 services pin 1.6.0 and every service Dockerfile rebuilds this library from main, so a bump would leave all of them resolving a version that exists nowhere. Recent additions to types/ shipped the same way.