Choose one PBX identity model before configuration
GoTrunk documents static and dynamic PBX connection types. A static public IP can authorize outbound traffic by source address and receive inbound traffic at a configured SIP URI. A dynamic-address deployment uses generated credentials, and the current Asterisk PJSIP example registers so inbound traffic follows the latest contact. Record the selected endpoint object, direction, public address or redacted identity and configuration owner before applying a template.
Keep authorization, registration and call completion as separate states. A static endpoint is not expected to prove reachability with the dynamic model's REGISTER signal, while a green registration does not prove the number target, outbound permissions or media path. Follow the account-specific endpoint instructions; do not combine source-IP and credential settings merely to make one status display change.
Documented service facts
Reviewed 2026-09-28. Compare SIP trunk services →
Authentication
DocumentedGoTrunk documents two PBX identity models: a static public IP can authorize outbound traffic by source address, while a dynamic-address deployment uses generated username and password credentials. The same account can expose different inbound and outbound controls, so preserve direction, endpoint object, public address or redacted credential identity and configuration owner separately.
SIP registration
DocumentedThe dynamic-IP Asterisk PJSIP example uses REGISTER so inbound calls follow the most recent contact. The static-IP model sends calls directly to the configured address and does not establish a REGISTER dependency. A successful registration, accepted source address and completed call are separate evidence states; follow the selected account model rather than combining both templates.
Inbound delivery
DocumentedGoTrunk documents inbound delivery either to a static SIP URI or to the latest registered contact for a credentialed endpoint. Purchased or ported telephone numbers are assigned a target that can be changed in the portal, and some number orders can remain pending. Preserve the exact number, endpoint, target, delivered called-party format, provider source and PBX context; outbound success does not prove inbound assignment.
Inbound failover
Not verifiedGoTrunk's network guide says its own data-centre failover can redirect traffic and tells customers to allow every listed signaling and media address. The reviewed pages do not establish ordered customer destinations, response-code triggers, timers, off-net forwarding or established-call survival. Separate provider-site continuity from customer PBX and access-path resilience, then obtain the exact account behavior before testing.
Number and regional availability
Not verifiedGoTrunk says its portal offers numbers across more than 4,000 cities and supports purchases and ports, but exact inventory, portability, activation time, documents and feature combinations remain number-, account- and date-specific. Some DIDs can remain pending for support processing. Verify the exact locality, number type, status and port requirements before scheduling a migration.
Audio codecs and DTMF
Not verifiedThe reviewed current endpoint, network and Asterisk pages do not publish a complete customer codec and DTMF support matrix. An illustrative PJSIP template or open RTP path is not evidence of the codec, payload, packetization or digit method negotiated on a production route. Obtain the current interop profile and capture SDP and digit behavior on representative authorized calls.
T.38 fax
Not verifiedThe reviewed current service, endpoint, network and telephone-number pages do not establish T.38 availability, audio-fax fallback or a supported fax workflow. Ordinary voice delivery does not qualify fax. Confirm the exact number, direction, route, PBX or gateway, initial codec, redundancy mode and document set before relying on fax service.
Signaling and media encryption
Not verifiedThe current network guide lists TCP and UDP SIP signaling plus RTP address ranges, while the Asterisk example uses UDP. The reviewed pages do not establish a customer TLS identity, certificate-validation procedure, SRTP profile or downgrade policy. Source-IP authorization, NAT handling and firewall allowlisting are not encryption; obtain protected-transport requirements in writing and verify the negotiated leg.
Concurrent calls and burst
Not verifiedThe telephone-number guide says incoming channels can be increased for an additional monthly charge, but the reviewed pages do not define one account's simultaneous-call, calls-per-second, burst, queueing or abuse limits. Number count and SIP endpoints are not capacity. Obtain active limits, direction, rejection behavior, upgrade timing and billing before an authorized load test.
Emergency calling
DocumentedGoTrunk documents emergency calling only in some geographic locations. Its portal workflow adds and verifies a geographic address, then links that Location to one telephone number; regulatory proof of address can be required. Confirm country and number eligibility, validated address, outbound identity, callback and the current provider-approved test procedure for every site, and retain an independent fallback.
Pricing model
Not verifiedGoTrunk advertises per-second billing, no setup fee and no contract, and its portal exposes destination rates. The number guide also notes a monthly charge for added incoming channels. These statements do not establish an account's current numbers, destinations, currency, billing increments, commitments, porting, emergency, support, taxes or renewal terms. Preserve a dated quote and rate export for the actual traffic mix.
Administration and support
DocumentedThe portal documentation covers SIP endpoints, telephone-number targets, call-detail filtering, end causes, trace download, CSV export and FTP access. These controls can support diagnosis but do not define an account SLA, trace completeness, data-retention period, support response or credit. Preserve redacted configuration, provider call identifiers, CDR or trace evidence and support case together.
SMS and MMS
Not verifiedThe reviewed current SIP-trunk, telephone-number and portal pages do not establish SMS or MMS on a GoTrunk number. Voice capability does not prove messaging eligibility, sender registration, consent controls, API delivery, throughput or fees. Verify the exact number, country and messaging program independently.
Map every number to its actual inbound target
GoTrunk's number workflow assigns a target to each purchased or ported number and allows that target to be changed. Some number requests can remain pending for support processing. Preserve the exact number, order or port status, endpoint, target, provider ingress set, delivered called-party format and PBX context. A configured endpoint or successful outbound call does not establish that a particular DID is active and routed.
The provider advertises broad city coverage, but inventory, portability, documents, activation and features remain specific to the number, account and date. Confirm the exact locality and number type before publishing a migration window. After activation, place a bounded inbound test from another carrier and compare the observed target and identity with the portal record.
Separate provider data-centre continuity from customer failover
The network guide lists regional signaling and RTP addresses and says provider data-centre failover can redirect traffic to another location. Its firewall guidance therefore tells customers to permit every published address in scope. Snapshot the current provider list and compare it with the PBX, SBC, firewall and NAT policy without opening broader source ranges or exposing management interfaces.
That provider control is not proof of ordered customer destinations, response-code retry, PSTN forwarding or established-call survival. The reviewed pages do not establish those customer-side behaviors. Document internet, firewall, PBX and provider-site failures separately, obtain the actual account behavior, then test only the authorized scenario with a rollback and an independent calling path.
Qualify media, security and capacity instead of inferring them
The reviewed endpoint, network and Asterisk pages do not publish a complete current codec and DTMF matrix. The network guide describes TCP or UDP signaling and RTP, and the Asterisk example uses UDP; neither establishes TLS certificate validation or SRTP. Likewise, ordinary voice service does not establish T.38 fax. Obtain the current interop profile, then preserve SDP, negotiated transport, media endpoints and digit behavior on representative routes. Qualify fax independently by number, direction, gateway and document set.
The number guide says incoming channels can be increased for an additional monthly charge, but it does not establish one account's simultaneous-call, calls-per-second, burst or queueing limits. Capture active limits, rejection behavior, upgrade timing and billing before any authorized load test. A count of numbers, endpoint objects or portal controls is not a measured capacity result.
Verify emergency location and caller identity together
GoTrunk documents emergency calling only in some geographic locations. Its portal workflow adds and verifies an address, can require regulatory proof and links the resulting Location to one telephone number. Confirm the eligible country and number, validated address, outbound identity, callback, alerts and provider-approved test process for every operating site. A verified address that is not linked to the calling identity is not complete evidence.
Do not place an emergency test call without the provider's current authorization and local procedure. Mobile users, temporary sites and nomadic endpoints need an explicit location plan rather than inheriting the office record. Retain an independent emergency fallback and protect address and identity evidence according to the organization's privacy policy.
Use portal evidence without overstating service terms
The portal documentation covers endpoint and number configuration, destination rates, call-detail filtering, end causes, trace download, CSV export and FTP access. Preserve a redacted configuration snapshot, provider call identifier, trace or CDR, and support case together. A portal trace can narrow a signaling failure, but its presence does not define completeness, retention, SLA, response time or credits.
GoTrunk advertises per-second billing, no setup fee and no contract, while extra incoming channels can carry a monthly charge. Obtain a dated quote and rate export for actual numbers, destinations, currency, increments, porting, emergency service, support, taxes and renewal. The reviewed pages do not establish SMS or MMS on a trunk number. No GoTrunk account, endpoint, number, call, codec, DTMF, fax, encryption, failover, capacity, emergency call, message, price, availability or support response was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- GoTrunk service overview ↗
- GoTrunk SIP Endpoints ↗
- GoTrunk Network Configuration ↗
- GoTrunk Locations ↗
- GoTrunk Asterisk PJSIP 18 guide ↗
- GoTrunk Telephone Numbers ↗
- GoTrunk Call Rates ↗
- GoTrunk Call Detail Records ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.