V7 — Grandstream + BSNL Meeting Brief¶

Two parts: - (A) Info to share with the Grandstream installer + BSNL engineer ahead of the meeting so they come prepared. - (B) What YOU still need to gather/verify before the meeting so it doesn't get blocked on missing data.

(A) Pre-meeting brief — share with Grandstream + BSNL¶

Site / customer¶

What we're trying to achieve¶

The hotel's BSNL landline 04175295093 should land on Astradial's cloud PBX so calls can be answered by an AI agent / IVR / queues, and outbound calls placed by hotel staff (via Astradial cloud) should display 04175295093 as caller ID. The on-prem Grandstream UCM6301 will be the SIP trunk bridge between BSNL and the cloud.

Equipment on site¶

Carrier / numbers¶

Network / WAN¶

What's already configured (don't undo this)¶

1. Cloud-side SIP trunk endpoint for V7 created and registered:
2. Cloud Asterisk: devsip.astradial.com:5080 UDP
3. Endpoint name: org_moijhj2l_trunk1777732151626
4. Auth username = peer name (the long string above), not a friendly name
5. Verified registered, RTT ~175ms, contact 202.141.32.100:37126;x-ast-orig-host=192.168.0.60:5060
6. UCM SIP trunk (Register SIP Trunk type) named AstradialCloud pointing at devsip.astradial.com:5080. Status: Reachable, Registered.
7. UCM Outbound Route AstradialCloud_Out: pattern _918065978007, Privilege: Disable, Trunk: AstradialCloud. Saved + Applied.
8. UCM Inbound Route BSNL-AstraDial: Trunk = Analog Trunks PSTN, pattern _s, Default Destination = External Number 918065978007.

What's NOT working — the question for the meeting¶

• When a call arrives on the BSNL FXO line and the UCM's BSNL-AstraDial inbound route fires, the UCM silently drops the call before sending an INVITE to the SIP trunk. The cloud sees zero INVITE traffic from 202.141.32.100.
• Grandstream's UCM6301 firmware on this site does not expose an explicit "Allow trunk-to-trunk forwarding" or "Use Outbound Trunk for Inbound Routes" toggle that we could find.
• The "External Number" inbound destination does not have an inline trunk picker on this firmware.

Specific questions for the Grandstream installer:

1. On UCM6301 firmware (current version — pull from Status → System Information), what setting gates trunk-sourced (FXO inbound) calls from using outbound routes?
2. Is there a hidden global config (PBX Settings → SIP Settings or General) for cross-trunk forwarding?
3. Should we use a Ring Group with a static SIP destination (918065978007@AstradialCloud) instead of External Number, to bypass any privilege gating?
4. Is there a Custom Dialplan facility we can use to write exten => s,1,Dial(PJSIP/918065978007@AstradialCloud,30) directly?
5. What CDR / SIP capture method gives us the most useful diagnostics if the call is silently dropped?

Specific questions for the BSNL engineer:

