Name the ordered product and access path before configuring SIP
Gamma describes SIP Trunks as the connection between an on-premises telephone system and its network over an internet connection or private access circuit. The public material does not publish one universal registrar, credential, fixed-source authorization rule, SBC list, transport or port set for every order. Start with the contract, Gamma or channel-partner handover, assigned peers, permitted customer addresses, access circuit, DNS treatment, number ranges and change owner.
SIP Trunks, SIP Trunk Call Manager and Gamma Inbound are separate named components on the current page. A trunk connection does not prove that Call Manager or Inbound was ordered, and portal visibility does not prove that a PBX peer, number route or live call works.
Documented service facts
Reviewed 2026-10-23. Compare SIP trunk services →
Authentication
Not verifiedThe public page establishes internet or private-circuit access but does not publish one universal registrar, credential, fixed-source policy, SBC list, transport or port set. Build from the dated Gamma or partner handover and verify assigned peers and customer addresses.
SIP registration
Not verifiedThe reviewed public material does not say every ordered trunk registers or publish registrar, username, expiry or Contact behavior. Do not create credentials or wait for registration state without the current implementation record.
Inbound delivery
DocumentedSIP Trunk Call Manager can terminate subscribed 01, 02, 03 and 08 numbers on Gamma SIP Trunks. Number assignment, selected cloud rule, provider attempt, customer-edge receipt and PBX destination remain separate.
Inbound failover
DocumentedGamma describes site-to-site trunk rerouting, SIP Trunk Call Manager destinations and a separate Gamma Inbound service. The public material does not prove the ordered trigger, first-call delay, recovery rule or established-call survival.
Number and regional availability
DocumentedGamma describes UK PSTN breakout and number transfer, while its code says geographic-number retention after a move is not always possible. Inventory, portability, address eligibility and timing require a dated result.
Audio codecs and DTMF
DocumentedGamma names G.711 and G.729. The public page does not define law, preference, packetization, DTMF or the selected format for one account; preserve offer, answer and RTP evidence.
T.38 fax
Not verifiedThe reviewed sources do not establish T.38, G.711 fax pass-through or an acceptance workflow for every order. Qualify fax independently.
Signaling and media encryption
Not verifiedPrivate access and CallGuard are documented, but they are not proof of SIP TLS or SRTP. Obtain the ordered transport, certificate, peer-validation, media and downgrade profile.
Concurrent calls and burst
Not verifiedGamma says trunk channels are technically uncapped subject to bandwidth. That is planning language, not purchased entitlement or a call-start limit. Preserve ordered channels, calls per second, bandwidth and rejection behavior separately.
Emergency calling
Not verifiedThe reviewed public SIP material does not define emergency eligibility, registered location, identity, callback or approved testing for every order. Confirm per site and number and retain an independent fallback.
Pricing model
Not verifiedThe product page contains indicative figures while the code points customers to their contract and current price information. Obtain dated terms for access, channels, calls, numbers, porting, cloud features, support and termination.
Administration and support
DocumentedCurrent support material separates direct-customer and partner paths, publishes a service-status channel and provides SIP Trunking training. Record support ownership, portal role, service IDs, call IDs, timestamps and tickets.
SMS and MMS
Not verifiedThe reviewed Gamma SIP Trunks material does not establish SMS or MMS entitlement on trunk numbers. Voice service does not prove messaging eligibility, sender controls, throughput, retention or fees.
Trace the subscribed number to its trunk and PBX destination
Gamma says SIP Trunk Call Manager can terminate subscribed 01, 02, 03 and 08 numbers directly on Gamma SIP Trunks. Preserve the assigned number, port state, selected service, source peer, Request-URI, To, asserted identity, diversion history, customer-edge receipt, PBX match and final destination for one authorized attempt. A reachable trunk is not evidence that a number is assigned, ported or normalized correctly.
The current page says numbers can be retained or transferred, while the March 2020 code of practice says retaining a geographic number after an office move is not always possible. Treat portability, inventory, address eligibility and cutover timing as dated order results rather than general product capabilities.
Version every Call Manager rule and its selected destination
The current product page describes routing to a colleague, mobile, hunt group or call queue and says call plans can be built around operating hours. Gamma’s current Inbound training page lists two SIP Trunk Call Manager Call Plans tutorials, while the broader product page describes IVR, announcements, statistics and scheduled inbound routing under Gamma Inbound. Verify which product and current portal fields own each behavior.
For each affected number, export or record the active rule name, priority, schedule, condition, destination, queue or hunt membership, fallback, editor, change time and timezone. A saved portal change proves configured intent only. It does not prove which rule evaluated, that the destination answered or that a call used the expected media path.
Keep trunk rerouting, Call Manager and Gamma Inbound distinct
Gamma describes connecting two on-premises systems so new calls can reroute between sites. It separately describes SIP Trunk Call Manager as centralized inbound control and Gamma Inbound as a cloud service with Contact Point, Contact Path and Contact Pro variants. Record which component owns the trigger and destination instead of treating every redirect as trunk failover.
The page uses immediate continuity language, but it does not establish that an existing call survives, the first new call avoids detection delay or a failed primary is restored automatically. Test primary failure, first later attempt, subsequent calls, alternate destination, recovery and return separately with timestamps and rollback.
Separate marketing availability, media and capacity from observations
The current page publishes 99.99% availability in one section and 99.999% later on the same page. Preserve that conflict and obtain the signed service schedule, measurement perimeter, exclusions and remedy; neither webpage statement is an observed account result. The public service-status page is a current incident channel, not proof that one customer path is healthy.
Gamma names G.711 and G.729 and says trunk channels are technically not capped, subject to bandwidth. Those statements do not define the ordered codec law, preference, packetization, DTMF, purchased channels, calls per second, rejection behavior or PBX limit. Retain SDP, RTP and capacity evidence for the exact authorized call or load test.
Resolve security, emergency and support ownership before cutover
The current page describes private access and CallGuard fraud controls but does not publish a universal customer-facing SIP TLS or SRTP profile. Access isolation, fraud monitoring, signaling protection and media protection remain different controls. Obtain the ordered transport, certificate, peer-validation, media and downgrade requirements rather than inferring encryption from a private circuit or fraud feature.
The reviewed public SIP material does not define emergency eligibility, registered location, required identity, callback or an approved test method for every order. Confirm those per site and number and keep an independent fallback. The support page distinguishes new, partner and direct-customer paths; record who owns first-line support and retain redacted configuration, call identifiers, status evidence and tickets.
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 Inbound Call Routing user support and training ↗
- Gamma help and support ↗
- Gamma service status ↗
- Gamma codes of practice ↗
- Gamma Business Communications Code of Practice ↗
- Gamma disaster-recovery planning article ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.