phone.systems™ trunks#
An inbound phone.systems™ trunk delivers calls received on your DIDWW DID numbers to the phone.systems™ PBX associated with your DIDWW account. Use this trunk type to send incoming calls to the PBX rather than directly to an external SIP endpoint or PSTN phone number.
The trunk settings control the format of the caller’s number, an optional caller ID prefix, and optional CNAM lookup for U.S. caller IDs. Configure how calls are answered and routed separately in phone.systems™, using call flows, users, and contact methods.
How phone.systems™ trunks work#
When a caller dials a DID number, the public telephone network routes the call to DIDWW. DIDWW delivers the call through the phone.systems™ trunk assigned to that DID number. The PBX then applies the routing configured for the number to determine where the call goes.
%%{init: {
"theme": "base",
"themeVariables": {
"fontSize": "14px",
"primaryColor": "#e0f2fe",
"primaryBorderColor": "#38bdf8",
"primaryTextColor": "#1f2d3d",
"secondaryColor": "#ccfbf1",
"secondaryBorderColor": "#2dd4bf",
"secondaryTextColor": "#1f2d3d",
"lineColor": "#0066cc",
"textColor": "#1f2d3d",
"nodeTextColor": "#1f2d3d",
"edgeLabelBackground": "#ffffff"
}
}}%%
flowchart LR
caller["Caller"] --> |dials DID| did["DID number"]
did --> |assigned trunk| trunk["phone.systems™ trunk"]
trunk --> pbx["phone.systems™ PBX"]
pbx --> |configured routing| destination["Call destination"]
classDef endpoint fill:#e0f2fe,stroke:#0066cc,color:#1f2d3d,stroke-width:1.5px
classDef process fill:#ccfbf1,stroke:#2dd4bf,color:#1f2d3d,stroke-width:1.5px
class caller,destination endpoint
class did,trunk,pbx process
linkStyle default stroke:#0066cc,stroke-width:1.5px
The DIDWW phone.systems™ trunk is separate from Inbound Trunks in phone.systems™, which configure how the PBX receives SIP traffic from VoIP providers.
phone.systems™ trunks and DID numbers#
To route a DID number’s incoming calls to phone.systems™, assign a phone.systems™ trunk to that number in the DIDWW User Panel. Multiple DID numbers can use the same trunk and its caller ID and CNAM lookup settings.
Assigned DID numbers automatically appear under Numbers > Phone Numbers in phone.systems™. These DIDWW number records cannot be edited or deleted from that list. Manage their trunk assignment in the DIDWW User Panel and their PBX routing in phone.systems™. See phone.systems™ Phone Numbers for details about the number records.
The DID number must have sufficient Capacity for concurrent inbound calls. The phone.systems™ trunk configuration does not include a separate Capacity Limit field.
Get started#
An active phone.systems™ subscription and at least one DID number are required. A trunk named phone.systems is created automatically with your subscription. Assign it to your DID numbers, then configure the PBX.
Start a subscription and choose the number of seats for your PBX.
Assign the phone.systems™ trunk to one or more DID numbers.
Open the PBX and prepare your app or softphone to receive calls.
Configure and manage trunks#
Create an additional trunk only when some DID numbers need different caller ID or CNAM settings. Editing an existing trunk changes the settings used by all DID numbers assigned to it.
Create an additional trunk with its own caller ID and CNAM settings.
View, edit, or delete existing trunks.
Caller information#
Configure the caller number and optional caller name delivered to the PBX.
Choose the caller ID format and an optional prefix.
Enable caller-name lookup for U.S. caller IDs. Additional per-call charges apply.
Configure PBX call routing#
Configure how phone.systems™ answers and routes calls after they arrive through the trunk.
Build call flows to direct incoming calls through the PBX.
Create users and configure their application lines and access.
Configure apps, SIP devices, and forwarding destinations for incoming calls.
Monitor calls and troubleshoot#
Review delivery to the PBX and how phone.systems™ handles each call.
Review DIDWW call records for delivery attempts to the PBX.
Review call destinations, statuses, and end codes inside the PBX.
Identify failed inbound calls and investigate delivery problems.