1. The line 04175295093 — was it rate-limited / under maintenance when we observed ~15 minutes of inbound silence on the initial install evening? Multiple inbound test calls produced silence then resumed.
2. What service tier is currently provisioned on the line — analog conversion (FXS at the ONT) or true SIP trunk delivery? (We see analog at the UCM's FXO port.)
3. Can the same fibre deliver voice as SIP-over-Ethernet instead of analog FXS? Today the ONT converts SIP→analog internally. We'd like the ONT to pass SIP through to its Ethernet port so our equipment can register/peer directly. What plan/service is needed?
4. If yes to #3 — is the SIP authenticated by username/password (registration-based) or by IP whitelist (peer-based)? This is the single biggest architecture decision.
5. If by IP whitelist — can BSNL whitelist a remote cloud IP (Astradial cloud 89.116.31.109, Contabo Germany), or only the local hotel circuit's WAN IP?
6. If currently analog and staying analog: what's the inbound delivery SLA, and does BSNL throttle inbound after rapid call-test sequences (anti-fraud)?
7. Static IP availability for the WAN side — needed if we go with IP-whitelisted SIP peering.
8. Cost / SLA / lead time for any SIP upgrade.

Decision tree based on BSNL's answers¶

The combination of answers to questions 3, 4, and 5 above determines the architecture. Use this table at the meeting:

Quick analogy for the BSNL engineer (if they need it)¶

"Today the fibre carries voice + internet, but the ONT splits voice off as analog before handing it to us. We want the ONT to pass voice through as SIP over Ethernet — so we can connect our equipment to the Ethernet port and handle voice digitally without the ONT converting it. Most modern GPON deployments support this; we want to know if this site/plan does."

Most BSNL field engineers will recognise this immediately as the difference between "ONT in voice gateway mode" (today) vs "ONT in bridge mode for voice VLAN" (what we want).

Test plan to run during the meeting (Astradial side)¶

1. Verify trunk still registered: ssh root@89.116.31.109 'asterisk -rx "pjsip show aor org_moijhj2l_trunk1777732151626"' — should see Avail.
2. Apply Grandstream installer's recommended fix.
3. From an external mobile, dial 04175295093. Watch cloud Asterisk logs in real time:

   ssh root@89.116.31.109 'asterisk -rx "pjsip set logger on"'
   tail -f /var/log/asterisk/full.log | grep -E "202\.141\.32\.100|918065978007"
   

4. Expected: see INVITE arrive, see Goto into org_moijhj2l__incoming, see Dial to ext 09. GRP2636 should ring.
5. From a cloud-registered softphone, dial an external number. Watch UCM CDR for the outbound. Recipient should see CID 04175295093.
6. Reverse direction: failover behaviour — disable AstradialCloud trunk on UCM, re-test inbound. Confirm only the BSNL CFA fallback still works.

(B) What YOU still need to gather/verify before the meeting¶

These are things that aren't stored in our docs and we need them to walk in prepared.

Critical (without these, meeting is partially blocked)¶

1. UCM6301 firmware version — UCM web UI: Status → System Information. Screenshot or copy the version string. Grandstream behavior varies wildly between firmwares, so the installer's first question will be "what version".
2. DBC ONT admin password — sticker on the bottom/back of the BSNL ONT (the SaiNXT box at 192.168.1.1). Format usually: User: admin / Password: <printed>. Without it, BSNL engineer can only configure remotely; with it, we can also inspect locally during the meeting.
3. BSNL service tier confirmation — call the hotel manager and ask what plan/circuit they have. Or ask them to read out the BSNL bill. Differentiates "broadband + analog phone" from "NGN SIP Trunk".
4. BSNL account number / customer ID — from hotel's BSNL bill. Both engineers will ask for this.
5. Whether BSNL line has CFA (Call Forwarding Always) enabled or supported — get the hotel manager to dial *#21# from any phone connected to the BSNL line. They'll hear a voice response. Document it.

Nice to have¶

1. Current GWN7002 router admin password — needed to disable SIP ALG (a common cause of SIP problems on Indian routers). 3 login attempts left. If unknown, factory-default is admin/admin. Don't lock it out.
2. Photographs of the rack — make sure you have:
3. Front of UCM6301 + label/serial
4. Back of UCM6301 showing FXO/FXS port labels and which cables are plugged where
5. Front + back of DBC SaiNXT ONT (the BSNL fiber CPE) including the credentials sticker
6. Where the BSNL fiber pigtail enters the room
7. Any wall-mount BSNL termination box outside the rack
8. List of which UCM extensions are actively used — Extension/Trunk → Extensions page screenshot. Useful so Grandstream installer doesn't accidentally break a working phone.
9. BSNL field engineer's direct phone/email — if you can get a name from the hotel manager or via BSNL helpline, having a name to reach gets things moving faster than the generic helpline.

Already in our doc — bring these to the meeting¶