Start with direction and identity
Commio's reviewed outbound workflow authorizes traffic by the source IP entered on a trunk. An address change must be reflected in the portal, and the guidance warns that changes can take several minutes to propagate. Preserve the PBX or SBC egress address, trunk object, routing profile and dialed identity in the change record.
Inbound service uses a routing profile assigned to a number. That profile can deliver to an IP address, DNS A or SRV record, PSTN number or SIP URI. The reviewed material does not establish a Commio registrar binding used by the PBX as the trunk identity. Do not select a credential-registration template merely because one PBX screen expects a registration state.
Documented service facts
Reviewed 2026-09-27. Compare SIP trunk services →
Authentication
DocumentedCommio documents outbound trunks by permitted source IP. A changing public address must be updated in the portal, and multiple source addresses are represented by additional trunks. Preserve the exact egress address and propagation delay rather than substituting a credential-registration template.
SIP registration
Not verifiedThe reviewed outbound guidance authenticates by source IP, while inbound routing can target a SIP URI when a receiving switch requires registration. It does not document a Commio registrar binding used by the customer's PBX as the trunk identity. Confirm the selected direction and account workflow instead of waiting for an assumed REGISTER state.
Inbound delivery
DocumentedAn inbound routing profile must be assigned to a number. The profile can target an IP address, DNS A or SRV record, PSTN number or SIP URI, with the first entry primary and as many as two backup entries. Record number assignment, target type, port, identity handling and permitted source addresses for the actual route.
Inbound failover
DocumentedCommio documents up to three ordered inbound destinations. It advances immediately on most responses other than 486, and after roughly four seconds when a destination gives no signaling response. Confirm the behavior of every intended failure response and restoration; this routing policy does not establish preservation of active calls.
Number and regional availability
DocumentedThe portal can search and purchase domestic local and toll-free numbers by NPA, NPA-NXX or rate center, including contiguous-block and back-order requests. Inventory, portability, activation timing, address requirements and voice or messaging capabilities remain specific to the number and transaction.
Audio codecs
DocumentedCommio's technical FAQ lists G.711 mu-law first and G.729a second for voice, documents RFC 2833 out-of-band DTMF and says media is sent directly to the selected carrier rather than anchored by Commio. Preserve the actual SDP, negotiated codec and observed media addresses for each route.
T.38 fax
DocumentedThe technical FAQ lists G.729a, G.711 mu-law and T.38 in its fax codec order. That general statement does not prove T.38 availability or pass-through on a particular carrier, DID, direction, gateway or page profile. Qualify the exact path and keep a fallback decision explicit.
Signaling and media encryption
Not verifiedThe reviewed technical guidance documents SIP over UDP on port 5060, source-IP authorization and direct carrier media. It does not establish a TLS or SRTP procedure for this service. Treat firewall rules as access controls, not encryption, and confirm any protected-signaling or protected-media option in writing before production use.
Concurrent calls and call starts
DocumentedCommio says concurrency and calls per second are controlled separately and can be adjusted to customer needs. A trunk can also have its own channel limit, described as per Commio switch rather than a simple account-wide ceiling. Obtain both effective limits and an authorized burst-test plan; do not derive one from the other.
Emergency calling
DocumentedCommio documents an active inbound account and ANI, a Commio-network DID with E911 enabled, a linked site address and authorized source IPs as parts of the 911 path. It publishes 711 as a read-back and two-way-audio check and instructs customers to coordinate live 911 tests with local authorities. Follow the current approved procedure; ordinary calling is not proof of emergency readiness.
Pricing model
DocumentedCommio's public pricing entry requests a custom quote, while its routing documentation describes account rate decks, per-minute maximums and route selection. Price the exact destination and number mix from the effective account terms, including billing increments, number rental, carrier or regulatory charges, emergency service and messaging fees.
Administration and support
DocumentedThe portal manages source-IP trunks, routing profiles, numbers, E911 data and messaging activation. Commio publishes active-support hours plus an after-hours hard-down escalation path, but those contacts do not establish an SLA or resolution time. Export applied configuration and keep PBX evidence, call examples and provider tickets together.
SMS and MMS
DocumentedCommio documents activating SMS on an eligible DID, creating an API token, configuring messaging IP allowlists and receiving inbound messages; its FAQ also describes MMS payload behavior. Confirm number capability, registration, consent, throughput, content, callbacks, retention, carrier fees and ownership separately from voice routing.
Test inbound advancement response by response
An inbound profile can hold a primary and two backup destinations. Commio says it advances immediately on most responses other than 486 and waits about four seconds when a destination produces no signaling response. That is a specific routing policy, not a generic promise that every failure will reach the next PBX.
Pilot the exact responses your maintenance and outage states produce. Record the destination attempted, elapsed time, response and selected backup, then verify restoration. This protects new attempts; the documentation does not claim that calls already established survive a route change.
Keep signaling, media and fax evidence distinct
The technical FAQ documents SIP over UDP 5060, G.711 mu-law and G.729a voice priorities, RFC 2833 DTMF and direct media between the endpoint and selected carrier. Commio's INVITE examples show the corresponding SDP forms. Preserve a real offer, answer and media trace because route choice can affect the path.
The same FAQ lists T.38 in its fax guidance, but that does not prove support across every carrier, number, gateway or page profile. It also does not establish TLS or SRTP. Qualify fax and encrypted transport independently instead of inferring either from an ordinary completed voice call.
Measure channel and call-start controls separately
Commio states that concurrent-call and calls-per-second limits are separately set for customer needs. Its trunk article adds that a configured channel limit is per Commio switch and can result in more active calls when load is spread across switches. Record the effective account, trunk and route controls rather than treating one visible number as a universal ceiling.
Use an authorized bounded test plan with an agreed stop condition. Outbound routing profiles can advance among selected carriers using rate and post-dial-delay conditions, but route diversity does not establish destination quality or a guaranteed capacity figure.
Verify numbers, E911 and messaging per DID
The portal searches domestic local and toll-free inventory by NPA, NPA-NXX or rate center. Treat each result as a dated inventory observation; portability, activation and capability remain transaction-specific.
For E911, Commio documents an active inbound account and ANI, a DID on its network with E911 enabled, a linked site address, permitted switch IPs and a specific route. It offers 711 as a read-back and audio check and advises coordinating live 911 tests with local authorities. Messaging is separately activated on eligible DIDs and uses API tokens plus IP allowlists. Neither feature follows automatically from ordinary voice service.
Price the account and preserve an operational record
The public site directs buyers to request pricing, while the portal guidance refers to account rate decks, maximum per-minute rates and carrier selection. Obtain a quote for the exact destination, number, emergency and messaging mix and preserve billing increments, pass-through charges, taxes, minimums and support terms.
Before cutover, export the source-IP trunks, outbound profiles, number assignments, inbound destinations, emergency records and messaging configuration. Keep approved rollback targets and provider support cases with PBX traces. No Commio account, trunk, number, call, media, fax, encrypted transport, emergency call, message, rate, availability 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.
- Commio Technical FAQs ↗
- Commio outbound trunks ↗
- Commio inbound routing profiles ↗
- Commio SIP INVITE examples ↗
- Commio number search and ordering ↗
- Commio E911 portal workflow ↗
- Commio E911 service overview ↗
- Commio outbound routing profiles ↗
- Commio pricing request ↗
- Commio support ticket and escalation guide ↗
- Commio SMS and MMS FAQ ↗
- Commio messaging overview ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.