VoIP Wholesale Agreement Template

A voip wholesale agreement template is a foundational document for any carrier or service provider engaging in the bulk termination of voice traffic. This legal framework governs the relationship between two or more telecommunications entities, ensuring clarity on routing, billing, compliance, and service expectations. A well-structured voip wholesale agreement template protects both the originator and the terminator by defining responsibilities, quality metrics, and financial terms. Without such a contract, disputes over call quality, unpaid invoices, or regulatory non-compliance can escalate quickly, damaging business relationships and revenue streams. For wholesale providers, resellers, and emerging VoIP startups, having a standardized yet customizable carrier agreement template is not just best practice—it’s a necessity in a high-volume, low-margin industry. Whether you're buying or selling SIP trunking services, international routes, or DID termination, this guide provides a detailed breakdown of what to include in your wholesale voip contract, with real-world examples, rate structures, and industry-specific clauses that reflect current VoIP market dynamics. We’ll also explore how platforms like VoIP Billing Platforms for Wholesale Carriers integrate with contractual obligations to ensure accurate CDR processing and dispute resolution.

What Is a VoIP Wholesale Agreement?

A VoIP wholesale agreement is a legally binding contract between two telecommunications providers that outlines the terms under which one party (the seller) will terminate voice calls originated by the other (the buyer). These agreements are central to the operation of SIP-based networks, enabling carriers to exchange traffic across international borders, regional networks, or niche termination markets. The buyer typically routes outbound calls through the seller’s infrastructure, paying a per-minute rate based on destination, protocol, and quality of service. Unlike retail VoIP contracts, which are consumer-facing, wholesale agreements focus on volume, interconnectivity, and network performance. They are used by Tier 1 carriers, regional operators, and even MVNOs that require access to global termination without building their own international infrastructure.

The agreement defines technical parameters such as SIP signaling, RTP/RTCP stream handling, SRTP support, DTMF modes, and codec preferences (G.711, G.729, Opus). It also specifies how CDRs will be exchanged, whether via FTP, SFTP, or real-time APIs, and what format they must follow (e.g., CSV, XML, or RADIUS). These technical details are critical because discrepancies in CDR interpretation can lead to significant billing disputes. For example, a difference in how PDD (Post-Dial Delay) is calculated—whether from SIP INVITE to 180 Ringing or to 200 OK—can affect revenue by thousands of dollars monthly on high-volume routes. The VoIP Interconnect Agreement Guide expands on these technical interdependencies, particularly in multi-vendor environments.

Wholesale agreements also address liability, force majeure, and data retention policies. For instance, if a carrier fails to deliver calls to a specific destination due to a fiber cut or regulatory shutdown, the contract must clarify whether credits are issued and how they’re calculated. Similarly, if one party is found to be carrying fraudulent traffic or violating FCC, Ofcom, or TRAI regulations, the agreement should allow for immediate suspension of service. These safeguards are essential in an industry where NER (Network Effect Ratio) and ASR (Answer Seizure Ratio) are closely monitored by regulators and peers alike. A standardized wholesale agreement template streamlines negotiations and reduces legal overhead, especially for smaller providers entering the market.

Key Components of a Wholesale Agreement Template

Every effective voip wholesale agreement template must include several core sections to ensure enforceability and operational clarity. The first is the Parties section, which identifies both entities by legal name, registered address, and contact information. This includes authorized signatories and technical points of contact. Without this, disputes over contract validity or change requests become difficult to resolve. Next is the Definitions clause, which standardizes terminology such as “Call,” “Origination,” “Termination,” “CDR,” and “Billing Cycle.” For example, defining a “completed call” as one that reaches 200 OK and lasts at least 6 seconds prevents ambiguity during audit periods.

The Scope of Services section details the types of traffic covered—SIP trunking, DID termination, toll-free, or mobile bypass—and the geographic destinations included. This is where you specify supported protocols (SIP over UDP/TCP/TLS), codecs (G.711u, G.729a), and whether SRTP or ZRTP encryption is required. It should also state whether the seller provides CLI (Calling Line Identification) or if NCLI (No CLI) is permitted, which has regulatory implications in many countries. For instance, India’s TRAI mandates CLI for all international incoming calls, and failure to comply can result in traffic blocking.

