VoIP.infoThe independent guide to business communications.
VoIP.info Provider research

Vocus SIP Voice: service family, access and continuity evidence

Separate Vocus SIP Trunks, SIP Voice Connect and related offers before turning a product statement, schedule or diversion setting into account acceptance or tested continuity.

Reviewed 2026-10-28Current Vocus SIP Voice, SIP Trunks and SIP product records, the 27 April 2026 SIP Voice Connect and Australia Direct Unified Communications schedules, current legal index, support diversion guidance and service-level record were reviewed October 28, 2026. These records describe different service families and do not establish which product, agreement, order, access, PBX, signaling profile, authentication, registration, source trust, transport, codec, DTMF method, media range, encryption option, number state, emergency-location record, channel quantity, call-per-second allowance, continuity feature, service level, price, availability or compatibility applies to one customer. No Vocus account, quote, order, portal, circuit, router, PBX, SBC, credential, number, port, channel, packet, call, media stream, diversion, outage, emergency outcome, price, availability, compatibility, incident or support response was inspected or testedAdvancedDocumentation based · not lab tested

Identify the ordered Vocus voice service

Vocus publishes several related but different records. The current SIP Voice page describes business SIP connectivity, while the product overview distinguishes registered SIP Trunks from SIP Voice Connect and the April 2026 schedules govern named service families. Do not combine those records into one universal trunk profile.

Record the exact product name, customer class, service order, site, schedule version and implementation pack. A product page, current schedule or older data sheet is evidence about that record only; it is not proof that one account ordered the service or inherited every feature.

Documented service facts

Reviewed 2026-10-28. Compare SIP trunk services →

SIP authentication

Not verified

Product records distinguish registered SIP Trunks from SIP Voice Connect. The current order and implementation pack govern credentials, certificates or source trust.

SIP registration

Documented

The product overview describes SIP Trunks as registered and SIP Voice Connect as a SIP gateway. Account registrar, expiry, Contact policy and loaded state remain unverified.

Numbers and inbound delivery

Documented

Current schedules cover geographic numbers, service addresses, IPND and porting boundaries. One account number state, delivered format and completed route remain unverified.

Diversion and continuity

Documented

Vocus support describes whole-trunk Call Forward Always and Unreachable Destination controls. Entitlement, scope, target, trigger and completed calls remain unverified.

Access and service interface

Documented

SIP Voice Connect uses UC Access and an ordered service interface; product material also describes over-the-top SIP Trunks. The current order governs.

Signaling and media

Documented

The SIP Voice Connect schedule names SIP/RFC 3261 or RFC 3264 delivery and mandatory G.711 A-law. Other products and one observed call remain separate.

Fax and non-voice use

Not verified

The reviewed current records do not establish fax, T.38, modem, alarm or EFTPOS compatibility for one order.

Transport and media protection

Documented

The SIP Trunks data sheet describes optional TLS/SRTP for OTT SIP Trunks. It is not a universal or observed-call encryption claim.

Channels and call rate

Documented

SIP Voice Connect documents 60-channel minimums, 30-channel increments, limits and call-rate policy; SIP Trunks material describes a different range. The order governs.

Location and emergency evidence

Documented

Schedules describe fixed locations, service-address and IPND duties where applicable. One number location, alternate path and emergency outcome remain unverified.

Term, price and availability

Not verified

Rates, terms, feasibility and activation depend on the current order and governing records. Public material is not a current quote.

PBX, support and SLA

Documented

The schedules assign equipment and interface responsibilities and link to the Vocus SLA. Internet or third-party access can change SLA applicability.

SMS and MMS

Not verified

The reviewed Vocus SIP Voice records do not establish SMS or MMS on trunk numbers.

Bind access and demarcation to the product

The 2026 SIP Voice Connect schedule requires UC Access to the service interface and distinguishes a Vocus data-centre interface from one delivered to customer premises. The SIP Trunks data sheet instead describes an over-the-top option over a preferred network. These are different access models.

Preserve the ordered access, interface, cross-connect, router or SBC, IP addressing, routing, firewall and customer/provider responsibility boundary. Internet reachability, an active UC Access circuit or a reachable address does not prove that the SIP identity, numbers or media path is accepted.

Keep channels, call rate and media product-specific

The SIP Voice Connect schedule documents a minimum of 60 channels, increases in blocks of 30, endpoint and access limits, a capacity study above 500 channels, mandatory G.711 A-law and an outgoing call-per-second policy. The SIP Trunks product material describes a different 10-to-120-channel range, SIP registration and optional TLS/SRTP.

Apply each value only to its named product and current order. Ordered channels, call attempts per second, concurrent dialogs, bandwidth, PBX resources, codec negotiation and audible result remain separate measurements.

Treat numbers, location and porting as evidence

The SIP Voice Connect schedule describes geographic numbers as fixed-location services, requires current service-address information and says porting is not warranted. It also records IPND obligations where Australian numbers are supplied. The Australia Direct schedule separately governs SIP Trunks within its service family.

Retain allocation, port order, activation, IPND or service-address record, provider delivery, PBX receipt and route result separately. A number in a portal or a completed port step does not prove inbound delivery, outbound identity, emergency location or a completed call.

Prove diversion and continuity end to end

Vocus support guidance documents two SIP-trunk diversion controls in BroadSoft: Call Forward Always and an Unreachable Destination, with whole-trunk scope. That article does not establish that the current account, product or implementation uses BroadSoft, includes those controls, or has a tested target and restoration path.

Record the continuity feature, scope, trigger, control owner and target. Test through an approved plan that covers new calls, established calls, both media directions, number presentation, restoration and rollback. A saved diversion or secondary path is not proof of completed failover.

Keep SLA, security and commercial claims bounded

