V7 (VSEVEN HOTELS) — Master Info, Checklist & To-Dos¶

Status: Install in progress (cloud-side complete, on-prem pending Grandstream + BSNL meeting) Last touched: 2026-05-03 Owner (CSM): Hari Prasath

One-stop page for everything VSEVEN HOTELS — status board, open to-dos, all credentials, equipment, contacts, and notes. Edit via GitHub's pencil icon on this page (top-right) for one-click in-browser editing — no git knowledge needed.

Status board (at-a-glance)¶

Legend: ✅ done · ⚠️ partial / blocked · ❌ pending · ➖ n/a

Open to-dos¶

Pre Grandstream + BSNL meeting (gather these from hotel manager via WhatsApp)¶

• [ ] Get UCM6301 firmware version (Status → System Information screenshot)
• [ ] Get latest BSNL bill (account number + plan name)
• [ ] Get photo of DBC SaiNXT ONT bottom/back sticker (admin credentials)
• [ ] Get hotel manager + IT lead direct contact details (phone + email)
• [ ] Confirm whether *#21# shows any active call-forward on the BSNL line

During the Grandstream + BSNL meeting¶

• [ ] Resolve UCM trunk-to-trunk gating (Grandstream installer)
• [ ] Confirm BSNL service tier — analog FXS or SIP-over-Ethernet (BSNL engineer)
• [ ] If SIP-over-Ethernet: get plan upgrade quote + SIP credentials / IP whitelist policy
• [ ] Disable SIP ALG on GWN7002 router (likely needed)
• [ ] Live test: BSNL → cloud → ext 09 rings (full path)
• [ ] Live test: outbound call shows CID 04175295093

Post-meeting¶

• [ ] Update this page's status board with meeting outcomes
• [ ] If trunk-to-trunk fixed: enable BSNL-AstraDial inbound route on UCM, switch primary inbound away from CFA fallback
• [ ] Configure recording verification end-to-end
• [ ] Schedule customer demo
• [ ] Production handover sign-off

Tech-debt items (future, not blocking)¶

• [ ] Strip the credentials block from this doc once Bitwarden Teams (or similar) is set up
• [ ] Set hotel WAN as static IP (BSNL plan upgrade), required for cloud-direct SIP peering

Identity¶

Contacts¶

Carrier accounts¶

Network¶

Equipment¶

Device 1 — Grandstream UCM6301 (PBX)¶

Device 2 — Grandstream GWN7002 (Multi-WAN VPN router)¶

Device 3 — Grandstream GWN7802 managed switch ×2¶

Device 4 — DBC Technologies / SaiNXT GPON ONT (BSNL fiber CPE)¶

Device 5 — Grandstream GRP2636 IP phone (front desk, ext 09)¶

Device 6 — Other hotel IP phones (extensions on UCM)¶

Astradial-side configuration¶

DIDs / phone numbers¶

Extensions / users (cloud-side)¶

How BSNL delivers internet + voice (single fibre)¶

This site is a single-fibre GPON delivery: internet AND voice come down one fibre from the BSNL exchange, multiplexed at the optical layer. The DBC SaiNXT ONT splits them before handoff:

BSNL exchange
     │
     │ ONE optical fibre (internet + SIP voice multiplexed via GPON)
     ▼
DBC SaiNXT ONT  (192.168.1.1 — wall-mounted, white plastic box)
     │
     ├──→  Ethernet port → GWN7002 router → LAN/WiFi → internet ✅
     │
     └──→  RJ-11 FXS jack (analog phone signal)
           → copper → UCM6301 FXO port → "PSTN" trunk inside UCM
           The ONT does the SIP→analog conversion internally.
           Our equipment never sees the SIP.

So although the hotel's voice service is technically SIP at the carrier level, what we receive is plain analog. The conversion happens inside the ONT, behind a sealed configuration we can't see or touch.

The big question for the BSNL meeting: can BSNL flip the ONT into "voice over Ethernet" mode (sometimes called "voice VLAN passthrough" or "ONT bridge mode for voice") so that the SIP packets reach our UCM/cloud directly, bypassing the analog conversion? See v7-meeting-brief.md for the decision tree.

Architecture target (post-meeting)¶

        BSNL carrier
             │  (existing trunk, terminated at hotel)
             ▼
   ┌──────────────────────┐
   │  UCM6301 @ .60       │   on-prem bridge
   │  - BSNL FXO          │
   │  - AstradialCloud SIP trunk (registered to cloud)
   └──────────┬───────────┘
              │  SIP over internet
              ▼
   Astradial Cloud Asterisk (devsip.astradial.com:5080)
              │
              ├─ Inbound: BSNL → cloud → ext 09 GRP2636 / queue / IVR / AI bot
              └─ Outbound: cloud → UCM → BSNL FXO → recipient sees CID 04175295093

If BSNL approves SIP-over-Ethernet delivery on the line, this simplifies further (cloud peers directly with BSNL, UCM stays only for internal extensions).

Photos / files¶

