CC Routes — CLI & NCLI Wholesale VoIP for Call Centers
MCC CC Routes is part of MCC's wholesale voice offering for organizations with call-center and outbound dialer traffic requirements. This is a voice termination service — not contact center software. If you are looking for agent queues, IVR, and customer interaction management, see MCC Contact Center.
Wholesale voice termination
A voice termination service for organizations with call-center and outbound dialer traffic requirements. Routes traffic from your dialer or platform to destination networks. No agent seats. No queues. No IVR.
Contact Center software
A cloud platform for managing inbound and outbound customer interactions — with agent seats, call queues, skills-based routing, IVR, call recording, and supervisor tools. This is agent and customer management software, not a voice termination route.
See Contact CenterWholesale VoIP routing for call-center traffic requirements.
MCC CC Routes is part of MCC's wholesale VoIP voice offering for organizations with call-center and outbound dialer traffic requirements. If your organization runs outbound dialing campaigns or operates VoIP platforms serving call-center clients, contact MCC to discuss whether CC Routes is the right fit for your traffic profile.
Call-center traffic has characteristics that differ from general voice traffic: high call-per-second rates, short-duration calls (particularly for unanswered attempts), and high concurrent call volumes. These characteristics matter when evaluating a wholesale VoIP route's suitability for your operation. Our guides to CLI, Non-CLI and CC route types and to buying USA CC routes explain how call-center VoIP routes differ. Discuss your traffic profile and technical requirements with MCC.
For general outbound voice traffic that is not call-center or dialer-specific, see MCC Wholesale Voice.
How CC Route traffic flows
USA CC Routes for call centers and dialers
MCC USA CC Routes provides wholesale voice termination to US destinations optimized for call-center and predictive dialer traffic. USA routes are the primary requirement for North American call centers, BPOs, and outbound dialer operations targeting US customers across all 50 states and US territories.
MCC's USA CC Routes carry call-center traffic to US landline and mobile destinations. A route that passes through fewer intermediate carriers generally has lower post-dial delay and more consistent CLI delivery than one transited through several, so ask MCC how a route is built before you send volume on it.
USA-specific routing benefits for call center operations include: (1) routing to the US area codes your campaigns call most, (2) paths to major US metro markets, (3) capacity for predictive-dialer bursts, confirmed with MCC against your peak CPS, and (4) US caller ID presentation, which recipients are generally more willing to answer than anonymous or international numbers.
High-volume predictive dialers targeting USA destinations require routes provisioned specifically for burst CPS patterns without throttling. Discuss your concurrent call count, peak CPS requirements, and target US area codes with MCC to confirm USA CC Routes capacity and routing optimization for your specific traffic profile.
MCC provides both CLI and NCLI USA CC Routes. CLI routes present caller ID to US recipients and are generally answered more often than NCLI routes, where no number displays. How much more depends on the destination and the campaign, so measure it on your own traffic. See CLI vs NCLI routes explained for how caller ID affects answer rates.
VoIP-specific routing for call center operations
VoIP CC Routes use IP-based voice termination infrastructure specifically optimized for call-center traffic patterns. Unlike legacy circuit-switched TDM connections, VoIP routing allows for dynamic capacity scaling, real-time route optimization, and integration with modern dialer platforms through SIP.
VoIP-based call center routes offer several technical advantages for high-volume operations: sub-second call setup times (critical for predictive dialer pacing), dynamic codec negotiation for bandwidth optimization, and the ability to handle burst CPS rates that would saturate traditional ISDN PRIs. Modern VoIP infrastructure also enables real-time call quality monitoring through RTP statistics, allowing route quality issues to be detected and addressed faster than with circuit-switched alternatives.
For call centers migrating from traditional TDM circuits to VoIP termination, the technical requirements differ significantly. VoIP CC Routes require proper SIP trunk configuration, network QoS settings to prioritize RTP media, and sufficient internet bandwidth to handle concurrent calls plus overhead. MCC works with call center operators to validate network readiness and provision VoIP routes matched to their platform's SIP implementation. See VoIP routes explained for technical details on route types and quality metrics.
How call-center routes are evaluated
Buyers of call-center traffic routes evaluate on the following criteria. These are standard industry metrics — confirm how they apply to MCC CC Routes during your evaluation.
CLI and NCLI
Calling Line Identification (CLI) routes present the originating caller ID number to the called party. NCLI routes do not. CLI routes typically achieve higher answer rates; NCLI routes are used where CLI presentation is not required or not available. CLI vs NCLI routes explains the answer-rate trade-off. Confirm CLI and NCLI availability with MCC.
ASR — Answer Seizure Ratio
The percentage of call attempts that are answered. For call-center dialer traffic, ASR is a primary quality indicator — it directly affects how many connects the dialer achieves per hour. Higher ASR means more answered calls per attempt.
ACD — Average Call Duration
The average length of completed calls. For call-center traffic with many short-duration calls (unanswered, AMD, or quick disconnects), ACD can be lower than general traffic averages. Some routes are designed to accommodate this traffic profile.
CPS — Calls Per Second
The rate at which new calls can be initiated. Predictive dialers generate high CPS bursts that standard routes may throttle or reject. When evaluating CC Routes, discuss your CPS requirements with MCC to confirm what capacity is available for your traffic profile.
PDD — Post Dial Delay
The time between when the call is placed and when the destination phone begins ringing. Lower PDD is important in dialer workflows where agents are connected as soon as a call answers — high PDD creates a perceptible delay and reduces effective talk time.
Concurrent calls
The maximum number of simultaneous calls the voice trunk can handle. Predictive dialers run significantly more concurrent attempts than the number of active agents — route and trunk capacity must accommodate the full concurrent attempt count, not just connected calls. Confirm capacity with MCC during evaluation.
What are NCLI routes and when are they used?
NCLI (Non-CLI) routes do not present Calling Line Identification to the called party. The recipient sees no caller ID number — the call displays as "unknown" or shows no number at all.
NCLI routes are used in call-center and dialer operations where CLI presentation is not required, not available, or where destination/regulatory considerations make NCLI appropriate. NCLI routes typically have lower answer rates than CLI routes because the recipient cannot see who is calling — but they remain a standard option in wholesale voice for traffic types that do not require CLI delivery.
When evaluating NCLI routes, the primary quality metrics are ASR (Answer Seizure Ratio) and PDD (Post Dial Delay) — there is no CLI delivery to assess. Confirm NCLI availability for your destinations with MCC.
How CLI termination works for call center traffic
CLI (Calling Line Identification) termination delivers the originating caller ID number through the routing infrastructure to the terminating network, where it is presented to the called party. For call center operations, CLI delivery is not merely a feature — it is the primary technical factor determining answer rates, which directly affects dialer efficiency and campaign ROI.
Call center CLI routes must handle three technical requirements that general business routes do not face at the same scale: (1) preserving CLI accuracy across thousands of concurrent calls per second, (2) delivering CLI consistently even when traffic bursts exceed normal CPS baselines, and (3) maintaining CLI presentation reliability when routing through multiple carrier interconnects to reach diverse destination networks.
The technical path for CLI delivery in wholesale call center routing works as follows: the dialer's SIP INVITE includes the calling number in the FROM header and P-Asserted-Identity header. MCC's routing infrastructure validates the CLI against the customer's authorized number inventory, then forwards the call to the destination carrier with CLI intact. The terminating carrier delivers the number to the called party's device, where it displays before or during the first ring.
CLI delivery reliability varies by destination network and carrier relationship. Some destination markets require CLI to be presented in specific E.164 format, others apply CLI validation rules that reject foreign-origin numbers, and certain mobile networks strip CLI from wholesale-terminated calls regardless of upstream delivery. When evaluating CC Routes for a specific destination mix, confirm actual CLI delivery rates per destination rather than assuming wholesale CLI availability means universal delivery.
For high-volume outbound campaigns where answer rate is the dominant cost driver, CLI route selection should be evaluated against three criteria: (1) measured CLI delivery rate for your specific destination mix, (2) ASR performance when CLI is successfully delivered, and (3) consistency of CLI delivery during peak CPS periods when dialer traffic spikes. Non-CLI routes cost less per minute but produce materially lower answer rates — the per-connect cost is usually higher despite the lower per-minute rate.
CLI vs NCLI for call-center traffic — a practical comparison
The route type you choose for call-center traffic directly affects answer rates. Here is how CLI and NCLI routes differ for outbound dialer operations.
| Area | CLI Route | NCLI Route |
|---|---|---|
| Caller ID presentation | Originating number presented to the called party | No caller ID — called party sees no number or unknown |
| Answer rate expectation | Generally higher — recipient can see who is calling | Generally lower — number not visible to recipient |
| Common usage | Outbound campaigns where presenting a number improves answer rates — customer service follow-up, collections, verification calls | Traffic types where CLI is not required or where destination/regulatory considerations make NCLI appropriate |
| Route considerations | CLI delivery consistency across destinations is a standard evaluation criterion alongside ASR | ASR and PDD are the primary quality metrics — no CLI delivery to evaluate |
CLI and NCLI availability for CC Routes depends on destination. Confirm availability with MCC for your specific routes and traffic profile. See also: CLI vs NCLI routes explained.
How to request CC Routes from MCC
Share your dialer and traffic profile
Contact MCC with your dialer type, estimated CPS, concurrent call count, and destination mix. This information shapes the route discussion and confirms whether CC Routes is the right fit.
Specify route type requirements
Confirm whether you need CLI or NCLI routes, or both. Indicate your destination priorities so MCC can advise on route availability and pricing for those specific destinations.
Review route availability and pricing
MCC will provide available routes and pricing for your profile. CC route pricing varies by destination, route type, and traffic volume — there is no public rate card.
Test before committing production traffic
Before routing live campaign traffic, test route quality — specifically ASR and PDD for your target destinations and CPS handling for your dialer's call rate.
Move production traffic
Once route testing confirms quality and capacity, production traffic moves to the provisioned routes. MCC's team is the ongoing point of contact for route performance and escalation.
Who uses CC Routes?
Outbound call centers
Organizations running outbound campaigns with predictive or progressive dialers — where call volume and CPS requirements may not be suited to standard retail trunks. Contact MCC to discuss your profile.
Dialer platform operators
VoIP platforms or dialer software companies that need wholesale termination capacity for their customers' call-center traffic — rather than retail per-seat trunks. Contact MCC to discuss available options.
Resellers serving call-center clients
Resellers and service providers whose customers include outbound call-center operations with high-volume traffic requirements.
Note: Businesses operating outbound dialing campaigns are responsible for evaluating their calling practices against applicable laws, consent requirements, calling-time rules, and do-not-call obligations. MCC CC Routes is a voice termination service — compliance with applicable calling regulations is the responsibility of the organization operating the dialing campaigns.
Discussing your traffic profile with MCC
Traffic characteristics that matter when evaluating wholesale voice routing for call-center operations:
Traffic factors to discuss with MCC
- Your estimated calls-per-second (CPS) rate
- Expected concurrent call count
- Average call duration and volume of short-duration / unanswered calls
- Whether CLI or NCLI route presentation is required (confirm availability)
- Destination mix and coverage requirements
General Wholesale Voice
For outbound voice traffic that is not call-center or dialer-specific, MCC Wholesale Voice may be the more appropriate starting point. Whether CC Routes and general wholesale voice are distinct product lines or different configurations is a question to confirm directly with MCC.
See Wholesale VoiceCC Routes questions
Discuss call-center route requirements with MCC.
CC Routes are provisioned based on your traffic profile. Send your dialer type, CPS requirements, destination mix, and CLI/NCLI route preference, and the team will come back with rates.
Reselling or wholesaling MCC services to your own customers? Partner with MCC.