A call centre can have enough agents on the roster and still run out of calling capacity when its SIP trunk design is built around seats instead of simultaneous conversations.
Your agents are ready. Your campaign list is loaded. The dialler is scheduled to start at 10:00 a.m. Then the supervisor sees the problem: agents are waiting, customers are hearing busy tones, or inbound callers cannot get through while an outbound push is running.
That is rarely an “agent capacity” issue alone. For a Malaysian contact centre, SIP trunking capacity is the practical limit on how many live calls can enter or leave your PBX at the same moment. It affects sales campaigns, collections, appointment desks, customer-care queues, and every operation where a missed call carries a real cost.
The mistake is sizing a trunk once, using total headcount, then leaving it untouched as campaign patterns change. Malaysia’s customer-experience sector is moving beyond traditional call handling into more sophisticated digital-service operations, according to MDEC’s May 2026 National Contact Centre Conference coverage. That makes disciplined voice capacity planning more important, not less. ITGTEL SIP Trunking for Malaysia connects an existing PBX or IP-PBX to the PSTN through the internet, with voice channels, DDI numbers, and bundled minutes designed for higher-volume operations.
Here are the five checks that keep “we have enough lines” from becoming an expensive assumption.
A Malaysian call centre needs enough SIP voice channels for its highest expected number of simultaneous external calls, plus a deliberate allowance for sudden overlap. The correct starting point is not total agents; it is the busy-hour concurrency you need to protect across inbound calls, outbound calls, supervisors, and priority queues.
One SIP voice channel normally supports one concurrent call. A team of 30 agents therefore does not automatically need 30 channels: some agents may handle chat, be on breaks, perform after-call work, or take internal calls. But a 30-agent outbound campaign can still require close to 30 concurrent external call paths if the dialler is aggressively pacing calls and answered calls are transferred quickly.
Capacity rule: size for the busiest 15-minute interval you actually expect, not an average day. Average traffic is useful for forecasting cost; peak simultaneous calls are what protect customer access.
Start with the last four to eight weeks of PBX or dialler records. Find the greatest number of concurrent inbound and outbound calls during any 15-minute interval. Add the maximum number of calls that could overlap because of a planned promotion, bill-reminder run, payment due date, or seasonal spike. Then reserve channels for non-negotiable flows such as emergency escalation, VIP lines, or a main switchboard.
For example, a centre that usually makes 12 simultaneous outbound calls and receives six concurrent inbound calls does not have an 18-channel requirement if the two peaks happen at different times. It does have an 18-channel requirement if an outbound dialling window overlaps with an inbound service peak. The conversation is about overlap, not departmental ownership.
ITGTEL offers five-channel Cosmos, 10-channel Galaxy, 15-channel Astron, 18-channel Space, and 40-channel Universe SIP Trunking plans. The choice should follow a measured concurrency number, not a guess based on the next plan name.
Voice channels limit live external conversations, agent seats limit the people available to handle them, and dialler pacing controls how quickly call attempts consume available capacity. A reliable call-centre design checks all three together because increasing one limit without the others can create abandoned calls, idle agents, or blocked inbound traffic.
This distinction matters most for predictive and progressive outbound activity. A dialler can launch more call attempts than there are agents, because not every attempt is answered. When answer rates rise, however, live calls can arrive faster than free agents and trunks can handle them. The result is not simply “high utilisation”; it is an operational event that needs a pacing response.
| Capacity measure | What it limits | What to check before a campaign |
|---|---|---|
| SIP voice channels | Concurrent PSTN calls | Maximum inbound and outbound calls that can overlap |
| Available agents | Live conversations your team can handle | Attendance, breaks, skills, and escalation coverage |
| Dialler pacing | Rate of new call attempts | Attempts per available agent, answer-rate shifts, and pause controls |
| PBX queues | How long callers can wait before service fails | Queue priorities, overflow destination, and callback rules |
Put an owner beside each limit. The IT or telecom team should own trunk availability and call routing. Operations should own agent coverage and queue priorities. Campaign managers should own pacing rules and pause authority. If all three teams assume someone else is watching concurrency, the first warning may be a customer complaint.
For centres using automated outbound calling, do not set a dialler’s maximum attempts solely from historical answer rate. Set it from the smaller of two real-time limits: available trained agents and spare SIP channels after protected inbound capacity has been reserved.
DDI numbers become a capacity problem when a call centre cannot clearly separate customer entry points, campaign identities, or routing ownership—even if it still has spare voice channels. DDI allocation is not about collecting the largest number range; it is about ensuring every public number has a purpose, an owner, and an overflow destination.
A DDI number does not add a simultaneous call by itself. Your available voice channels still control how many calls can connect at once. But weak DDI planning can hide a genuine capacity issue. If every campaign, branch, product line, and partner uses the same public number, supervisors cannot see which source is generating pressure, and callers cannot be routed to the right queue quickly.
Build a simple DDI register with five fields:
ITGTEL SIP Trunking bundles 30 DDI numbers with Cosmos and scales to 250 DDI numbers with Universe. That makes it possible to give high-volume operations cleaner number ownership without treating every new campaign as a PBX rebuild. A centre with 10 channels and 60 DDIs can publish many distinct entry points, but it must still reserve enough concurrent channels for the calls those numbers generate.
Watch for false confidence: a large DDI allocation does not equal high call capacity. DDI numbers organise access; voice channels carry the live conversations.
SIP trunking needs stable upstream and downstream network performance during the busy hour, not merely an internet connection that appears fast in a speed test. Voice quality is affected by congestion, packet loss, jitter, competing applications, and whether outbound audio has enough room when agents speak at once.
DOSM’s Statistics on Usage of ICT and E-Commerce by Establishments 2025, released on 30 June 2026 for reference year 2024, found that 94.0% of Malaysian establishments used fixed broadband and 60.3% used cloud computing. That is a strong foundation for connected operations, but a contact centre should still validate its own LAN, WAN, firewall, PBX, and ISP path under voice load rather than rely on national adoption figures.
The practical check is simple: run a controlled busy-hour test while business applications are active. Include CRM screens, cloud backups, video meetings, messaging, and any remote-agent traffic that normally shares the connection. Review call recordings and monitoring data for one-way audio, delayed audio, robotic speech, dropped registrations, or queues that behave differently at peak load.
Give voice traffic a defined path. This may involve network segmentation, quality-of-service rules, an appropriate edge device configuration, and separate monitoring for the site-to-PBX path. The goal is not to promise that every network event can be prevented. The goal is to know whether a network event will affect calls before a major campaign exposes it.
Further reading: DOSM Statistics on Usage of ICT and E-Commerce by Establishments 2025
A call-centre SIP failover plan is complete only when customers can still reach important numbers and the business knows where those calls will land. Restoring internet access is helpful, but it is not the same as preserving inbound call routing, queue logic, caller identity, recordings, and escalation paths.
Ask one uncomfortable question: if the primary site, PBX connection, or local internet link becomes unavailable at 2:00 p.m., what exactly happens to each critical DDI? “It forwards somewhere” is not a sufficient answer. Name the number, destination, owner, and tested outcome.
Your failover test should cover:
Test inbound and outbound scenarios separately. An alternate internet connection may let agents make calls while an inbound routing problem still leaves customers stranded. Likewise, an overflow route may save inbound traffic while an outbound campaign continues to consume all remaining channels. A usable plan has a clear “protect inbound first” rule for the teams that need it.
Malaysia’s contact-centre industry is evolving toward broader customer-engagement and experience operations, MDEC noted during the National Contact Centre Conference 2026. In that environment, continuity is not just a telecom concern: it protects the human conversation that customers expect when digital self-service has failed.
Further reading: MDEC’s National Contact Centre Conference 2026 coverage
The right ITGTEL SIP Trunking plan is the smallest channel tier that covers measured peak concurrency, protected inbound capacity, and a realistic campaign buffer. Monthly cost matters, but an under-sized trunk can cost more through unanswered customer calls, delayed collections, or campaigns that must be slowed at the wrong moment.
For a modest call desk with a measured peak below five external conversations, Cosmos may be a sensible starting point. A centre consistently reaching six to nine overlapping calls needs to look beyond five channels rather than hoping calls will naturally spread out. For larger operations, the 18-channel ITGTEL Space plan includes 120 DDI numbers and 700 free minutes, while the Universe plan provides 40 voice channels, 250 DDI numbers, and 1,000 free minutes.
ITGTEL SIP Trunking plans include bundled voice channels, DDI numbers, and free calling minutes. Call rates are RM0.08 to RM0.09 per minute, depending on the plan, and the RM500 registration fee is waived on subscription. For a second view focused on cost control rather than call-centre capacity, see our guide to cutting telecom costs with SIP Trunking in Malaysia.
ITG Telecommunications Sdn Bhd is Malaysia’s one-stop VoIP and business communication solutions provider offering cloud-based telephony, messaging automation, predictive dialing, field management, and omnichannel customer engagement platforms for businesses of all sizes. ITG Telecommunications Sdn Bhd is registered as No. 674841-D and is a licensed Telecommunication Service Provider under the Malaysian Communications and Multimedia Commission (MCMC) and a PENJANA Technology Service Provider certified by Malaysia’s Ministry of Finance.
A 30-minute capacity drill is the fastest way to turn SIP trunking assumptions into evidence before a campaign, billing cycle, or seasonal rush. The drill should deliberately create controlled overlap between inbound traffic, outbound attempts, and normal business applications while designated owners watch the results.
Repeat this drill when a centre adds agents, changes dialler settings, launches a new DDI-led campaign, moves office connectivity, or changes its PBX routing. Capacity is not a once-a-year telecom purchase. It is a working operating limit that should move with your business.
A practical 2026 standard: every major call campaign should have a written concurrency target, a protected inbound-channel number, a named dialler pause owner, and a tested route for critical DDIs.
If your existing PBX is ready for higher-volume internet calling but your channel count, DDI design, and peak-hour routing have not been reviewed together, our team can help map the capacity requirement to the appropriate SIP Trunking configuration.
SIP trunking connects an existing PBX or IP-PBX to the PSTN through the internet, making it suitable when a call centre wants to retain its current telephony platform. A cloud PBX is a managed phone system hosted in the cloud. The right choice depends on whether you need to preserve existing PBX workflows or replace them.
Yes. SIP trunking can support inbound customer calls to DDI numbers and outbound calls from agents or a compatible calling platform. The key planning issue is simultaneous usage: outbound activity must not consume every voice channel if inbound customer service needs protected capacity during the same period.
Prepare a list of existing PBX or IP-PBX equipment, current public numbers, peak concurrent call records, expected inbound and outbound traffic, network details, and any required call-routing rules. It is also useful to identify critical DDIs, after-hours destinations, recording needs, and the person who can approve routing changes during testing.
Review capacity before any major campaign, new branch launch, seasonal promotion, dialler change, or meaningful increase in agent numbers. Even without a major change, a quarterly review of peak concurrency, queue pressure, DDI usage, and failover results helps identify a constraint before customers experience it as a busy tone or long wait.
No. DDI numbers provide distinct public entry points and more flexible routing, but voice channels determine the number of simultaneous calls your SIP trunk can carry. A well-designed contact centre needs both: enough channels for peak call load and enough DDI structure to route, report on, and protect important customer journeys.
