Identify the exact Voiceflex service and order
Voiceflex presents SIP trunking, International SIP Breakout, automatic failover, call recording and other voice services as related but distinct capabilities. Record the legal account, ordered product, countries, number inventory, ports, channel entitlement, PBX or SBC, support path and current technical pack before selecting a configuration template.
A public feature page does not establish that an option is included in the selected order, available for a requested country or compatible with a specific PBX. Preserve the dated order, provisioning sheet and observed portal state separately.
Documented service facts
Reviewed 2026-10-11. Compare SIP trunk services →
SIP authentication
Not verifiedVoiceflex describes connecting a PBX to its SIP service, but the reviewed public pages do not establish one registration, digest-credential or source-IP authentication method for every order. Obtain the current provisioning sheet and record direction, SIP identity, authorization identity, source address or FQDN, challenge and observed response without treating the methods as interchangeable.
SIP registration
Not verifiedThe failover page says Voiceflex can monitor whether a PBX responds or regularly registers, which shows that registration may be relevant to a configured service but does not make REGISTER mandatory for every trunk. Confirm the ordered mode, registrar, proxy, transport, Contact, expiry, refresh and response from the account-specific technical pack.
Inbound delivery and number format
Not verifiedVoiceflex documents UK and international number supply, porting and inbound PBX connectivity. The reviewed pages do not publish a universal Request-URI, number format, source range, destination port or identity-header contract. Retain the assigned number, port result, delivery target and observed SIP message for every route.
Inbound resilience
DocumentedVoiceflex describes optional automatic failover that sends calls to another PBX when the primary PBX does not respond or regularly register. It states that failover is configured at SIP-account level rather than individual-number level. This does not establish detection timing, restoration timing, active-call survival, capacity or caller-identity behavior; qualify new-call routing and return to primary with an approved test.
Number and regional availability
Not verifiedThe SIP product page advertises UK and international numbers and porting, while International SIP Breakout separately describes local numbers and porting in supported countries. Those statements do not prove that every country, rate centre, number type, address or existing number is available or portable on a given date. Obtain a dated inventory or port result for the exact legal entity and service address.
Audio codecs and DTMF
Not verifiedThe reviewed public product, FAQ and failover pages do not establish a codec list, packetization interval, DTMF method, RTP address range or media-latching behavior for the ordered trunk. Obtain the current technical pack and preserve the actual SDP offer and answer, telephone-event mapping, RTP endpoints and decoded result.
Fax and T.38
Not verifiedThe reviewed public pages do not establish T.38 support, audio-fax fallback, direction, gateway interoperability or document limits for the SIP trunk. Qualify fax separately using a provider-approved representative document set, and do not infer support from ordinary voice completion.
Signaling and media encryption
Not verifiedVoiceflex describes fraud controls as part of its service portfolio, but the reviewed public pages do not establish TLS, certificate, SRTP, keying or IP-filter requirements for the ordered customer-facing trunk. Treat fraud monitoring, SIP authorization, signaling confidentiality and media confidentiality as separate controls and verify each from the current technical pack and observed session.
Concurrent calls and call-start rate
Not verifiedThe product page describes rapid channel ordering but does not publish a per-account concurrent-call entitlement, bursting rule or calls-per-second limit. Do not convert an ordered channel count, number inventory or marketing capacity statement into a CPS allowance. Obtain dated account limits and run only a separately approved bounded load test.
Emergency calling
DocumentedThe FAQ says UK 999 and 112 calling is available but depends on the phone equipment, Internet connection, interconnection and electrical power working. International SIP Breakout separately describes local emergency-service access. Confirm the exact country, registered location, callback number, nomadic behavior, outage alternative and provider-approved validation process for each site; do not place an uncoordinated emergency call.
Pricing and minimum term
Not verifiedThe reviewed pages do not publish a complete current price for a specific trunk, number set, destinations, port, recording, support, taxes or renewal. Voiceflex publishes a dated minimum-term schedule with different product entries, so no one term should be applied across every SIP-trunk order. Obtain the current order form, tariff, minimum period, renewal and cancellation terms in writing.
Administration and support
Not verifiedVoiceflex publishes a SIP and Teams Direct Routing SLA version 1.1 dated September 10, 2025, with incident priorities and response and resolution targets. A public SLA does not prove that it is incorporated into a particular order or define every maintenance, escalation, log-retention and service-credit condition. Bind monitoring, escalation and restoration ownership to the signed contract.
SMS and MMS
Not verifiedThe reviewed SIP-trunk pages do not establish SMS or MMS eligibility, sender registration, API scope, throughput, retention or price for a trunk number. Qualify messaging as a separate number and commercial service rather than inferring it from voice routing, number supply or the availability of separate call-recording controls.
Bind authentication and signaling delivery to the provisioned trunk
The reviewed pages do not define one authentication model for every Voiceflex trunk. The failover description refers to a PBX that responds or regularly registers, but that does not prove a universal REGISTER requirement. Determine whether each direction uses registration, digest credentials, an approved source address or another provisioned method.
Retain the registrar or proxy, DNS result, transport, SIP and authorization identities, source address or FQDN, Contact, expiry, challenge and response. A portal status, successful REGISTER or OPTIONS reply does not by itself prove inbound and outbound call completion.
Separate number supply, porting and caller identity
Voiceflex advertises UK and international numbers and number porting, while International SIP Breakout describes local number and emergency capabilities in supported markets. Confirm the exact number, country, service address, port status and go-live window rather than treating general coverage as inventory.
For inbound calls, retain the Voiceflex source, destination, Request-URI, asserted identity, PBX match and final extension. For outbound calls, retain the authorized identity, presented caller number, privacy behavior and carrier response. Do not infer caller-ID authorization from number ownership or inbound delivery.
Negotiate media and protection from current evidence
The reviewed public pages do not publish a universal codec, packetization, DTMF, RTP, T.38, TLS or SRTP contract for the ordered service. Obtain the current technical pack and configure only the methods it and the PBX both support.
Preserve offer and answer SDP, telephone-event mapping, RTP endpoints, packet timing, decoded result, transport, certificate and media-protection profile where applicable. Keep fraud monitoring, signaling authorization, signaling confidentiality and media confidentiality as separate findings; none proves the others.
Model failover at SIP-account level
Voiceflex says its automatic failover can route calls to an alternate PBX when the primary does not respond or regularly register, and that the feature is applied at SIP-account rather than individual-number level. Map every number on that account, the primary and alternate destinations, capacity, caller identity, detection, restoration and return-to-primary behavior before enabling it.
Prove new-call routing with an approved failure and recovery exercise. Do not claim that established calls survive, that all numbers can fail independently or that the backup path has matching capacity unless those outcomes are separately documented and observed.
Accept emergency, operational and commercial limits separately
Voiceflex states that UK emergency calling depends on customer equipment, Internet, interconnection and power, while international breakout separately describes local emergency access. Confirm the registered location, callback number, country rules, nomadic behavior, outage alternative and provider-approved validation method for every site; do not place an uncoordinated emergency call.
The dated SLA and minimum-term schedule are evidence inputs, not proof that their targets or terms govern the selected order. Reconcile the signed order, current tariff, minimum period, support and escalation obligations, recording policy, explicit capacity and a bounded acceptance matrix for inbound, outbound, identity, audio, DTMF, protection, failover and rollback.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Voiceflex SIP trunking ↗
- Voiceflex frequently asked questions ↗
- Voiceflex automatic failover ↗
- Voiceflex international SIP breakout ↗
- Voiceflex voice services ↗
- Voiceflex call recording ↗
- Voiceflex fraud protection ↗
- Voiceflex SIP and Teams Direct Routing SLA, version 1.1 ↗
- Voiceflex minimum-term schedule ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.