Another critical component is the Acceptable Use Policy (AUP), which prohibits illegal activities such as slamming, cramming, robocalling, or using the network for phishing IVRs. The AUP should explicitly ban traffic from known fraud vectors like Wangiri (one-ring scams) or PBX hacking. Violations can trigger immediate suspension and financial penalties. The Confidentiality clause ensures that routing plans, rate decks, and network topology remain protected. Finally, the Governing Law and Jurisdiction section specifies which legal system applies—often New York, London, or Singapore law—and whether disputes will be settled via arbitration or court action. These elements, when combined, form a solid foundation for any wholesale voip contract.

Pricing Structures and Rate Schedules

Pricing is one of the most negotiated aspects of any wholesale agreement template. Rates are typically quoted in USD per minute and vary by destination, time of day, and call type. A flat-rate model is common for high-volume routes, while tiered pricing applies volume-based discounts. For example, a carrier might offer $0.008/min for India mobile up to 1 million minutes, then $0.0075/min for volumes between 1M and 5M minutes. Some agreements use dynamic pricing linked to LCR (Least Cost Routing) tables, where rates adjust based on real-time availability and competition.

Below is a sample rate schedule commonly found in a carrier agreement template:

These rates assume G.711u codec and SIP over UDP. Higher PDD allowances reflect network instability in certain regions, such as Nigeria or Pakistan, where signaling delays are common. The minimum duration ensures that short-duration calls (e.g., misdials) are not billed, reducing disputes. Some contracts include Revenue Share models, especially for DID termination, where the seller pays the buyer a percentage of inbound call revenue. This is common in virtual number services used for call centers or verification systems.

Rate changes must be communicated with advance notice—typically 30 days—and cannot be applied retroactively. The agreement should also specify whether rates are exclusive of VAT, GST, or other taxes, and who bears the cost of regulatory fees. Transparent pricing prevents conflicts and supports long-term partnerships. For providers looking to compare current market rates, the Buy VoIP Routes section on VoIP Wholesale Forum offers real-time pricing data from multiple carriers.

Service Level Agreements and QoS Metrics

Quality of Service (QoS) is non-negotiable in a voip contract. The SLA section defines measurable performance standards and remedies for failure. Key metrics include ASR (Answer Seizure Ratio), ACD (Average Call Duration), PDD (Post-Dial Delay), and MOS (Mean Opinion Score). A typical SLA might require an ASR of at least 85% for all destinations, with penalties if it drops below 75% for three consecutive days. ACD should exceed 60 seconds; lower values may indicate fraud or misrouting. PDD must be under 1,500ms for 95% of calls, and MOS should average 3.8 or higher, measured via POLQA or PESQ algorithms.

The agreement should specify how these metrics are calculated. For example, ASR is (Answered Calls / Total Seizures) × 100, where “Answered Calls” are those with RTP flow and duration ≥ 6 seconds. CDRs must be provided daily in a standardized format, allowing both parties to audit performance independently. Discrepancies can be resolved using third-party tools like PortaSwitch or VOS3000, which support built-in reporting and fraud detection. If SLA thresholds are breached, the buyer is typically entitled to service credits—e.g., 10% of the affected traffic value for ASR below 75%.

Network uptime is another SLA component, often guaranteed at 99.9% monthly. Downtime exceeding 43 minutes in a month triggers compensation. The contract should also define failover procedures: if the primary route fails, traffic must automatically reroute to a backup trunk within 30 seconds. This is critical for mission-critical clients like emergency services or financial institutions using IVR systems. Additionally, the seller must provide real-time SIP OPTIONS ping monitoring and alert the buyer of any degradation. Tools like FreeSWITCH and Asterisk can be configured to generate these alerts and log them for SLA verification. For deeper insights into network performance, visit the VoIP Forum to discuss best practices with other engineers.

Regulatory Compliance and Numbering

