Start with the ordered demarcation
Cox's current product page positions SIP Trunking as an IP connection between telephone service and an existing customer PBX. Cox-hosted reference guides show a local provider E-SBC as the demarcation for their documented Asterisk 1.8.7 and Avaya IP Office topologies. Record the exact ordered access, E-SBC ownership, LAN handoff, peer addresses, routing responsibility and support boundary before selecting a PBX template.
Those guides describe registration with a trunk-group pilot number and a provider-issued secret, but they are versioned reference configurations rather than a current universal interface contract. Use the implementation worksheet for the actual order. Never copy example numbers, passwords, private addresses, timers or legacy channel-driver syntax into production.
Documented service facts
Reviewed 2026-10-06. Compare SIP trunk services →
SIP authentication
DocumentedCox-hosted Asterisk 1.8.7 and Avaya IP Office guides describe digest credentials based on a trunk-group pilot number plus a provider-issued secret. They are old, PBX-specific reference configurations, not a current universal credential contract. Obtain the implementation worksheet and protect the supplied secret; never copy example values.
SIP registration
DocumentedThe Cox-hosted Asterisk 1.8.7 guide says its reference service requires SIP REGISTER through a Cox E-SBC and uses a provider-supplied pilot number and key. That evidence is tied to the documented legacy topology. Verify the ordered service, current PBX, registration interval, transport, E-SBC address and source restrictions before deployment.
Inbound delivery
DocumentedThe current product page describes SIP Trunking as connecting an existing PBX to telephone service, while the PBX guides route assigned DIDs through a local Cox E-SBC into PBX destinations. Keep number assignment, E-SBC peer, delivered called identity, PBX match and final destination as separate evidence.
Routing and failover
DocumentedCox advertises call redundancy, downtime protection, business continuity and real-time capacity changes. The Asterisk reference topology also shows an E-SBC with diverse routes to primary and secondary provider SBCs. These statements do not prove the customer's access diversity, retry rules, route order, restoration behavior or survival of established calls; obtain the ordered design and test only approved new-call failures.
Number and regional availability
DocumentedThe current page says SIP Trunking is available in many areas and that number portability is supported in most markets. Neither statement establishes serviceability, current inventory, port eligibility, identity rights or regulatory approval for a specific address and number. Use dated serviceability and port-order results.
Audio codecs
DocumentedThe Cox-hosted Asterisk 1.8.7 guide lists G.711 mu-law as tested and presents A-law and G.729 in its example trunk configuration, while the Avaya guide specifies G.711 mu-law and RFC 2833 DTMF for that platform. These are legacy PBX-specific findings, not a current universal codec list. Obtain the current interface specification and preserve the actual SDP offer, answer and decoded result.
T.38 fax
Not verifiedThe Avaya IP Office guide documents a T.38 configuration but explicitly says to confirm regional availability with Cox. The Asterisk 1.8.7 guide says fax was not tested in that reference exercise. Confirm entitlement, gateway mode, switchover, codecs, page profile and delivery report for the exact order instead of transferring the Avaya settings.
Signaling and media encryption
Not verifiedThe reviewed current product page and legacy PBX guides do not define one customer-facing SIP TLS hostname, certificate-validation workflow, SRTP profile or downgrade policy. A private provider network, E-SBC or managed demarcation does not itself prove application-layer encryption. Obtain the current security schedule and inspect each PBX-facing leg.
Concurrent calls and call starts
Not verifiedCox says capacity can scale in real time, but the reviewed public sources do not publish one numeric active-call, burst or calls-per-second limit. Purchased sessions, concurrent calls, call starts, PBX channels, E-SBC resources and access bandwidth remain different quantities that require order and acceptance evidence.
Emergency calling
Not verifiedThe legacy Asterisk guide includes E911 among tested reference features, and the current page describes an emergency locator under PRI Trunking rather than clearly assigning it to SIP Trunking. Neither establishes the current SIP order's address workflow, caller identity, callback behavior or approved test process. Obtain the applicable emergency-service terms and provider-approved test method.
Pricing model
Not verifiedCox states that SIP Trunking pricing varies and directs customers to request a tailored plan. Obtain a dated quote or contract for sessions, minutes, numbers, porting, access, E-SBC or equipment, emergency service, support, minimums, taxes, renewal, service levels and cancellation.
Administration and support
DocumentedThe current page advertises professional installation, 24/7 support, custom configuration guides, online feature management, utilization reporting, robocall protection and optional Dubber call recording. Availability of those operational features can depend on the order; portal state, installed configuration, provider acceptance and successful calls remain separate evidence.
SMS and MMS
Not verifiedThe reviewed Cox SIP Trunking product page and PBX guides do not establish SMS or MMS entitlement on trunk numbers, API access, sender registration, throughput, webhook security or price. Do not transfer messaging features from hosted voice or collaboration products to a PBX-facing trunk.
Keep current service claims separate from legacy PBX evidence
The current page advertises PBX integration, real-time scaling, multi-site connectivity, call redundancy, utilization reporting, robocall protection, optional call recording, professional installation and 24/7 support. The Asterisk guide is explicitly for Asterisk 1.8.7 and the Avaya guide is tied to a particular IP Office generation. Their lab topologies and tested features do not prove current compatibility, settings or service behavior.
Use each guide to understand what must be specified—demarcation, registration, identity, inbound matching, media and acceptance—not to certify a modern PBX. For FreePBX or current Asterisk, translate the ordered interface into supported PJSIP objects and current security controls, then validate with Cox rather than reproducing old chan_sip examples.
Separate signaling, media and fax acceptance
The Asterisk reference lists G.711 mu-law among tested features and shows A-law and G.729 in an example configuration; the Avaya guide specifies G.711 mu-law and RFC 2833 DTMF. These details are platform- and era-specific. Preserve the current SDP offer and answer, DTMF behavior, media addresses, decoded audio and one-way-audio checks for the exact PBX and route.
Fax evidence is deliberately mixed: the Avaya guide documents T.38 settings but says to confirm regional support, while the Asterisk exercise says fax was not tested. Confirm the current entitlement and gateway behavior for the intended fax path. A successful SIP registration, ordinary voice call or old configuration screenshot does not prove fax delivery.
Turn resilience language into testable controls
Cox advertises call redundancy, downtime protection and business continuity. Its Asterisk reference topology shows an E-SBC with diverse routes toward primary and secondary provider SBCs. Provider-core diversity is not the same as an independent customer access circuit, alternate PBX destination or a verified route around a failed local E-SBC.
Obtain the service-level schedule, route order, retryable responses, timers, alternate destination, restoration procedure and ownership for each failure domain. Test approved new-call scenarios and keep established-call survival as a separate result. Do not report availability or failover success from architecture language alone.
Validate serviceability, emergency terms and total cost
Cox says the service is available in many areas, supports number portability in most markets and uses custom pricing. Use dated serviceability, port-order and quote evidence for the exact address, number type and market. Separate trunk sessions, minutes, numbers, access, equipment, emergency service, support, taxes, renewal, cancellation and service-level terms.
The Asterisk reference includes E911 in its tested feature list, but the current page's emergency-locator text appears under PRI Trunking. Do not transfer that wording to every SIP order. Obtain the applicable address, caller-identity, callback and approved-test workflow. The reviewed sources do not establish messaging entitlement or protected SIP media. No account, quote, contract, service address, trunk, number, port, E-SBC, PBX, route, call, media stream, fax, protected session, failover event, emergency workflow, message, availability, price or support response was inspected or tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Cox Business Voice Trunking ↗
- Cox Business Asterisk 1.8.7 configuration guide ↗
- Cox Business Avaya IP Office configuration guide ↗
- Cox Business certified PBX systems ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.