Start with the current order and local demarcation
Cox's current page describes SIP Trunking as connecting an existing PBX to voice service and links to a certified-PBX support page. Cox-hosted Asterisk, Avaya and CIC guides show a provider-managed EdgeMarc E-SBC as the local demarcation in their older reference topologies. Preserve the current order, access circuit, E-SBC ownership, LAN address, PBX or SBC peer, source policy and support boundary before translating any example.
Those guides name obsolete PBX releases and lab addresses. Their diagrams explain evidence boundaries; they do not certify a current Asterisk, FreePBX, Avaya or other deployment. Obtain the present implementation worksheet and record the assigned values rather than copying example addresses, credentials, codecs, timers or legacy channel-driver syntax.
Documented service facts
Reviewed 2026-10-20. 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
DocumentedCox-hosted 2011–2012 PBX-specific guides use a trunk-group pilot or billing telephone number plus a provider-issued secret for REGISTER through a local E-SBC. That is historical reference evidence, not a current universal interface contract. Preserve the current worksheet, challenge, final response, Contact and expiry.
Inbound delivery
DocumentedPilot or BTN registration and DID delivery are separate. The old Avaya guide creates an incoming call route for each DID and uses To-header indexing in that release. Preserve current assignment, Request-URI, To, source E-SBC, PBX identification, normalization and first loaded route.
Routing and failover
DocumentedOlder guides distinguish Call Forward Always, Call Forward Not Reachable, Route Exhaustion and geo-redundant PBX routing; provider-core diversity is another layer. The current page does not publish one universal trigger, timer, retry-code matrix, precedence or restoration sequence.
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
DocumentedUse the current product and certified-PBX pages to identify today's service and support boundary, then obtain the current implementation worksheet. The archived PBX guides remain product-, release- and topology-specific evidence rather than current certification or universal configuration.
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.
Separate the pilot or BTN from every delivered DID
The Asterisk and CIC references use a trunk-group pilot number as the registration username, while the Avaya guide calls the same role a pilot or billing telephone number in its registration field. Separately, the Avaya guide creates an incoming call route for every DID in the PBX inventory and says its To-header routing method is needed for DID indexing in that release.
A successful REGISTER for the pilot identity therefore does not prove that a particular DID is assigned, delivered, normalized or matched by the PBX. Preserve the redacted registration identity, final response, Contact and expiry; then preserve the called DID, Request-URI, To, source E-SBC, first PBX response, trunk or endpoint identification, context and first loaded inbound route.
Keep old PBX behavior scoped to its exact release
The 2011 Asterisk guide targets Asterisk 1.8.7 and uses chan_sip; the Avaya reference targets IP Office 6.0 with Manager 8.0; the CIC reference targets release 3.0 SU13. Their registration, header, codec, DTMF, transfer, fax and caveat findings belong to those documented combinations. They are not a current PJSIP or FreePBX template.
For a current Asterisk or FreePBX system, model the accepted handoff with supported PJSIP endpoint, auth, AoR, registration and identify objects. Confirm the effective generated configuration, current security controls and an authorized trace. A provider page that names Asterisk does not establish compatibility with every branch, module, appliance or customization.
Distinguish provider continuity controls from PBX recovery
The older guides describe Call Forward Always, Call Forward Not Reachable on the trunk-group pilot, Route Exhaustion to a PSTN number and support for a geo-redundant PBX deployment. They also show diverse E-SBC paths toward provider SBCs. These are different layers: a forwarded PSTN leg, provider route exhaustion, a backup data-center trunk, provider-core diversity and a repaired primary PBX do not prove one another.
The current page advertises call redundancy and downtime protection but does not publish one universal trigger, retry-code matrix, timer, precedence rule, restoration sequence or established-call result. Bind each configured control to the current order, destination and provider-approved test. Record only the observed new-call transition.
Validate signaling, media, fax and emergency separately
The old references include combination-specific G.711 mu-law and RFC 2833 results, while fax evidence differs: the Avaya guide contains T.38 configuration but marks T.38 unsupported for that tested version, and the Asterisk exercise says fax was not tested. Treat those records as historical scope, not a current entitlement. Preserve actual SDP, negotiated payloads, RTP endpoints, digit events, decoded audio and fax transition for authorized representative calls.
The Asterisk guide includes E911 in its lab feature list, while the current product page places emergency-locator language under PRI Trunking. Do not transfer either statement into a current SIP emergency procedure. Obtain the assigned emergency identity, dispatchable address, callback route and approved test process; do not place an uncoordinated emergency call.
Bound serviceability, capacity, pricing and proof
The current page says SIP Trunking is available in many areas, portability is supported in most markets, capacity can scale in real time and pricing is customized. Those statements do not prove serviceability, number eligibility, port completion, current sessions, burst entitlement, price or availability for one account. Preserve dated order, port, quote and service-level evidence.
Voice utilization reporting and a support ticket are provider-side records, not proof of customer-edge receipt, PBX routing, answer or two-way media. Confirm each boundary independently and keep secrets redacted. No account, pilot, DID, E-SBC, registration, route, continuity event, media path, emergency workflow, price, availability or compatibility was 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 SIP Trunking certified PBX systems ↗
- Cox Business Asterisk 1.8.7 configuration guide ↗
- Cox Business Avaya IP Office 6.0 configuration guide ↗
- Cox Business Interactive Intelligence CIC configuration guide ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.