Choose trunk in or trunk out before building routes
sipgate's current help page distinguishes two operating modes. With trunk in, inbound and outbound traffic use sipgate and retained number ranges must be ported. With trunk out, inbound traffic remains on the existing fixed-network connection and sipgate carries outbound traffic. These are different cutover, ownership and failure models.
Record the exact ordered mode, PBX and software version, SIP ID owner, number inventory, port state, capacity, emergency record and support boundary. Keep this German service distinct from sipgate UK; similar branding does not make country, number, emergency, commercial or technical terms interchangeable.
Documented service facts
Reviewed 2026-10-09. Compare SIP trunk services →
SIP authentication
Documentedsipgate's current Asterisk example uses a personal SIP ID and SIP password for outbound authentication and registration. The example does not establish the production account's digest realm, algorithms, secret-rotation process, source-address restrictions or permitted concurrent registrations. Obtain the current trunk record, keep credentials out of tickets and captures, and validate a sanitized challenge and response.
SIP registration
Documentedsipgate says the PBX is registered as a whole rather than every phone. Its Asterisk example uses sipconnect.sipgate.de for server and client URIs and states that incoming calls require the Asterisk system to register. Treat that example as a starting point, not a complete template for another PBX, transport, DNS policy, Contact lifetime, qualification interval or retry strategy.
Inbound delivery
DocumentedThe current help page distinguishes trunk in, where inbound and outbound calls use sipgate after numbers are ported, from trunk out, where inbound calls stay on the existing fixed-network connection. The Asterisk example says inbound calls present the complete dialed E.164 number in the Request-URI. Confirm the ordered mode, assigned or ported number block, delivered identity and PBX normalization for each route.
Routing and failover
Not verifiedThe reviewed pages do not publish one automatic trunk failover, alternate registrar, DNS priority, PSTN reroute or established-call survival design for the selected order. The portal's fallback number is a caller-ID value used when the PBX sends no acceptable calling number; it is not a call-delivery failover destination. Record resilience, triggers, timers, route order and restoration separately and test an approved new-call failure case.
Number and regional availability
Not verifiedsipgate documents German local numbers, number blocks and porting in the product context, but the reviewed public pages do not establish current inventory, portability, lead time or serviceability for a requested address and number block. Bind every number to a dated qualification and port record. Keep sipgate's German service separate from the existing sipgate UK research record and do not transfer country-specific emergency, pricing or number rules between them.
Audio codecs and DTMF
Documentedsipgate's current Asterisk example permits G.722, A-law, mu-law, G.726 AAL2, GSM and iLBC and sets DTMF mode to auto. That sample is not proof of every PBX profile or negotiated call. Preserve both SDP bodies, selected payload and packetization, received RTP and decoded digits for the required destinations before reducing or reordering codecs.
T.38 fax
Not verifiedThe Asterisk example enables T.38 UDPTL settings, but a sample PBX configuration does not establish current fax entitlement, supported direction, switchover, redundancy, gateway interoperability or completed pages for the selected account. Obtain a current service statement and test representative pages over the ordered path. Treat alarms, elevators and other non-voice devices as separate workflows.
Signaling and media encryption
Documentedsipgate's current trunking help explicitly says a TLS/SRTP protected connection between the customer PBX and sipgate servers is not available and that infrastructure expansion for this is not planned. Do not label the PBX-to-provider leg encrypted. Document the exposed signaling and media boundary, restrict network access, protect credentials and assess whether the stated service design meets the organization's requirements.
Concurrent calls and call starts
Documentedsipgate's current help page describes tariff variants by usable channels and separately states 100 outgoing calls for the listed trunking offers. Do not convert those labels into an undocumented calls-per-second, burst, total-concurrency or PBX-capacity figure. Capture the current order's inbound channels, outbound limit semantics, codec bandwidth, PBX resources and any rate control as separate values.
Emergency calling
Not verifiedThe trunk detail page exposes a Notrufstandort emergency-location field, but the reviewed public pages do not establish the selected trunk's activation state, eligible number, dispatch handling, nomadic restrictions, callback behavior, notification, outage behavior or permitted test method. Complete the current provider process for every served location and retain an independently powered alternative for outages.
Pricing model
Not verifiedsipgate publishes current product and price pages and the help record describes monthly tariff variants, but a web page is not the selected account's accepted commercial record. Bind channel tier, numbers, usage, porting, international and premium destinations, taxes, support, renewal and termination to a dated order and bill. Recheck immediately before purchase or change.
Administration and support
Documentedsipgate documents a trunk overview showing location, status, consumed minutes and call barring plus detail views for emergency location, fallback caller ID and assigned numbers. Those portal fields do not prove registration, emergency activation or completed calls. Preserve role ownership, approved changes, monitoring, support contacts, escalation targets and timestamps from the actual account.
SMS and MMS
Not verifiedThe reviewed trunking pages do not establish SMS or MMS entitlement on trunk numbers, sender registration, API access, throughput, webhook protection, retention or price. Require a separate current messaging product and number-eligibility record; do not infer messaging from ordinary voice number assignment or from another sipgate product.
Treat registration as one evidence state
sipgate says the PBX is registered as a whole rather than registering every phone. Its Asterisk example uses sipconnect.sipgate.de, a SIP ID and password, and says registration is required for incoming calls. That confirms the model, not every production timer, transport, DNS decision or retry rule.
Preserve a sanitized REGISTER exchange, active contact, expiry and one inbound attempt. Then validate the complete Request-URI and authorized caller identity. The example says inbound calls carry the full dialed E.164 number in the Request-URI and uses P-Preferred-Identity for outbound caller ID; confirm both on the selected account rather than copying placeholders.
Do not mistake caller-ID fallback for call failover
sipgate's Fallbackrufnummer is a caller-ID fallback: the portal value is used when the PBX sends no acceptable outgoing calling number. It is not a reroute destination and does not make the registrar, access circuit, PBX or media path resilient.
Document the real continuity design separately: alternate targets, DNS behavior, triggers, timers, number redirection, established-call treatment and restoration. An online trunk indicator or an accepted caller identity does not prove that a new call will survive an access or PBX failure.
Preserve the explicit unencrypted service boundary
sipgate's current trunking help explicitly says TLS/SRTP protection between the customer PBX and sipgate servers is not available and that an infrastructure extension is not planned. Do not turn a private LAN, strong SIP password or unrelated HTTPS portal session into a claim that the SIP signaling or RTP leg is encrypted.
Record the exposed network path, restrict source and destination access, protect the credential, minimize capture retention and confirm whether this service design meets policy and regulatory requirements before activation. A different sipgate product's security capability does not change the trunking statement.
Keep channels, outbound labels and observed capacity separate
sipgate's current help record publishes tariff variants by usable channels and separately labels 100 outgoing calls. Those public labels do not define a universal call-start rate, burst window, PBX channel limit or media-bandwidth result. Bind each number to the current order and obtain the exact semantics before capacity planning.
The same separation applies to media. sipgate's Asterisk example lists several codecs, automatic DTMF and T.38 settings, but a template is not a negotiated call or delivered fax. Preserve offer, answer, payload mapping, decoded digits and representative fax results on the actual path.
Close emergency and commercial records in the account
The trunk detail page exposes an emergency-location field, but that does not prove a selected number is activated, that every endpoint maps to the correct location or that nomadic and outage cases are covered. Complete the current provider process, record callback identity and permitted test procedure, and retain an independently powered alternative path.
Likewise, public product and price pages are dated inputs rather than the accepted commercial record. Preserve the ordered tier, number and port charges, usage, destination rates, taxes, support, renewal and termination in a current quote, contract and bill.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- What is sipgate trunking? ↗
- Configure Asterisk for sipgate trunking ↗
- sipgate trunking TLS and SRTP status ↗
- sipgate trunking fallback caller ID ↗
- sipgate SIP Trunking ↗
- sipgate pricing ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.