Name the exact Vodafone voice service first
Vodafone’s current UK page presents Evolved Voice over Public Internet as a bring-your-own-access service and presents Hybrid Voice separately for retained ISDN30 PBXs through a gateway. Vodafone Business UC terms separately define Global SIP Trunking, while the current storm terms contain another SIP Trunking module. Preserve the ordered product name, legal entity, document version and service element before reusing any field.
A Vodafone logo, SIP label or shared corporate network does not make those offers interchangeable. The Hybrid data sheet’s ISDN30 presentation, the GSIP definition and storm customer-boundary clauses are separation evidence, not automatic Evolved Voice features.
Documented service facts
Reviewed 2026-10-25. Compare SIP trunk services →
SIP authentication
Not verifiedThe current public records do not establish one universal Evolved Voice registration, credential, IP-authentication or certificate model. The selected order, endpoint design and provider-issued parameters govern.
SIP registration
Not verifiedNo selected Evolved Voice REGISTER model or observed registration was established. Keep activation, endpoint reachability, OPTIONS, registration, number routing, answer and media separate.
Inbound delivery and identity
DocumentedVodafone says customers may retain existing numbers or obtain new ones, while the older Converged terms describe order-governed elements and a porting-authority process. Assignment, port completion, provider attempt, delivered identity and PBX route remain separate.
Endpoint diversity and diversion
DocumentedThe current Evolved Voice page describes end-to-end failover through Customer Endpoint Diversity and emergency diversion. Topology, health test, trigger, alternate selection, completed result and return to primary remain unverified.
Site and number availability
Not verifiedThe reviewed UK product page does not establish serviceability, access eligibility, number inventory, portability or lead time for a selected site. Retain dated qualification and order evidence.
Codecs, DTMF and RTP
Not verifiedNo current selected-order codec set, packetization, DTMF method, media range or transcoding policy was established. Hybrid-specific figures are not transferred to Evolved Voice; observed SDP and decoded media govern.
Fax
Not verifiedThe reviewed current Evolved Voice page does not establish fax entitlement, T.38, G.711 pass-through, gateway behavior or completed-page support for a selected order. Hybrid evidence is not transferred.
Signaling, media and fraud controls
DocumentedThe current page lists high-level encryption options and proactive fraud monitoring. Ordered enablement, certificate identity, signaling transport, SRTP coverage, alert thresholds and observed protection remain unverified.
Virtual lines and call starts
Not verifiedThe product page describes scalable virtual lines but does not establish a selected order’s channels, call-start rate, burst limit, PBX resources or access-bandwidth acceptance. Hybrid-specific measures are not transferred.
Emergency calling
DocumentedThe 2019 Converged terms require site-address accuracy, preserve site-to-number mapping for customer-managed PBXs and describe a soft-client location limitation. Current order and provider process govern applicable notice, effective state and approved testing.
Pricing and contract
Not verifiedNo selected-site price was established. Bind access, endpoints, virtual lines, numbers, usage, options, support, taxes, term and changes to the dated current order and bill.
Support and service boundaries
DocumentedVodafone publishes Foundation, Enhanced and Premium support tiers. The ordered tier, contacts, hours, severity, response, third-party responsibility and observed case history remain unverified.
SMS and MMS
Not verifiedThe reviewed Evolved Voice records do not establish messaging entitlement, sender registration, API access, throughput, webhook security, retention or price for trunk numbers. Treat messaging as a separate ordered service.
Bind bring-your-own access to the endpoint design
The current Evolved Voice page describes customer-provided access and end-to-end failover through Customer Endpoint Diversity. Record the ordered access, public addresses, edge devices, routing owner, endpoint diversity design and provider handoff independently. BYOA does not reveal one universal registration, static-IP, DNS, port or firewall model.
The current storm terms make the customer responsible for required network information and compliant third-party telephony systems for that separate service. Use that as a warning to establish the actual Evolved order and responsibility matrix rather than as a transferred technical specification.
Keep order, activation, numbers and call evidence distinct
Vodafone’s current page says customers can keep existing numbers or obtain new ones. The 2019 Converged terms say selected core and optional elements are set out in Commercial Terms or the Order and describe a porting-authority process where applicable. Requested, accepted, scheduled, ported, activated, routed and call-proven remain different states.
For each number, preserve the order reference, port or allocation evidence, effective time, intended endpoint, provider attempt, delivered identity, PBX route and result. A number listed in a portal or order is not proof that the current network attempted the expected edge.
Treat security, fraud and Teams labels as options
The current Evolved Voice page lists high-level encryption options, proactive fraud monitoring and Microsoft Teams calling when an enterprise Session Border Controller is present. Those labels do not establish enabled TLS, certificate identity, SRTP on every leg, alert thresholds, response ownership, Teams licensing, SBC configuration or successful calls.
Record each ordered option and its effective state, then verify DNS, clock, certificate, signaling transport, SDP security and actual media separately. A fraud alert is provider-published operational evidence, not proof of compromise or of the affected customer path.
Preserve capacity, failover and restoration states
The product page describes scalable virtual lines, endpoint diversity and emergency diversion but does not publish one selected order’s channels, call-start rate, diversity topology, trigger, alternate route or restoration timers. Keep virtual-line entitlement, concurrent dialogs, offered attempts, call starts, PBX resources and access bandwidth separate.
The Hybrid data sheet publishes Hybrid-specific channel and traffic measures. Do not transfer them to Evolved Voice. For continuity acceptance, record the trigger, primary evidence, alternate selection, provider attempt, completed result and proven return to primary.
Keep emergency location and support order specific
The 2019 Converged terms require accurate site-address information, preserve site-to-number mapping for customer-managed PBXs and warn that Vodafone cannot automatically determine the location of a user on a customer soft client. Those dated terms remain bounded evidence; the current order and provider process govern the applicable notice, address and testing requirements.
Do not place an uncoordinated emergency call. Preserve registered address, effective update, outbound identity, route, callback and alternate method. Vodafone publishes tiered support, but the selected tier, hours, contacts, severity, response and service scope require the order and an observed support record.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Vodafone UK — SIP trunking ↗
- Vodafone — Converged Hybrid/Evolved Voice Service Specific Terms v1.4 ↗
- Vodafone — Converged Hybrid Voice data sheet ↗
- Vodafone — Tiered Support Services brochure ↗
- Vodafone storm Service Specific Terms v2.3 ↗
- Vodafone Business UC with RingCentral Service Terms ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.