Document group-owned personal number assignment

Update the dashboard's own Personal Numbers card description and the
Anveo Direct setup guide to mention assigning a DID to a group instead
of a single extension.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ho9mZgAkVpdz7S5wJkg8Nf
This commit is contained in:
Claude
2026-07-24 03:03:55 +00:00
parent dd3ea131ac
commit c893751859
2 changed files with 9 additions and 1 deletions
+8
View File
@@ -159,6 +159,14 @@ In the Security Dashboard's PSTN Trunk tab:
DID instead of the shared trunk DID. Enter the DID as **10 digits, no
leading 1** (matches the same convention as the trunk DID above) —
the dashboard's own input validates against exactly that format.
You can assign the DID to a **group** instead of a single extension —
pick `Group: <name>` in the owner dropdown (create the group first
under Groups if it doesn't exist yet). Every current member whose own
tier/approved-numbers authorize the caller rings, checked fresh on
every call, so membership changes apply immediately with no reinstall.
A group has no single extension to hang an outbound Caller-ID override
on, so the Caller-ID-override part above only applies to
single-extension assignments.
## 7. Test
+1 -1
View File
@@ -1625,7 +1625,7 @@ INDEX_HTML = """<!doctype html>
<div class="card">
<h3 style="margin-top:0">Personal numbers</h3>
<p class="muted">
Multiple DIDs can share this one trunk. Assigning a DID to an extension routes inbound calls to that DID straight to its owner (still gated by the owner's own tier/approved-numbers above — no ring-group fallback), and makes that extension's outbound calls show this DID as Caller-ID instead of the shared trunk DID. The shared DID/ring-group keeps working regardless.
Multiple DIDs can share this one trunk. Assigning a DID to an extension routes inbound calls to that DID straight to its owner (still gated by the owner's own tier/approved-numbers above — no ring-group fallback), and makes that extension's outbound calls show this DID as Caller-ID instead of the shared trunk DID. You can also assign a DID to a <b>group</b> instead of a single extension — every current member whose own tier/approved-numbers authorize the caller rings (checked fresh on every call, so membership changes apply immediately); a group has no single extension to hang the outbound Caller-ID override on, so that part only applies to single-extension assignments. The shared DID/ring-group keeps working regardless.
</p>
<div class="row">
<input type="text" id="pd-did" placeholder="DID, e.g. 5551234567 (10 digits, no leading 1)" style="width:12rem">