Compliance with national and international telecom regulations is a cornerstone of any wholesale voip contract. The agreement must require both parties to adhere to local laws, including those enforced by the FCC (USA), Ofcom (UK), TRAI (India), and PTA (Pakistan). This includes lawful interception capabilities, data retention (typically 12 months of CDRs), and adherence to number portability rules. For example, in the EU, carriers must support ENUM and comply with GDPR when handling subscriber data.

The numbering section specifies whether the seller provides DIDs (Direct Inward Dialing numbers) and under what conditions. If DIDs are included, the contract must state whether they are local, national, or toll-free, and whether they support SMS or fax. It should also clarify ownership: in most cases, the seller retains ownership of the numbers and leases them to the buyer. Unauthorized resale or number spoofing is strictly prohibited. CLI (Calling Line Identification) must be passed accurately and in compliance with destination country rules. For instance, Japan requires full CLI for all incoming international calls, while Germany blocks calls with private or withheld numbers.

The agreement should include a clause requiring both parties to register with relevant regulatory bodies and maintain valid licenses. It must also address STIR/SHAKEN implementation for call authentication in North America. Carriers failing to sign calls properly may have their traffic flagged or blocked by terminating operators. Additionally, the contract should prohibit the use of numbers associated with high fraud risk, such as premium-rate or geographic numbers in unstable regions. Non-compliance can result in blacklisting by carriers like Tata Communications or BT, damaging long-term business prospects. For startups navigating these complexities, the How to Start a VoIP Business - Step by Step Guide offers practical compliance checklists.

Billing and Invoicing Procedures

Billing accuracy is paramount in a voip wholesale agreement template. The contract must define the billing cycle (e.g., monthly, net-30), currency (usually USD), and method of CDR delivery. CDRs should be provided daily via SFTP in a predefined format, including fields like Origination IP, Destination Number, Call Start Time, Duration, ASR, and PDD. Any deviation—such as missing records or incorrect timestamps—can lead to disputes. The agreement should allow for a 72-hour reconciliation window, during which both parties can submit adjustments.

Invoices are typically generated from aggregated CDRs and must include a detailed breakdown of traffic by destination, total minutes, rate, and any deductions (e.g., SLA credits or fraud adjustments). Payment is usually via wire transfer, with late fees applied at 1.5% per month for overdue amounts. The contract should also specify whether prepayment or credit limits apply. For new carriers, a postpaid model with a $5,000 credit cap is common, while established operators may negotiate higher limits.

Fraud detection is a shared responsibility. The agreement should require real-time monitoring for anomalies like sudden spikes in call volume, high NER (e.g., > 5%), or calls to high-risk destinations (e.g., Somalia, Yemen). If fraud is detected, both parties must notify each other within 2 hours and freeze further billing. The contract should outline how fraudulent minutes are calculated and deducted—typically at the seller’s discretion, with evidence provided. Disputes over billing must be resolved within 14 days, with unresolved cases escalating to arbitration. Integration with billing platforms like PortaBilling or Oasis ensures automated invoicing and reduces manual errors. For more on this, explore VoIP Billing Platforms for Wholesale Carriers.

Termination and Dispute Resolution

The termination clause in a wholesale agreement template defines how and when either party can end the contract. Standard notice periods are 30 to 90 days, but immediate termination is allowed for material breaches like fraud, non-payment, or regulatory violations. The agreement should specify whether traffic must be gradually migrated or can be cut off instantly. Abrupt termination can disrupt downstream customers, so a phased approach is often preferred.

Dispute resolution mechanisms are equally important. Most contracts require mediation before litigation, with disputes handled by a neutral third party in a neutral jurisdiction. If mediation fails, arbitration under ICC or UNCITRAL rules is common. The contract should state that the prevailing party is entitled to legal fees, incentivizing good faith negotiations. Technical disputes—such as conflicting CDR reports—should be resolved using agreed-upon monitoring tools like Wireshark packet captures or SIP trace logs from FreeSWITCH.

