Identify the exact service and partner relationship
Clearfly presents SIP trunking and adjacent voice services through a partner-oriented model. Record the legal customer, serving partner, sites, voice groups, numbers, ordered trunk type and quantity, billing owner, support entitlement, PBX or SBC, access provider and signed service schedule. Keep the trunk separate from unified billing, fax-to-email, conferencing, personalized forwarding, virtual attendant, voicemail and messaging.
Translate commercial labels into technical objects. A portal voice group, trunk count, DID, forwarding destination and messaging switch are different states. Preserve who may change each one, how an emergency change is approved, and where customer responsibility begins.
Documented service facts
Reviewed 2026-10-15. Compare SIP trunk services →
SIP authentication
Not verifiedThe reviewed public pages do not identify whether a selected trunk uses digest registration, source-address trust, certificates or another account control. Obtain the Clearfly handoff for the exact voice group and preserve the authentication identity, source policy, challenge behavior and secret owner without exposing credentials.
SIP registration
Not verifiedClearfly says its portal can expose voice-group information and registrations, but the public material does not publish one registrar, proxy, expiry, Contact policy or failover sequence. Treat portal state, loaded PBX configuration, a SIP transaction and completed call as separate evidence.
Numbers and inbound delivery
DocumentedClearfly describes local and long-distance numbers, toll-free calling, personalized DID forwarding and virtual-attendant options. It does not publicly establish current number inventory, port eligibility, delivered Request-URI, identity headers or primary and alternate SIP destinations for a selected order. Preserve the order, port record and one authorized inbound trace.
Failover and continuity
DocumentedThe service page describes personalized forwarding and a virtual attendant that can front calls during weather events or a phone-system outage. These are routing features, not proof of SIP target health detection, access diversity, PBX survival or established-call continuity. Record each ordered control, trigger, destination, restoration rule and approved new-call test.
Service area and number coverage
DocumentedClearfly presents service through nationwide partners and tells prospective customers to confirm what is available in their area. No complete public rate-centre, number-type, portability, service-address or international-destination matrix was verified. Qualify every number and calling direction against the current order.
Codecs, DTMF and call quality
Not verifiedThe public pages market voice quality and provide a bandwidth calculator, but no definitive codec, packetization, DTMF, RTP range, transcoding or QoS handoff profile was verified. Capture offer and answer SDP, RTP tuples, markings, loss, jitter and decoded results on representative authorized calls.
Fax
DocumentedClearfly lists fax-to-email or eFax-to-email as an available service. That is a managed fax product statement, not proof that T.38, G.711 pass-through, analogue adapters or existing fax machines work on a SIP trunk. Keep managed fax, trunk media and analogue-device qualification separate.
Signaling and media protection
Not verifiedThe reviewed public pages do not define TLS versions, certificate validation, mutual authentication, SRTP profiles, keying, encryption scope or unprotected intermediary legs for SIP trunking. Obtain the ordered security profile and verify the negotiated signaling and media path rather than inferring protection from the provider relationship.
Trunks, channels and call starts
DocumentedClearfly says customers choose the type and quantity of trunks, that more trunks can be added, and that call bursting may be available. The public pages do not define one account's simultaneous-call pool, burst ceiling, calls-per-second limit, direction sharing or overload response. Use the signed order and controlled acceptance evidence.
Emergency calling
Not verifiedClearfly says its portal can update 911 addresses, but the reviewed pages do not define trunk eligibility, location validation, callback identity, nomadic use, propagation, failure behavior or a provider-approved test process. Keep an accessible independent emergency method until the selected service and location controls are evidenced.
Pricing, billing and policy
Not verifiedClearfly describes flexible pricing, metered trunks with local calling included and long distance billed per minute, but it does not publish one complete durable tariff for every order. Preserve the quote, current rate deck, taxes, fees, minimums, term, renewal, porting, emergency service, international use, suspension and cancellation terms.
Portal, support and demarcation
DocumentedClearfly publishes 24/7 technical support and a portal for incidents, maintenance, voice groups, calling areas, rates, 911 addresses and messaging. Those interfaces do not define the customer/provider demarcation or prove restoration performance. Record monitoring, ticket severity, escalation, maintenance, access, PBX and last-mile owners for the exact service.
SMS and MMS
DocumentedClearfly lists SMS/MMS and says the portal can enable it. That does not establish eligibility for every voice number, registration, campaign approval, throughput, API or webhook behavior, retention, consent workflow, carrier filtering or price. Treat messaging as a separately ordered and accepted service.
Use the issued handoff instead of assumed SIP defaults
The reviewed public pages do not publish a complete registrar, proxy, authentication, transport, port, DNS, codec, DTMF or RTP profile. Obtain the Clearfly or partner-issued handoff for the selected order and preserve its revision. Do not derive hosts from the marketing domain, copy another customer configuration or treat a portal registration label as proof of a usable call path.
For acceptance, retain resolver answers, loaded PBX objects and one authorized inbound and outbound transaction: source and destination tuples, Request-URI, From, asserted identity, Contact, challenge and final response. Then prove destination answer, negotiated media, DTMF and user experience separately.
Map routing features to explicit failure cases
Clearfly describes personalized forwarding and a virtual attendant that can front inbound calls during weather events or a phone-system outage. Those features may support continuity, but they do not establish SIP target monitoring, customer-access diversity, PBX redundancy, trigger timing, restoration behavior or survival of an established dialog.
Document each routing layer in order: public number, ordinary destination, forwarding or attendant control, alternate destination, voicemail and final failure result. Exercise approved new calls for the intended PBX, access and power failures, then reverse the change and verify restoration. Preserve caller identity, delay, media and an unrelated control call.
Qualify capacity, media and protection on the deployed path
Clearfly says customers select trunk type and quantity, can add trunks, and may use call bursting. Obtain the actual simultaneous-call pool, burst ceiling, direction sharing, calls-per-second controls and overload responses. Test only within authorization and do not turn a marketing scalability statement into measured capacity.
The public pages do not define the selected codec, DTMF, RTP or cryptographic profile. For representative calls, retain SDP, RTP endpoints, QoS markings, loss, jitter and decoded audio. If protected signaling or media is ordered, verify certificate names and trust, protocol and cipher, SRTP keying, downgrade policy and each intermediary hop.
Keep number, emergency, fax and messaging acceptance separate
Clearfly markets local and long-distance numbers, toll-free service, SMS/MMS and fax-to-email, and its partner portal can update 911 addresses. None of those general statements proves eligibility for a particular number, successful porting, emergency location propagation, T.38 or analogue-device support, or messaging registration and throughput.
Build separate acceptance records for number inventory and porting, inbound delivery, emergency location and callback identity, managed fax, trunk media, and messaging. Maintain an accessible independent emergency method until Clearfly or the serving partner documents the exact process and authorizes testing. Do not place test calls to emergency services without that process.
Accept the commercial and operational service actually ordered
The public service page describes flexible pricing and a metered model with local calling included and long distance charged per minute. Preserve the signed quote, current rate deck, taxes and fees, number and port charges, trunk and burst rules, emergency and messaging charges, international controls, term, renewal, suspension and cancellation terms. Public descriptions are not a durable account tariff.
Before cutover, verify portal access, numbers, routing, identity, inbound and outbound calls, DTMF, media, security where ordered, capacity within authorization, routing changes, restoration, monitoring, support escalation and rollback. Store redacted evidence with the configuration export and case record. No Clearfly account, order, trunk, number, network, PBX, packet, media stream or call was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Clearfly voice services and SIP trunking ↗
- Clearfly service FAQs ↗
- Clearfly partner programme and portal ↗
- Clearfly support contacts ↗
- Clearfly legal and regulatory index ↗
- Clearfly Acceptable Use Policy ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.