sync: auto-sync from GURU-5070 at 2026-06-22 09:44:14

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-22 09:44:14

.claude/memory/reference_packetdial_oit_netsapiens.md

@@ -0,0 +1,27 @@
+---
+name: reference_packetdial_oit_netsapiens
+description: VoIP vendor stack — PacketDial = ACG's VoIP department/brand; runs on NetSapiens (the PBX platform) supplied by OIT/OITVOIP (white-label wholesaler). YMCS = Yealink device mgmt.
+metadata:
+  type: reference
+---
+
+ACG's VoIP vendor stack, top to bottom (don't conflate these):
+- **PacketDial** = ACG's own **VoIP department / customer-facing brand**. `pbx.packetdial.com` is
+  the ACG-branded host. The `packetdial` skill is ACG's VoIP-management tool — keep it named
+  `packetdial` (ACG's brand) even though it speaks the NetSapiens API.
+- **NetSapiens** = the underlying **PBX/UCaaS software platform** (open API v2, v44.4.10). What the
+  skill actually talks to.
+- **OIT / OITVOIP** = the **white-label wholesale provider** that runs NetSapiens and resells it to
+  MSPs; ACG buys VoIP wholesale from OIT. `api.ucaasnetwork.com` is the OIT/NetSapiens host (same
+  platform as `pbx.packetdial.com`, different white-label hostname). Reseller territory
+  `91912.service` is ACG's account on OIT's platform; the reseller API key is vaulted at
+  `msp-tools/oitvoip.sops.yaml` (key-id `nsr_hSGUB5Wo`).
+- **YMCS (Yealink Management Cloud Service)** = separate Yealink **device-management** cloud for the
+  physical phones (`us-api.ymcs.yealink.com`); pairs with the PBX (phones register to
+  pbx.packetdial.com). API creds `services/yealink-ymcs.sops.yaml`; portal login
+  `infrastructure/voip-phones.sops.yaml`.
+
+One line: customer-facing brand = **PacketDial (ACG)**; platform = **NetSapiens**; wholesaler =
+**OIT/OITVOIP**; phone device-mgmt = **YMCS (Yealink)**.
+
+Related: [[reference_resource_map]]