Freeze the ordered location and current PBX boundary
Intermedia defines a SIP Trunking location as the address where the PBX resides; two phone systems at the same physical address can appear as separate locations. Preserve the account location, trunk or trunk group, phone numbers, PBX or gateway, software release, public addressing, implementation record and current support owner. A shared street address or similar portal nickname is not proof that two systems use the same route.
Intermedia distinguishes direct connection for an interworked IP PBX from a gateway path for analog, digital or non-interworked systems. Its configuration guides were produced by partners and are not actively maintained, while the certified-PBX page says the extent of testing varies. Treat both as starting evidence, not current certification for an arbitrary maintenance release.
Documented service facts
Reviewed 2026-10-20. Compare SIP trunk services →
Outbound authentication
Not verifiedThe reviewed public trunk pages do not define one account's source-IP or digest-authentication contract, credential lifecycle or accepted outbound identities. Obtain the current implementation record and preserve secrets outside shared traces.
SIP registration
Not verifiedIntermedia's broad service port table covers hosted-platform SIP registration, but that does not establish REGISTER behavior for a SIP Trunking order. Confirm the trunk-specific target, transport, identity, refresh and health signal before interpreting registration state.
Inbound delivery
DocumentedHostPilot organizes trunks by PBX location and assigned phone numbers. Keep location, number assignment, arriving INVITE, PBX route and final destination separate; a portal number is not evidence of accepted delivery.
Inbound failover
DocumentedIntermedia documents per-number failover to an alternate ten-digit destination when a location is detected as unavailable, with continued monitoring and restoration to the original route. The public pages do not enumerate the complete probe, response, timer or established-call contract, so perform a bounded account-specific test.
Number and regional availability
Not verifiedThe product and overview pages describe local, toll-free, remote-market and international DIDs, but they do not prove inventory, portability, address eligibility or serviceability for one account. Require a dated result for every number and site.
Audio codecs
Not verifiedThe reviewed service pages and multi-product port table do not establish one SIP Trunking order's codecs, packetization, DTMF or media endpoints. Retain the actual SDP offer and answer, payload mapping, RTP endpoints and application result.
T.38 fax
Not verifiedThe reviewed trunk pages do not establish T.38 or voice-band fax behavior for one order. Qualify exact direction, number, gateway, document set, error correction, switchover and fallback separately.
Signaling and media encryption
Not verifiedIntermedia lists SecureSIP and SRTP for hosted services in a broad port table, but that does not prove TLS, certificate validation, SRTP, keying or downgrade behavior on one trunk. Obtain trunk-specific parameters and verify both negotiated legs.
Concurrent calls and burst
Not verifiedThe product page promotes scalable channels and bursting, but the reviewed sources do not establish purchased concurrency, burst policy, call-start rate, rejection behavior or PBX capacity. Obtain the current order and perform only a bounded acceptance test.
Emergency calling
DocumentedHostPilot distinguishes a default 911 number for a PBX location from a dedicated number for a remote phone and requires the phone system to send that dedicated identity. Confirm physical address, eligible caller ID, callback and the provider-approved test path for every endpoint location.
Pricing model
Not verifiedThe public pages describe flexible pricing but do not establish one account's current charges. Obtain a dated quote covering locations, channels, bursting, numbers, usage, failover, E911, porting, support, taxes, commitments, renewal and termination.
Administration and support
DocumentedHostPilot exposes location, phone-number, caller-ID, 911, failover, call-history and QoS views. Location and number history have different scopes, outbound visibility can depend on PBX configuration, and jitter statistics are retained for seven days. Preserve query scope and correlate portal evidence with the PBX and packets.
SMS and MMS
Not verifiedThe reviewed SIP Trunking sources do not establish SMS or MMS entitlement on trunk-assigned numbers. Verify number capability, sender registration, consent controls, application path, throughput, retention and fees separately.
Keep the DID, location and caller identity independently observable
HostPilot exposes locations and their associated phone numbers. Keep number inventory, assignment to the ordered location, provider attempt, customer-edge receipt, Request-URI, PBX identification, inbound-route match and final destination as separate evidence. A DID visible beneath a location does not prove that a specific call reached or was accepted by that PBX.
Location-level and phone-number-level outbound caller-ID controls also remain separate from the identity actually sent by the PBX. Intermedia says the portal value is used only when the phone system sends no outbound caller ID and limits the value to a number assigned to the company. Capture the emitted identity and provider result before changing a fallback field.
Treat per-number failover as a monitored new-call route
Intermedia documents failover on each phone number to an alternate ten-digit destination when its customer location is detected as unavailable, followed by restoration when monitoring sees recovery. Record the DID, normal location, configured alternate, provider-visible availability state, trigger time, resulting destination, call detail and restoration time.
The public pages do not enumerate every monitoring probe, response code, timeout, retry interval, precedence rule or established-dialog outcome. Treat failover as a bounded new-inbound-call control until the current account contract and an authorized test establish more. A mobile number, remote PBX, alternate data centre and hosted voicemail have different dependencies and acceptance criteria.
Use call history and QoS as correlated records, not delivery proof
HostPilot can show call history by location or phone number and notes that outbound calls may or may not appear depending on PBX configuration. Its QoS tool summarizes connected calls and can expose route, jitter, round-trip delay and packet-loss views, with jitter statistics retained for only seven days. Preserve the query scope, export time, displayed leg, timestamps and retention limit.
A portal row does not prove that the customer edge received the request, that the PBX selected the intended route or that a person heard usable audio. Correlate the portal record with provider and PBX Call-ID where available, packet capture, SIP result, SDP, both media directions and an authorized endpoint observation.
Map each emergency identity to its physical address and PBX rule
HostPilot distinguishes one default 911 number for a SIP Trunking location, a dedicated 911 number for a remote phone and numbers without their own 911 icon. Intermedia says the PBX must send the dedicated number as caller ID for the corresponding address to reach the emergency operator. Preserve physical location, accepted portal address, eligible caller identity, PBX selection rule and callback route together.
The general emergency-policy page says emergency behavior may differ by location and that registered addresses must be updated when service moves. Portal coverage confirmation is administrative evidence, not a completed emergency call or dispatch record. Follow the provider's approved non-live verification process and maintain an independently validated fallback.
Version media, protection, capacity and commercial claims
Intermedia publishes broad port information across several voice services, including SIP, SecureSIP, RTP and SRTP, but that is not one trunk firewall or protection profile. Obtain the current account peers, transport, certificate policy, media ranges, codecs, packetization, DTMF and fax behavior, then verify the actual signaling and negotiated media legs.
The product page describes scalable lines, plans and automatic failover, while older support material contains dated bundles and minimums. Require a current quote and order for locations, concurrency, burst treatment, numbers, porting, E911, usage, support, taxes, commitments and termination. No Intermedia service behavior was laboratory validated for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Intermedia SIP Trunking product page ↗
- Intermedia SIP Trunking overview ↗
- Intermedia SIP Trunking HostPilot overview ↗
- Intermedia SIP Trunking failover routing ↗
- Intermedia PBX configuration guides ↗
- Intermedia service and configuration port information ↗
- Intermedia certified PBX list ↗
- Intermedia emergency 911 policy and information ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.