The agreement must also cover post-termination obligations. These include final billing reconciliation, return of confidential data, and deletion of network access credentials. Sellers should disable SIP trunks and revoke IP whitelisting within 24 hours of termination. Buyers must cease using any assigned DIDs or branding. Data retention policies apply even after termination—CDRs must be kept for at least 12 months for audit and compliance purposes. Failure to comply can result in regulatory penalties, especially in markets with strict data laws like the EU or Australia.

Sample Clauses for Your VoIP Contract

Below are real-world clauses you can adapt for your voip contract:

• Force Majeure: “Neither party shall be liable for failure to perform due to events beyond reasonable control, including natural disasters, war, government actions, or major network outages, provided written notice is given within 48 hours.”
• Fraud Liability: “The originating party is solely responsible for fraudulent traffic. If fraud is detected, the originator must reimburse the terminator for all costs incurred, including lost revenue and regulatory fines.”
• IP Whitelisting: “All SIP traffic must originate from pre-registered IP addresses. Unauthorized IPs will be blocked without notice. Changes require 24-hour advance submission via the portal.”
• CDR Retention: “Both parties agree to retain CDRs for a minimum of 365 days and provide access upon written request for audit or dispute resolution.”
• Rate Changes: “The seller may adjust rates with 30 days’ written notice. Adjustments shall not apply to traffic generated before the effective date.”

These clauses provide legal clarity and operational consistency. They can be customized based on the risk profile of the counterparty and the destinations involved. For high-risk regions, additional clauses on traffic filtering and real-time monitoring may be necessary. Always have legal counsel review the final document before signing.

How to Use a Carrier Agreement Template Effectively

A carrier agreement template is only valuable if used correctly. Start by customizing it for your business model—whether you’re a buyer, seller, or both. Remove irrelevant sections and add specific technical requirements for your infrastructure, such as support for SIP over TLS or IPv6 addressing. Define clear escalation paths for technical and billing issues, including SLA breach notifications and fraud alerts.

Use the template as a negotiation tool, not a final document. Share it early in discussions to align expectations. Store signed agreements securely and link them to your billing system for automated rate application. Regularly audit performance against SLA metrics and update the contract annually to reflect market changes. Platforms like VoIP Wholesale Forum allow members to share anonymized contract insights and benchmark their terms against industry standards. By treating the agreement as a living document, you ensure ongoing compliance, profitability, and network reliability.

Frequently Asked Questions

What is the difference between a VoIP wholesale agreement and a retail contract?

A VoIP wholesale agreement governs business-to-business traffic termination at scale, focusing on per-minute rates, CDRs, and SLAs. Retail contracts, in contrast, are consumer-facing and cover subscription fees, service features, and end-user support. Wholesale agreements involve higher volumes and lower margins, with technical and regulatory clauses absent in retail plans.

Can I use a free VoIP wholesale agreement template from the internet?

You can, but generic templates often lack jurisdiction-specific clauses, technical depth, or fraud protections. It’s safer to use a professionally drafted template from a trusted source like VoIP Wholesale Forum and have it reviewed by legal counsel familiar with telecom law.

How do I verify a carrier’s ASR and MOS before signing?

Request sample CDRs, conduct test calls using tools like SIPP or RTP-Play, and use platforms like PortaSwitch to analyze MOS. You can also check reputation on the VoIP Forum and ask for references from existing clients.

What happens if a carrier violates the agreement?

The non-breaching party can issue a notice of default, demand corrective action, and if unresolved, terminate the contract. Financial damages, SLA credits, or arbitration may follow, depending on the clause. Always document violations with CDRs and SIP traces.

Is STIR/SHAKEN required in a wholesale VoIP contract?

Yes, if terminating traffic in the US or Canada. The agreement should require all SIP calls to be signed with a valid attestation level (A, B, or C). Unsigned or improperly signed calls may be rejected by terminating carriers, leading to revenue loss.

A well-structured voip wholesale agreement template is more than a legal formality—it’s a strategic tool for building reliable, profitable carrier relationships. By including clear pricing, enforceable SLAs, and robust compliance clauses, you reduce risk and ensure smooth operations. Use this guide to audit your current contracts and improve your negotiation position. For ongoing support, rate comparisons, and peer insights, join the Register today and connect with the global VoIP wholesale community.