![voipsupply.com_logo450.jpg]](https://help.voipsupply.com/hs-fs/hubfs/voipsupply.com_logo450.jpg?height=40&name=voipsupply.com_logo450.jpg){kind=logo}
How to configure Grandstream GXW as one SIP Account / "Trunk"
1. Trunk-Style Registration
Instead of registering each port, you can configure the GXW to use a single SIP account (the "Trunk") for all 48 ports on each unit.
SIP Profile: Set up one SIP Profile (e.g., Profile 1) with your VSP's registration details.
Port Mapping: Assign all 48 FXS ports to this single Profile.
Caller ID/DOD: Use the DOD (Direct Outward Dialing) settings to map specific internal ports to their respective external DIDs provided by your VSP.
2. Hunting & Call Paths
Since you mentioned a 10-call path limit, you can manage this via the gateway's Hunting Group features.
You can group FXS ports together so they share the resources of the SIP trunk.
Limitation: The GXW doesn't natively "hard-cap" call paths to 10 at the gateway level like an SBC would; you typically rely on the VSP to reject the 11th concurrent session or use the Grandstream UCM series as a controller if strict local enforcement is needed.
3. Local Dialing (Internal Extensions)
If you need the ports to talk to each other without hitting the MetaSwitch:
The GXW supports a local dial plan. You can configure a dial plan that allows "extension-to-extension" dialing within the gateway using internal port numbers.
For your elevators and fire panels, ensure you prioritize these ports with Off-hook Auto-dial (Hotline) features to immediately trigger a call to the monitoring center upon off-hook.
Adtran vs. Grandstream Differences:
Internal Routing: The Adtran 908e has a more robust routing table for handling local vs. trunk traffic. On the GXW, you must be precise with your Dial Plan syntax to ensure local port numbers are handled internally while everything else is sent to the VSP.
Security: Like your Adtran, the GXW4248 supports SRTP and TLS for securing the SIP trunk connection to your VSP
Instead of registering each port, you can configure the GXW to use a single SIP account (the "Trunk") for all 48 ports on each unit.
SIP Profile: Set up one SIP Profile (e.g., Profile 1) with your VSP's registration details.
Port Mapping: Assign all 48 FXS ports to this single Profile.
Caller ID/DOD: Use the DOD (Direct Outward Dialing) settings to map specific internal ports to their respective external DIDs provided by your VSP.
2. Hunting & Call Paths
Since you mentioned a 10-call path limit, you can manage this via the gateway's Hunting Group features.
You can group FXS ports together so they share the resources of the SIP trunk.
Limitation: The GXW doesn't natively "hard-cap" call paths to 10 at the gateway level like an SBC would; you typically rely on the VSP to reject the 11th concurrent session or use the Grandstream UCM series as a controller if strict local enforcement is needed.
3. Local Dialing (Internal Extensions)
If you need the ports to talk to each other without hitting the MetaSwitch:
The GXW supports a local dial plan. You can configure a dial plan that allows "extension-to-extension" dialing within the gateway using internal port numbers.
For your elevators and fire panels, ensure you prioritize these ports with Off-hook Auto-dial (Hotline) features to immediately trigger a call to the monitoring center upon off-hook.
Adtran vs. Grandstream Differences:
Internal Routing: The Adtran 908e has a more robust routing table for handling local vs. trunk traffic. On the GXW, you must be precise with your Dial Plan syntax to ensure local port numbers are handled internally while everything else is sent to the VSP.
Security: Like your Adtran, the GXW4248 supports SRTP and TLS for securing the SIP trunk connection to your VSP