Core Module
Trunks
Trunks connect NextGenSwitch to upstream carriers or peering partners. Each trunk stores SIP credentials, connection properties, and optional call limits/recording policies. Properly configured trunks ensure outbound and inbound routes have reliable gateways.
Module Workflow
- Choose Trunks from the main navigation.
- The list page summarizes trunk names, host details, status, and usage.
- Click Create Trunk or edit an existing entry to manage SIP credentials and capacity.
Configuration Steps
- Trunk Overview - Name the trunk (for example, Carrier A - Primary) and specify whether it uses Peer mode. Peer mode exposes host/port fields and typically suits static peers; disable it for registration-based trunks. Enable call recording if required.
- SIP User Info - Provide username/password credentials. The labels adjust automatically between Remote and Local to reflect peer vs. registered trunks. When editing, leave the password blank to keep the existing secret.
- Peer Details - If peer mode is enabled, supply the host, port, and transport protocol. These fields hide automatically for registered trunks.
- Capacity & Caller ID - Set a call limit (or leave blank for unlimited) and decide whether to Overwrite CID, forcing outbound caller ID to match the trunk.
- Save the trunk. A helper script toggles field requirements whenever the peer checkbox changes, preventing incomplete submissions.
Operational Tips
- Naming - Include carrier and purpose (for example, VoIP.ms - Backup International) for quick identification.
- Security - Use long random passwords for registration trunks. Restrict by IP if your carrier allows.
- Monitoring - Pair trunks with carrier dashboard alerts so you learn immediately when a peer drops.
- Version Control - Before editing a production trunk, duplicate it and test with a staging route if possible.
Field Reference
| Section | Field | Required | Description |
|---|---|---|---|
| Overview | Name | Yes | Friendly identifier shown throughout the UI. |
| Overview | Peer? | No | When enabled, host/port become mandatory and the PBX expects IP-based authorization. |
| Overview | Record calls? | No | Enables carrier-level recording for compliance or QA. |
| SIP User Info | Username | Yes | Authentication or peer username. |
| SIP User Info | Password | Yes | SIP secret for new trunks. During edits, blank keeps the old value. |
| Peer Details | Host | No | Carrier hostname/IP for peer trunks (required only in peer mode). |
| Peer Details | Port, Transport | No | Optional non-default SIP port and transport (UDP/TCP/TLS). |
| Capacity & Caller ID | Call Limit | No | Caps concurrent calls on this trunk. |
| Capacity & Caller ID | Overwrite CID? | No | Forces outbound caller ID to values configured at the carrier. |
Troubleshooting
- Registration Fails: Double-check username/password, transport, and firewall openings on ports 5060/5061 (or your custom port).
- Cannot Save: Peer mode requires host entry; the form enforces this with a required indicator.
- Caller ID Wrong: Enable Overwrite CID only if your carrier expects a fixed caller ID. Otherwise, disable it and control IDs per extension/route.
- Exceeding Limits: Increase Call Limit or leave blank for unlimited, but confirm billing terms with the carrier first.
- Accurate trunk settings form the backbone for inbound/outbound routing. Engage support with trunk name, registrar or peer IP, and sample call timestamps for deeper diagnostics.
Practical Example
Scenario: Configure a registration-based trunk for Carrier Nova that overwrites caller ID to a toll-free number.
- Name: "Carrier Nova - Primary"
- Peer Mode: disabled (registration)
- Username: novasip01
- Password: randomly generated secure string
- Call Limit: 40
- Overwrite CID: enabled (carrier expects +18885551234)
- Record Calls: disabled (handled elsewhere)
Maintenance & Automation
Routine Checks
- Confirm registrations with sip show registry (Asterisk) or your SBC equivalent. Investigate peers marked Unreachable.
- Review call limits every quarter to ensure they match carrier contracts and traffic growth.
- Keep a secure vault entry for each trunk credential with rotation and ownership metadata.
Automation Ideas
- Monitor trunk health via SNMP or SIP OPTIONS pings and automatically open support tickets when peers fail for more than five minutes.
- Use CI/CD to lint trunk JSON definitions before deployment and flag missing hosts, weak passwords, or excessive call limits.
- Schedule password rotation scripts that update the carrier portal and PBX simultaneously, then send a Slack notification with completion status.
Related Platform Pages
Connect this module to product and solution context for planning and implementation.