Give a member a RingCentral JWT and an extension its own number

Featurekamo-shared-library
Shipped
August 26, 2026 at 1:01 AM UTC
Author
Kamo
Commit
b4f3358

Two columns, both nullable so nothing is backfilled and no existing row changes meaning. **************** holds a member's own RingCentral JWT. RingCentral only provisions a SIP identity for the extension that owns the token presented, so a softphone still needs a per-person credential; the JWT is the long-lived thing that mints it, in the place the rotating refresh token used to sit. Teams keeps using the refresh token, so the table now holds whichever long-lived credential its provider issues. phone_extension.direct_number holds the extension's own inbound DID. Without it a member's outbound caller id could only ever be the phone server's main number, so "assign this member their own number" had nowhere to be recorded. Extensions that have no direct line, and providers that model inbound routing separately from extensions, leave it null and fall back exactly as before. **************** is marked retired rather than removed — ids there are persisted and the enum is append-only. Nothing reads it any more: a RingCentral phone server's credentials are issued inside the customer's own account, so they live on the instance that uses them.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing