Begin with the ordered trunk, access and trust model
Gamma's current product page describes connecting an on-premises PBX to the Gamma network over broadband, Ethernet or a private access circuit. It does not publish one universal customer authentication or registration model. Preserve the exact supplier or channel partner, product name, quote, order, handover record, access circuit, assigned SBC peers, permitted source addresses, ports, transport, DNS behavior and change owner before building the PBX object.
Do not infer digest registration from the word SIP, fixed-IP authorization from a private circuit, or a registrar from another Gamma product. A network path, an OPTIONS response, a registration indicator and a completed call are separate evidence states. If the implementation worksheet is unavailable, keep authentication and registration marked unresolved rather than adapting another carrier's template.
Documented service facts
Reviewed 2026-10-05. Compare SIP trunk services →
Authentication
Not verifiedGamma's current product page establishes an on-premises PBX connection to the Gamma network over broadband, Ethernet or a private access circuit, but it does not publish a universal customer authentication method, source-address policy, credential format or SBC trust boundary. Obtain the current implementation record, assigned peers, permitted source addresses, transport and access design before choosing a PBX template.
SIP registration
Not verifiedThe reviewed public product and support pages do not say that the ordered trunk registers or document a registrar, username, expiry or Contact behavior. Do not create credentials, wait for a registration indicator or infer a fixed-peer model from the access circuit alone. Preserve the order, handover record and current confirmation from the named Gamma supplier or channel partner.
Inbound delivery
DocumentedGamma describes PSTN breakout through an on-premises PBX and says SIP Trunk Call Manager can terminate subscribed 01, 02, 03 and 08 numbers on Gamma SIP Trunks. That does not establish the Request-URI, asserted identity, number format or PBX route for an account. Trace one authorized number from the assigned route through the exact SIP identity to its final destination.
Inbound failover
DocumentedThe product page describes connecting two on-premises systems, rerouting between sites and combining Gamma SIP Trunks with the separate Inbound service or SIP Trunk Call Manager for alternate destinations. Gamma's user-support page lists separate Call Manager and Inbound guides, reinforcing that these controls are named service components rather than a universal trunk property. None of those pages proves the ordered trigger, route order, timer, destination, recovery behavior or established-call survival. Record the exact products and test bounded new-call failures with approved destinations and rollback.
Number and regional availability
DocumentedGamma's page describes UK PSTN breakout, 01, 02, 03 and 08 termination, number transfer and number retention when relocating. Gamma's published small-business code also describes number porting while warning that retaining a geographic number when moving is not always possible. Neither source proves inventory, portability, address eligibility or installation timing for a requested number; obtain a dated orderability and port result.
Audio codecs and DTMF
DocumentedGamma's current FAQ names G.711 and G.729 as network-supported codecs. The reviewed public materials do not define A-law versus mu-law, packetization, preference, transcoding, DTMF relay, telephone-event payload or downstream PSTN handling. Treat the codec names as service inputs and retain the actual SDP offer, answer, selected format, DTMF events and RTP endpoints from authorized calls.
T.38 fax
Not verifiedThe reviewed Gamma SIP Trunks page and code of practice do not establish T.38, G.711 fax pass-through, modem support or an acceptance workflow for the ordered service. Qualify fax independently for the exact number, direction, gateway, document set, switchover, ECM and fallback instead of transferring an ordinary voice result.
Signaling and media encryption
Not verifiedThe page discusses private access, CallGuard and fraud controls but does not publish a customer-facing SIP TLS or SRTP profile for this service. Access-network isolation, spend controls, signaling protection and media protection are different boundaries. Obtain the assigned transport and media profile, certificate and peer-validation requirements, downgrade behavior and fraud thresholds; do not represent CallGuard or a private circuit as proof that SIP or RTP was encrypted.
Concurrent calls and burst
Not verifiedGamma says channel capacity can be adjusted and its FAQ says there is no intrinsic maximum number of channels on a trunk, subject to bandwidth. That statement is not an account entitlement and does not define purchased channels, calls per second, burst behavior or rejection responses. Preserve active-call capacity, call-start rate, access bandwidth and PBX limits as separate dated values and load-test only with provider authorization.
Emergency calling
Not verifiedThe reviewed public SIP Trunks page does not define emergency-number eligibility, location registration, required calling identity, callback behavior, nomadic-use limitations or an approved test procedure. Confirm all of those for each UK site and number before migration, keep an independently available fallback and never place an uncoordinated live emergency test.
Pricing model
Not verifiedGamma's product page contains general cost examples and marketing comparisons, while its 2020 small-business code points customers to the contract and current price information. Neither is a complete current account quote. Obtain dated terms for access, channels, calls, destinations, numbers, porting, Call Manager or Inbound features, resilience, emergency service, support, taxes, commitment, renewal and termination.
Administration and support
DocumentedGamma describes a web portal and mobile app for SIP Trunk Call Manager, centralized number and inbound-call control, statistics and 24/7 assistance. Its separate user and partner support pages publish different training and escalation paths, so record whether Gamma or a channel partner owns first-line support before an incident. Portal controls belong to the named service and are not automatically transferred to a trunk-only order. Preserve the supplier, product names, order and service identifiers, assigned endpoints, redacted trust inputs, change timestamps, call identifiers and ticket; verify portal roles, escalation ownership and data retention.
SMS and MMS
Not verifiedThe reviewed Gamma SIP Trunks material does not establish SMS or MMS entitlement on trunk numbers. Its broad explanation of SIP carrying media is not a product commitment. Voice-number service does not prove messaging eligibility, sender registration, consent controls, API delivery, throughput, retention or fees; verify a separately identified messaging product and each exact number.
Trace each number and outbound identity separately
Gamma describes UK PSTN breakout and says SIP Trunk Call Manager can terminate subscribed 01, 02, 03 and 08 numbers on Gamma SIP Trunks. For one authorized inbound call, retain the assigned number, source peer, Request-URI, To, asserted identity, any Diversion or History-Info, PBX match and final destination. A reachable trunk does not prove a number is assigned, ported or normalized correctly.
For outbound calls, record the authorized identity contract and what the downstream network presents. Number ownership, PBX caller ID, provider acceptance and recipient display remain separate results. Gamma's small-business code describes porting and warns that retaining a geographic number after a move is not always possible; obtain a dated orderability and port result for every requested number and address.
Keep trunk continuity and cloud call control distinct
Gamma describes two on-premises systems, site-to-site rerouting and combinations with the separate Inbound service or SIP Trunk Call Manager. Its user-support page lists separate Call Manager and Inbound guides, reinforcing that these are named service components. Record which products are ordered, the primary and alternate destinations, route priority, trigger, timer, health signal, recovery rule, portal owner and any diversion charging or emergency-location consequence. Do not transfer Inbound or Call Manager controls to a trunk-only order.
These descriptions concern new-call routing and do not establish that an existing call survives a site, circuit, PBX or provider failure. Test each approved failure case separately with timestamps, rollback and a known calling number: initial failure, first subsequent call, later calls, alternate destination, recovery and return to the primary path.
Treat codec support as an input, not a call result
Gamma's current FAQ names G.711 and G.729 as supported codecs. It does not publicly define G.711 law, preference, packetization, transcoding, DTMF relay, telephone-event payload or downstream PSTN behavior for an account. Preserve the ordered media profile and capture the actual SDP offer, answer, selected format, packetization, DTMF events and RTP endpoints on authorized calls. Published support is not a quality or interoperability result.
The reviewed public material does not establish T.38, G.711 fax pass-through or modem behavior. Qualify fax as its own workflow for the exact number, direction, gateway, document set, switchover, ECM and fallback. Do not convert a successful audio call, G.711 support statement or another Gamma product's capability into fax acceptance.
Separate access, fraud controls, protection and capacity
The product page discusses private access, CallGuard, custom spend controls and service monitoring, but the reviewed material does not publish a customer-facing SIP TLS or SRTP profile. Access-network isolation, fraud detection, signaling protection and media protection have different owners and failure modes. Obtain the current transport and media profile, certificate and peer-validation requirements, keying method, downgrade behavior and CallGuard thresholds; do not claim encryption from a private circuit or fraud feature.
Gamma says channel capacity can be adjusted and that no intrinsic trunk-channel maximum applies, subject to bandwidth. That is not a purchased entitlement or a call-start-rate limit. Retain ordered concurrent channels, calls per second, burst behavior, rejection response, access bandwidth, codec budget and PBX limit separately, and run load work only with explicit provider authorization.
Resolve emergency, portal and commercial terms before cutover
The reviewed public SIP Trunks page does not define emergency-number eligibility, required identity, location registration, callback behavior, nomadic-use limitations or an approved test method. Confirm each item for every UK site and number, keep an independently available fallback and follow the provider's approved non-live validation path. Never place an uncoordinated live emergency test.
Gamma describes a web portal and mobile app for SIP Trunk Call Manager, centralized inbound control, statistics and 24/7 assistance. Its user and partner support pages expose different training and escalation paths, so the order and handover must establish whether Gamma or a channel partner owns first-line support. Portal functions belong to the named service and remain account-role dependent. Preserve service identifiers, redacted trust inputs, change timestamps, call identifiers and tickets. The reviewed pages do not establish messaging entitlement, exact availability or a complete current quote. No account, order, PBX, trunk, peer, number, route, call, codec, DTMF, fax, protection, failover, capacity, emergency call, message, price, availability, portal role 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.
- Gamma SIP Trunks and Call Management ↗
- Gamma SIP Trunking user support and training ↗
- Gamma partner support and training ↗
- Gamma Business Communications Code of Practice ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.