Documented specifications
Grandstream · Manufacturer documentation available at review; exact SKU availability, remaining support period and approved firmware not established.
| Specification | Documented value |
|---|---|
| Analog interfaces | 16 FXS RJ11 ports and a Telco connector Source ↗ |
| FXO ports | None; this model terminates analog subscriber devices Source ↗ |
| Network | One 10/100/1000 Mbps RJ45 port Source ↗ |
| SIP profiles | Four per system; separate SIP account per port Source ↗ |
| Fax | T.38 and G.711 pass-through options documented Source ↗ |
| Security | TLS, SRTP and secure boot described for the v2 series Source ↗ |
Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.
Confirm GXW4216 v2 before choosing firmware
Read the chassis label and record the V2 designation, installed firmware and configuration owner. The GXW4216 v2 has 16 FXS subscriber ports; it is not an FXO gateway. Use only the documented V2 firmware lane and review release notes before staging or rollback.
Map all sixteen ports to physical pairs
Document every RJ11 or Telco-connector pair, wall jack, analog device and intended extension. Compare a handset going off-hook with the gateway port-status row. A seated connector or dial tone does not prove the pair reaches the intended port.
Assign profile and SIP identity per port
The family supports four SIP profiles and an independent account per port. Record the profile, SIP User ID, Authenticate ID, masked credential state, server and PBX extension separately for each of the sixteen ports. Routing ID presentation does not replace the registration identity.
Keep hunting separate from registration
If ports belong to a linear or circular hunt group, document membership, order and Active Port Only versus All Ports registration. Hunting selects an eligible member for an incoming call; it does not make all sixteen ports ring at once.
Commission analog and fax behavior per circuit
Verify hook state, ringing, caller ID, disconnect supervision and DTMF on each required circuit. Test T.38 or G.711 fax end to end with a real document only after confirming support across the entire call path.
Prove effective configuration after provisioning
Distinguish template creation, fetch, parse, apply, reboot and effective per-port state across web, XML or GDMS ownership. Preserve a recoverable approved configuration and secrets handling. No gateway, analog endpoint, cabling, PBX, registration, firmware, fax, call or media stream was inspected or tested.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.