Map each Commio object before testing a call
Commio documents outbound trunks, outbound routing profiles, inbound numbers, inbound routing preferences, E911 sites and port orders as separate objects. Record the account, trunk ID, authorized public source, optional prefix, selected outbound profile, number status, inbound preference and effective time before interpreting one call.
A saved portal object or ACTIVE label proves that object state only. It does not prove the PBX used the expected source address, prefix, route, identity or media path.
Documented service facts
Reviewed 2026-10-23. Compare SIP trunk services →
Authentication
DocumentedOutbound trunks authorize the observed public source IP and can use an optional four-digit Request-URI prefix. Portal propagation and actual acceptance remain separate evidence.
SIP registration
Not verifiedThe reviewed outbound path is source-IP authorized and does not establish REGISTER as a universal requirement. SIP URI is an inbound destination type, not proof of a provider binding.
Inbound delivery
DocumentedAn active number references an inbound routing preference with up to three ordered IP, DNS, PSTN or SIP URI destinations.
Inbound failover
DocumentedCommio documents ordered destination advancement, approximate no-response timers and response-specific handling. Preserve each attempt and recovery observation.
Number and regional availability
Not verifiedNumber inventory, portability, locality, account eligibility and current availability require a dated portal or written result.
Audio codecs
DocumentedThe technical FAQ publishes codec priorities and says media is not anchored, so RTP can arrive directly from a carrier. Confirm the selected SDP and packets.
T.38 fax
DocumentedThe technical FAQ lists G.729a, G.711u and T.38 for fax priority. This is documentation, not a completed fax result.
Signaling and media encryption
Not verifiedThe reviewed FAQ publishes UDP 5060 and a broad media range but does not establish one current encrypted signaling or media profile for every account.
Concurrent calls and call starts
Not verifiedConcurrency and CPS are predefined account values, while a trunk limit can be per Commio switch. Confirm purchased limits and exact rejection behavior.
Emergency calling
DocumentedE911 requires active inbound service, a Commio-network number, enabled E911, an associated site, matching ANI and approved source state. Use approved validation.
Pricing model
Not verifiedObtain dated account terms for numbers, calls, routes, E911, porting, support, taxes and fees. No price was tested or normalized.
Administration and support
DocumentedPortal objects expose trunk addresses, prefixes, number status, routes, features and port identifiers. Record object IDs, owners, timestamps and propagation state.
SMS and MMS
Not verifiedA number-management SMS toggle and campaign identifier do not establish sender registration, throughput, media limits, retention or price.
Authorize the observed public source and prefix exactly once
The outbound trunk page binds traffic to the public IP address of the sending switch and optionally a four-digit prefix prepended to the Request-URI user. Preserve the pre-NAT and translated sources, trunk record, prefix, destination digits, Request-URI and first Commio response.
A portal save can take three to five minutes to propagate. That documented interval is not proof that a particular edge accepted the change; observe the exact retried transaction and do not compensate for a wrong source by weakening PBX or firewall policy.
Keep inbound number state and routing preference separate
A Commio number can be not ready, unconfigured, not ported or active. The number must reference an inbound routing preference, while the preference can contain ordered IP, DNS A, DNS SRV, PSTN or SIP URI destinations. Preserve the number status, FOC state, assigned preference, destination type, address and provider attempt.
A configured number is not evidence that the first destination answered, the customer edge received the INVITE or the PBX selected the intended route. Follow one Call-ID across those boundaries.
Treat route advance as documented policy, not a guaranteed outcome
The routing article describes up to three ordered destinations, approximate three-to-four-second advancement when there is no signaling, immediate advancement for some responses and distinct handling for 486. Retain the first request, response or timeout, CANCEL, next attempt and final result with timestamps.
Do not collapse DNS service-node changes, inbound destination advancement, PBX forwarding and carrier selection into one failover claim. Recovery behavior and active-call survival require separate evidence.
Separate identity, media and capacity evidence
Commio documents P-Asserted-Identity, Remote-Party-ID and From priority for originating ANI. Its technical FAQ also publishes UDP 5060, direct-to-carrier RTP over a broad range, codec priorities and account-specific concurrency and call-start limits. Preserve the actual headers, SDP, selected codec, media source and packets in both directions.
Published defaults are not proof of one account entitlement or call. A SIP response does not prove answer, decoded audio, capacity headroom, fax completion or downstream caller-name display.
Version E911, porting and production acceptance independently
Commio requires an active inbound account, a number on its network, E911 enablement, an associated site, matching ANI and approved source addresses. Its current article directs routine validation to 933 and warns that a not-ported number is not yet provisioned. Preserve the address, site, number state, effective time and approved test evidence.
Port approval, FOC, number activation, E911 readiness, inbound routing and a successful production call are separate checkpoints. No emergency call or service result was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Commio outbound trunks ↗
- Commio inbound routing profiles ↗
- Commio technical FAQ ↗
- Commio originating ANI and jurisdiction ↗
- Commio E911 configuration and testing ↗
- Commio number configuration ↗
- Commio porting guide and best practices ↗
- Commio elastic SIP trunking ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.