Start with the current order and portal record
VoiceHost's how-to collection describes register-based trunks with supplied credentials, registrar and proxy details, while the product page advertises on-demand channel management and hybrid platform features. Record the legal service, trunk identity, realm, peers, numbers, channels, support terms and change contacts from the current account before adapting any vendor template.
Older PBX guides remain useful implementation examples, but their tested software, field names and codec lists are not a universal current profile. Preserve the observed challenge, Contact and source-address decisions without exposing credentials.
Documented service facts
Reviewed 2026-10-07. Compare SIP trunk services →
SIP authentication
DocumentedVoiceHost's current how-to collection describes supplied authentication IDs or usernames and passwords, registrar and proxy values for specific PBX configurations. Preserve the exact portal-issued realm, identities, secret owner, source-address rules and observed challenge exchange; an old vendor template is not a universal current trunk profile.
SIP registration
DocumentedThe reviewed Avaya, Samsung and other guides describe register-based trunks using provider-issued credentials and registrar details. The current order and portal record must establish Contact, expiry, refresh, concurrent-registration and source-address behavior for the selected PBX rather than inheriting a legacy template.
Inbound delivery
DocumentedVoiceHost's PBX guides use assigned DDI inventory, E.164-style numbers and configurable plus-sign handling. Those examples do not establish the Request-URI, asserted identity or normalization for every account. Retain the assigned inventory, port state, delivered identifiers and matched PBX destination for each authorized acceptance call.
Routing and failover
DocumentedVoiceHost advertises a resilient network and multiple data-centre and interconnection relationships, but the reviewed pages do not define one trunk failover trigger, retry sequence, restoration order, customer-access dependency or established-call outcome. Bind continuity to the ordered design and a provider-approved new-call failure exercise.
Number and regional availability
DocumentedThe service advertises UK and other-country number portability and current UK bundles. This does not establish inventory, portability, identity rights, serviceability or regulatory eligibility for a particular address or number. Preserve dated order and port responses for the exact requirement.
Audio codecs and DTMF
DocumentedVoiceHost's vendor guides publish profile-specific codec and DTMF values; the Yeastar record lists A-law and GSM plus RFC2833, INFO, in-band and automatic DTMF options for its tested configuration. Other how-to text presents different codec sets. Obtain the current interface profile and preserve both SDP bodies, negotiated payload mapping, packetization and decoded digit evidence instead of merging examples.
T.38 fax
DocumentedThe Yeastar interoperability record lists T.38 for one tested PBX profile. It does not establish T.38 entitlement, switchover, redundancy, page limits or support on every trunk, gateway and destination. Treat fax as a separately accepted workflow with the current interface record.
Signaling and media encryption
DocumentedVoiceHost advertises SIP TLS and SRTP support. Support does not prove that either control is ordered, configured, certificate-validated or retained across every call leg. Record transport, trust chain, media keying, downgrade behavior and any recording or PSTN boundary for the selected service.
Concurrent calls and call starts
DocumentedThe current product page advertises portal-adjustable channels and a starter range from one to 150 channels. Ordered channels, active calls, inbound and outbound limits, call-start controls, bursts, PBX and SBC resources and access bandwidth remain different quantities. Use the dated account record for numeric entitlement and an approved load plan for observed behavior.
Emergency calling
DocumentedVoiceHost's current terms say its VoIP services should not be used to access 999 or 112 and warn that location or number may not be passed if a connection occurs. A separate call-charges page lists 999 and 112 as free destinations; that tariff entry is not an entitlement or reliability promise. Treat the terms and written account confirmation as governing and maintain an alternative calling method.
Pricing model
DocumentedVoiceHost publishes pay-as-you-go, bundle and channel-based options and notes that out-of-bundle and international usage can be charged separately. Public examples are not a complete account price. Use a dated quote or portal tariff for channels, call starts, usage, numbers, porting, options, support, taxes, term, renewal and cancellation.
Administration and support
DocumentedVoiceHost advertises real-time portal administration, permissions, MFA, spend control, network monitoring and 24/7 UK support. Preserve portal roles, named contacts, escalation, maintenance notices, purchased support terms, monitoring boundary and change evidence; marketing availability language is not an observed account service level.
SMS and MMS
Not verifiedThe SIP Trunking page presents SMS as an available hybrid-platform feature, but the reviewed pages do not establish SMS or MMS entitlement on every trunk number, sender registration, API access, throughput, webhook security, retention or price. Treat messaging as a separately ordered service and workflow.
Keep channels, call starts and platform capacity separate
The current page advertises portal-adjustable channels and a starter range from one to 150. That describes an order dimension, not a measured calling result. Purchased channels, active inbound and outbound calls, call attempts per second, burst controls, PBX and SBC ceilings and access bandwidth are separate limits.
Use the dated account record for numeric entitlements and an approved load plan for observed behavior. A vendor interoperability label or listed PBX brand does not establish exact-version compatibility or a capacity result for the intended design.
Turn encryption and resilience into path evidence
VoiceHost advertises TLS and SRTP support, a resilient network and multiple interconnection sites. Those claims do not prove that a selected trunk requires TLS, validates the intended certificate, negotiates SRTP, survives loss of a customer circuit or preserves established calls.
Map the PBX-facing signaling and media, provider network, recording service, PSTN route and any downstream leg. Preserve handshake, SDP and packet evidence for protection, and document the provider-approved new-call failure and restoration test before reporting continuity.
Resolve the emergency contradiction conservatively
VoiceHost's terms say its VoIP service should not be used for 999 or 112 and warn that number or location may not reach the operator. A separate call-charges page lists those destinations as free. A tariff row does not override the service limitation or prove routing, location delivery, callback behavior or availability.
Obtain written account-specific confirmation before representing emergency capability. Keep site, caller identity and location records current where a supported process exists, follow the provider's approved validation method and maintain an independently powered alternative calling path.
Accept media, fax, numbers and operations separately
VoiceHost's vendor guides contain configuration-specific codec, DTMF, number-format and T.38 examples. Retain the current interface profile, both SDP bodies, payload mapping, digit evidence, assigned DDI inventory, port state and matched PBX route rather than combining legacy examples.
Bind pay-as-you-go or bundle terms, portal roles, support, monitoring and messaging to dated account records. No VoiceHost service, route, protection state, availability, compatibility, price or call was tested for this record.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- VoiceHost SIP Trunking ↗
- VoiceHost platform how-to collection ↗
- VoiceHost Yeastar S-Series SIP trunk configuration ↗
- VoiceHost terms and conditions ↗
- VoiceHost call charges and phone numbers ↗
- VoiceHost network overview ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.