The legal index publishes current schedules and an SLA, while the SIP Voice Connect schedule states that its SLA does not apply when access uses the Internet or a third-party network. The public records also assign customer-equipment and password responsibilities and describe optional protection only for particular offers.

Obtain the current order, rate plan, feasibility result, SLA attachment, security profile and PBX approval. Do not infer price, site availability, compatibility, encryption, emergency behavior or support response from a marketing page or from another Vocus service.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Hub · Provider records reviewed individually on their listed dates; account-specific terms and availability require direct confirmation

SIP trunk provider research

Compare the connection model, call routing, media support and cost structure of documented SIP trunk services.

Explore topic →
Troubleshooting · Current Vocus SIP Voice, SIP Trunks and SIP product records, the 27 April 2026 SIP Voice Connect and Australia Direct Unified Communications schedules, current legal index, support diversion guidance and service-level record were reviewed October 28, 2026. These records describe different service families and do not establish which product, agreement, order, access, PBX, signaling profile, authentication, registration, source trust, transport, codec, DTMF method, media range, encryption option, number state, emergency-location record, channel quantity, call-per-second allowance, continuity feature, service level, price, availability or compatibility applies to one customer. No Vocus account, quote, order, portal, circuit, router, PBX, SBC, credential, number, port, channel, packet, call, media stream, diversion, outage, emergency outcome, price, availability, compatibility, incident or support response was inspected or tested

Vocus SIP Voice access, channel, number or continuity path fails

Find the first divergence across the ordered Vocus product, schedule, access, interface, PBX, channels, numbers, signaling, media and diversion path.

Read guide →
Guide

SIP trunking: numbers, capacity and operational control

Plan the carrier relationship that connects a self-managed PBX to outside calling.

Read guide →
Guide

SIP trunk channels and simultaneous calls

Size external capacity around busy-hour demand and the provider’s counting rules.

Read guide →
Guide

SIP trunk failover and redundant calling paths

Design alternate routing without assuming active calls will survive.

Read guide →
Guide

Firewall rules for VoIP

Define management, signaling and media access separately using actual deployment requirements.

Read guide →
Guide

NAT for VoIP: signaling and media addresses

Map each translation boundary and compare advertised destinations with reachable addresses.

Read guide →
Guide

QoS for VoIP

Apply prioritization where you control the bottleneck and understand what happens beyond it.

Read guide →
Guide

PBX credentials and extension secrets

Keep administrator, handset, trunk and backup identities separate and retire them deliberately.

Read guide →
Guide

Planning emergency calling for a VoIP deployment

Assign responsibility for location, routing and outage procedures before rollout.

Read guide →
Guide

Business number porting: a cutover checklist

Keep ownership records, dependencies and a fallback plan aligned with the gaining provider’s process.

Read guide →
Guide · Wireshark 4.x / current upstream tool documentation; inspect installed versions

VoIP packet-capture methodology

Select interfaces, time windows and paired capture points that distinguish network loss from missing evidence.

Read guide →
Guide · FreePBX 17 and current Asterisk res_pjsip documentation reviewed October 5, 2026; Sangoma's generic module pages are responsibility guides rather than an exact installed field map; no FreePBX host, module, account, credential, trunk, route, registration, number, identity, call, media path, failover, capacity, emergency workflow or compatibility was tested

Configure and verify a FreePBX 17 PJSIP trunk

Translate current carrier requirements into FreePBX-owned PJSIP trunk, route and identity controls, then verify the generated Asterisk objects and each call direction independently.

Read guide →
Guide · Current Asterisk PJSIP object, outbound-registration, configuration-example and res_pjsip references reviewed October 1, 2026; no account, carrier, PBX, endpoint, registration, identifier, route, call, emergency workflow, media stream, capacity or failover path was tested

Plan and configure an Asterisk SIP trunk

Translate each carrier direction into explicit PJSIP objects, identification, restricted dialplan, retry policy and leg-by-leg acceptance evidence.

Read guide →
Troubleshooting · Current SIPTRUNK IP-authentication, registration, status, inbound-call, failover, interconnection and general-configuration documentation reviewed October 14, 2026; the sources describe mutually exclusive credential-registration and static-public-IP modes but do not prove the selected account mode, public address, gateway resolution, Contact, registration, number assignment, route, failover treatment, capacity, compatibility or completed call, and no account, portal, credential, PBX, firewall, DNS answer, packet, registration, number, route, failover event, media stream or live call was inspected or tested

SIPTRUNK registration or IP-authentication mode does not match the call path

Determine whether the trunk uses credential registration or static-IP authentication, then trace the exact public address, gateway, Contact or stored destination, provider state, inbound route and failover treatment.

Read guide →
Troubleshooting · First-party Asterisk documentation and SIP standard reviewed September 30, 2026; FreePBX 17 terminology retained; no PBX, provider, number, route or live call test

Inbound VoIP calls do not reach the business

Trace carrier delivery, Asterisk endpoint identification, DID matching and the final destination without collapsing the boundaries.

Read guide →
Troubleshooting · Current Sangoma outbound-route guidance, current Asterisk Dial and troubleshooting documentation, and SIP standards reviewed October 5, 2026; no phone, PBX, carrier or live call test

Outbound VoIP calls fail: locate the broken call leg

Classify one failed call, then follow the exact digits through the phone, PBX route, attempted trunk, remote response, answer and media.

Read guide →
Troubleshooting · Asterisk 22 LTS · FreePBX 17 / Debian 12 checks

VoIP call connects but has no audio

Separate endpoint audio selection from a media path that fails in both directions.

Read guide →
Hub

VoIP troubleshooting

Use symptoms and evidence to isolate registration, routing, media and device faults.

Explore topic →