• [ ] Rack — front: TBD
• [ ] Rack — back (port labels visible): TBD
• [ ] DBC SaiNXT ONT — front (LEDs): TBD
• [ ] DBC SaiNXT ONT — back/bottom (sticker with credentials): TBD
• [ ] BSNL fiber pigtail entry point: TBD
• [ ] BSNL bill (latest): TBD
• [ ] UCM6301 — back showing FXO/FXS port cabling: TBD

When sensitive photos arrive (sticker, bill), drop them in internal-docs/docs/customers/v7-photos/ (private repo, behind Cloudflare Access — same protection as this page).

Critical gotchas (learned the hard way)¶

Gotcha #1 — Auth username = peer name, not the user-friendly name¶

When creating an inbound trunk via the editor, the credentials dialog shows username: vseven_ucm (the friendly name you typed). But the cloud Asterisk's auth block is rendered with username = <peer name> (the long auto-generated org_moijhj2l_trunk1777732151626) for multi-tenant isolation. The remote PBX must register with the peer name, not the friendly username. Symptom of getting it wrong: REGISTER fails with No matching endpoint found. Burned ~30 min on initial install.

Gotcha #2 — Cloud listens on UDP/5080, not 5060¶

The editor's credentials dialog defaults the Port field to 5060 for inbound trunks (a UI bug — see Bug #2 below). The cloud's primary transport-udp is bound to 5080; 5060 is reserved for the WireGuard-bound Tata gateway. Symptom of getting it wrong: REGISTER goes to a port nothing's listening on, trunk stays Unregistered.

Bugs (known platform bugs from this install)¶

All four were fixed during the install. Linked to troubleshooting page entries:

1. Editor "Add Trunk" form was missing Password input — fixed in PR #96, Error 50
2. Editor POST /users dropped routing fields + missing PUT /users/:id/routing endpoint — fixed in PR #97, Error 51
3. Credentials dialog shows wrong username for inbound trunks — needs asterisk_peer_name not username. Filed as backlog item; not yet fixed.
4. sip_trunks.registration_status never updates — DB column stays unknown forever. Needs AMI listener writing back on registration events. Backlog.

Open bugs / blockers¶

• UCM trunk-to-trunk routing on FXO inbound → SIP outbound is being silently dropped. Pending Grandstream installer meeting. See v7-meeting-brief.md for diagnostic questions.
• BSNL service tier unconfirmed — analog vs SIP-over-Ethernet decision blocks the long-term architecture. Pending BSNL engineer meeting.

Related docs¶

• Meeting prep messages (Grandstream / BSNL / hotel manager outreach): v7-meeting-prep.md
• Meeting brief (full agenda + decision tree): v7-meeting-brief.md
• Discovery questionnaire (generic template): vendor-discovery-questionnaire.md

Change log¶

Newest at top. Keep entries terse. One bullet per material change.

• Site survey, Astradial cloud trunk created and registered, UCM SIP trunk to cloud configured + registered, inbound flow from FXO to cloud failing on UCM trunk-to-trunk gating, demo using Tata DID fallback path, ext 1007 forwarded to mobile (9944421125).
• Editor + API platform fixes shipped (PR #96 trunk form password field, PR #97 user routing endpoints).

Background / narrative¶

Free-form section for "how we got here" context. Keep newest at top.

On-site discovery (initial visit)¶

Travelled ~500 km to the hotel. Network scan revealed UCM6301 + DBC ONT + GRP2636 + GWN7002 + 2× GWN7802 switches + ~24 IP phones registered to UCM. No Astradial NUC at this hotel — confirmed by SSH-rejecting the only suspicious LAN host (192.168.0.13).

Cloud trunk + UCM registration¶

Created the cloud-side org_moijhj2l_trunk1777732151626 inbound trunk via editor (with Bug 1 above patched mid-session and deployed). UCM-side Register SIP Trunk configured pointing to devsip.astradial.com:5080. After resolving Gotchas #1 (auth username = peer name) and #2 (port 5080 not 5060), trunk registered cleanly. Verified at cloud with pjsip show aor org_moijhj2l_trunk1777732151626 showing Avail RTT 175ms.

BSNL line behaviour during install¶

The BSNL line had a ~15-min outage mid-session — silent on both inbound and outbound — then resumed. Suspected carrier-side rate-limit after rapid test calls. Worth flagging to BSNL engineer in the meeting (ask if the line is anti-fraud throttled).

What blocks demo¶

Inbound calls hitting BSNL FXO are matched by UCM Inbound Route BSNL-AstraDial, which dials External Number 918065978007 via Outbound Route AstradialCloud_Out. UCM silently drops the call before sending an INVITE — no INVITEs reach cloud, no CDR entry on UCM. UCM6301 firmware does not expose an explicit "trunk-to-trunk allowed" toggle. Setting Privilege Level to Disable on the outbound route did not unblock. Suspected hidden permission gate or pattern matcher behaviour. Resolution deferred to Grandstream installer meeting.

Demo workaround available¶

BSNL CFA (*21*08065978007#) routes BSNL → Tata → cloud → ext 09 (works ✅, but bills BSNL forwarding leg). Not yet activated — requires either BSNL helpline 198 configuration or DTMF-passing from a UCM IP phone (which UCM's outbound route currently doesn't allow due to * and # characters).