Enterprise voice
fixed lines, international calling and cloud contact centre
Telephony is usually the oldest system in the building and the one nobody wants to touch — until you move office, open a branch or go remote. Then it becomes the thing holding everything up.
What this service covers
Enterprise fixed lines
Corporate fixed-line service with number arrangements confirmed case by case during assessment.
Global international calling
International long-distance for organisations operating across multiple markets.
Cloud contact centre
Elastic agent capacity, recording, routing and reporting without on-premises hardware.
HD IP and cloud voice
Data, video, voice and imaging on one fabric, with voice protected by policy rather than competing for bandwidth.
Business-system integration
Screen-pop, call-record archiving and recording linked to CRM and ticketing systems.
Local breakout
Branch voice breaks out near the user instead of hair-pinning through headquarters.
Who uses it, and for what
Unified dial plan
- Legacy PBX retained while new sites go cloud
- Inter-site trunking with one dial plan
- Local breakout avoids hair-pinning via HQ
- Voice prioritised by SD-WAN policy
Elastic agent capacity
- Cloud contact centre with recording and routing
- Screen-pop and record archiving into CRM
- Capacity scales with campaign volume
- 24/7 NOC monitoring
Store telephony
- IP phones delivered with the store-opening kit
- HQ-to-store and store-to-store calling on one plan
- About 1 week per store end to end
- Multiple sites delivered in parallel
Cross-market calling
- Global international long-distance
- International segments over the three carriers' licensed networks
- IP and cloud voice interworking
- Flexible terms, from one day
Service parameters at a glance
These are network-wide figures. Anything that depends on a specific site — facility conditions, access method, exact schedule — is confirmed by survey.
| Item | Specification |
|---|---|
| Scope | Enterprise fixed lines · global international calling · cloud contact centre · HD IP and cloud voice |
| Network integration | Deployed within the same line plan as SD-WAN, with voice prioritised by policy; multi-site deployments break out locally |
| Migration paths | SIP trunking with number retention · hybrid transition · full cloud, chosen against the state of the existing PBX |
| System integration | Integrates with CRM and ticketing systems (screen-pop, record archiving, recording linkage); interfaces and field mapping confirmed during solution design |
| Lead time | Standard delivery 3 days to 1 week; migrations involving number handling and parallel running are scheduled against the plan |
| Billing | Fixed monthly rate (monthly / quarterly / annual); agents and numbers billed on actual provisioned quantity; international calling at published tariffs; one-off activation and equipment listed separately |
| Bandwidth | 10 Mbps – 100 Gbps, upgradable in steps |
| Service assurance | PoP-to-upstream-ISP availability 99.99%; end-to-end link availability 99.5%; 24/7 NOC monitoring and proactive alerting; 100% VIP fault tracking |
| Contract term | Flexible — no blanket minimum. Annual terms for steady services; short-term needs (events, exhibitions, temporary projects) from one day |
| Footprint | 60+ PoPs across Greater China, 120+ PoPs worldwide; measured latency between nodes is queryable on the coverage map |
How to think about it
Three migration paths. SIP trunking with number retention keeps the existing PBX and extensions untouched and only replaces the outside lines — lowest investment, invisible to staff, and it solves line cost and provisioning time but not remote work or system integration. Hybrid transition keeps the PBX at headquarters while new branches go cloud, with trunking between them and one dial plan — the right answer for most multi-site organisations. Full cloud retires the PBX entirely, giving complete remote-work and integration capability at the cost of a concentrated cutover risk.
Numbers decide the plan, not technology. Whether existing numbers can be retained, how they port, and how old and new run in parallel during transition — these need answering before any equipment is chosen. Build the full number inventory (type, ownership, current use, monthly volume) during assessment; it is the foundation of everything after.
Voice needs the network planned with it. Voice is sensitive to loss and jitter, and over the open internet neither is controllable. Fredyun deploys HD IP and cloud voice within the same line plan as SD-WAN, so voice holds priority by policy and critical scenarios can ride dedicated transport. With 120+ global PoPs, branch voice breaks out locally rather than hair-pinning through headquarters.
Licence scope
International and Hong Kong / Macau / Taiwan capacity is not built by Fredyun. China Mobile International (CMI), China Unicom Global (CUG) and China Telecom Global (CTG) hold the international telecom licences and supply the underlying circuits. Fredyun procures that licensed capacity and delivers convergence, routing, end-to-end provisioning and operations on top of it.
Fredyun itself holds a trans-regional value-added telecom business licence (B1-20235481) issued by China's Ministry of Industry and Information Technology, covering IDC, ISP, CDN and domestic internet VPN — trans-regional, not international. This boundary is stated explicitly in every proposal and contract.
What clients ask most
Can we keep our existing numbers?
It depends on each number's type, ownership and how it is currently carried, so it has to be confirmed number by number — which is why the assessment stage starts by building a complete number inventory (type, ownership, use, volume). The parallel-running arrangement for the transition is settled at the same time, so customers never hit a dead line during cutover.
Our PBX still works — is there a reason to move now?
Not necessarily all at once. If the PBX has life left, SIP trunking with number retention keeps the hardware and extensions and only replaces the outside lines: low investment, invisible to staff, and it addresses line cost and provisioning time. Move further when structural needs appear — remote work, system integration — or when the equipment nears end of support.
How do we unify voice across many branches?
The hybrid transition path: keep the PBX at headquarters or major sites, put new branches on cloud voice, trunk the two together and unify the dial plan; the estate converges naturally as old equipment retires. The thing to plan carefully is extension numbering and call-reporting definitions, so the parallel period does not produce unreachable extensions or figures that do not reconcile.
How is voice quality protected?
Voice is sensitive to loss and jitter, so the point is not letting it compete for bandwidth. Fredyun deploys HD IP and cloud voice within the same line plan as SD-WAN, giving voice priority by policy, with dedicated transport available for critical scenarios. Multi-site deployments break out locally rather than backhauling branch voice to headquarters.
Can it integrate with our CRM or ticketing system?
Yes — screen-pop on inbound calls, automatic call-record archiving and recordings linked to tickets. Integration effort is routinely underestimated, so interface style, field mapping and division of responsibility are pinned down during solution design with time reserved for joint testing. Exact capability is confirmed during assessment.
Usually planned together
Need a link assessment for this design?
Tell us the site locations, bandwidth and latency targets
and we will come back with a workable topology and SLA proposal.
