ASTPP just launched v7.0.2 new features and VoIP billing software update that redefine telecom operations. Managing VoIP billing today demands real-time accuracy, carrier-grade reliability, multi-tenant control, and margin protection.  ASTPP is built to solve exactly that. Trusted by more than 20,000 telecom operators across 95+ countries, ASTPP is an open-source, carrier-grade VoIP billing and softswitch platform that combines Class 4 and Class 5 switching, a complete BSS with Online Charging System (OCS), Least Cost Routing (LCR), and full multi-tenant billing architecture in a single deployable platform. 

For telecom businesses, standing still is not an option. Regulatory environments shift. Carrier relationships evolve. Reseller hierarchies grow more complex. A billing platform that doesn’t keep pace becomes a liability. That’s why continuous, purposeful product releases matter: they address real operator pain points, close compliance gaps, and push the performance envelope where it counts. 

ASTPP v7.0.2, released in April 2026, is one of the most comprehensive updates in recent memory. The numbers alone tell a story: 

  • 63 total changes 
  • 9 new features 
  • 12 improvements 
  • 42 bug fixes 

Behind each of those numbers is a real operational problem that an ASTPP operator raised, and a solution the engineering team provided. This post covers every major change in v7.0.2, what it means for your business, and why upgrading is worth your attention. 

ASTPP v7.0.2: At a Glance

Before getting into individual features, let’s take a look at what this version brings operationally: 

  • Performance: Routing code optimizations, database improvements, and PHP 8.2 monitoring bring measurable stability gains for high-volume platforms. 
  • Compliance: Country-specific KYC verification is now built natively into the DID purchase workflow, removing a longstanding gap for operators in regulated markets. 
  • Automation: CLI assignment, session timeouts, and routing trunk enforcement are now configurable through rules rather than manual intervention, reducing operator overhead on routine tasks. 
  • User experience: The DID configuration form has been redesigned from scratch. Account management has improved. Admin workflows that used to require workarounds now just work. 

Who should upgrade? Short answer: everyone running an ASTPP deployment in production. The 42 bug fixes alone span SIP device handling, CDR billing accuracy, DID routing, IVR/PBX logic, and payment processing. If you have any of these functions active on your system, this version is just right for you. VoIP service providers, ITSPs, resellers managing multi-level billing, and call center operators will all see something useful in this release that makes them more efficient or helps them grow. 

Key New Features in ASTPP v7.0.2

Below explained are some of the top key features in ASTPP v7.0.2

1. DID Provider Trunk Enforcement

What it is: This feature gives platform administrators the ability to force outbound DID calls through a specific provider trunk, rather than leaving routing decisions to the general routing engine. 

How it works: Administrators assign a designated trunk to a DID or a group of DIDs at the configuration level. When a call is processed, the platform enforces that trunk selection for outbound delivery, bypassing competing routing paths. 

Business benefits: 

  • Better routing control: You decide which carrier handles specific DID traffic, not the algorithm. This matters when you have SLAs with specific carriers or when certain DIDs need to stay on premium routes. 
  • Cost optimization: Predictable trunk assignment means predictable per-minute costs. Operators running LCR across many carriers often find that forcing certain DID traffic through negotiated-rate trunks reduces margin leakage. 
  • Fault isolation: When something goes wrong, you know exactly which trunk was used. Debugging a routing issue across an open pool of carriers is far harder than checking a single enforced path. 

2. Country-Specific KYC Verification

What it is: Customers must now complete a country specific Know Your Customer (KYC) verification process before they can purchase or be assigned a DID number. 

How it works: The KYC requirement is tied to the country associated with the DID being requested. Each country can have its own verification rules and document requirements configured in the platform. A customer who hasn’t completed the required KYC for that country cannot proceed with the DID assignment. 

Business benefits: 

  • Regulatory compliance: In many markets, telecom regulators require identity verification before number assignment. This feature makes ASTPP deployments compliant with those requirements without custom development. 
  • Reduced legal risk: Operators no longer have to rely on external workflows or manual checks to satisfy KYC obligations. The platform enforces it at the point of purchase. 
  • Fraud prevention: Unverified entities obtaining DIDs is a known vector for toll fraud and call spoofing. Mandatory KYC raises the barrier to abuse. 

Also Read: VoIP Fraud: Everything You Need to Know 

1. Automatic CLI Assignment & Non-CLI Rating

What it is: The platform now auto-assigns CLI (Calling Line Identification) based on pre-configured rules and applies a separate rating logic for calls that arrive without a valid CLI. 

How it works: Administrators define CLI assignment rules at the account or routing level. When a call matches those rules, the CLI is assigned automatically before the call is processed. For calls where no CLI is present or the CLI doesn’t match any rule, the platform applies a designated non-CLI rating profile, which can have different pricing, routing, or blocking behavior than standard CLI calls. 

Business benefits: 

  • Improved billing accuracy: Calls that previously fell through the cracks because of missing CLI can now be rated correctly rather than misclassified or dropped. 
  • Reduced manual configuration: CLI assignment used to require manual intervention or custom scripts on many deployments. Rules-based automation handles it at scale. 
  • Granular control over non-CLI traffic: Non-CLI calls often come from specific origination types. Having a separate rating profile for them gives operators meaningful control over how that traffic is priced and handled. 

2. Origination Rate History Tracking

What it is: ASTPP now maintains a complete history of origination rate changes per destination, including the timestamp of each change and tooltip support for quick review. 

How it works: Any time an origination rate is modified, the change is logged with a timestamp and stored against the destination record. Administrators can view the full rate history from the rate management interface, with tooltips surfacing the most recent change details inline. 

Business benefits: 

  • Audit readiness: In a dispute or regulatory review, having timestamped rate history is essential. This feature makes that data available without needing to pull from external logs or reconstruct changes manually. 
  • Transparency in carrier management: Rate negotiations and carrier agreements  change over time. A visible history helps operators verify that agreed rates were actually applied and when. 
  • Easier troubleshooting: When a billing discrepancy is reported, the first question is usually “what rate was active at that time?” This feature answers it directly. 

3. SIP Device Limit & Default SIP Profile

What it is: Administrators can now set a maximum number of SIP devices allowed per account and define a default SIP profile that applies to new device registrations automatically. 

How it works: The account configuration panel now includes a SIP device limit field. When an account reaches that limit, additional device registrations are rejected. The default SIP profile setting assigns a standard profile to new devices without requiring manual selection each time. 

Business benefits: 

  • Better account control: For resellers managing downstream customers, device  limits prevent a single account from consuming disproportionate registration capacity on a shared platform. 
  • Improved security posture: Limiting the number of registered devices per account reduces the potential blast radius if an account credential is compromised. 
  • Faster onboarding: Default SIP profiles mean new devices come up with the right configuration automatically, reducing setup time for operators managing large device fleets. 

4. Multiple Click-to-Call Tokens per Account

What it is: Each customer account can now hold multiple Click-to-Call tokens, each with its own configuration, enabling separate integrations without token conflicts. 

How it works: The Click-to-Call addon interface now supports token management at the account level. Administrators can create, label, and configure multiple tokens per account. Each token operates independently, so an integration using Token A has no visibility into or conflict with an integration using Token B on the same account. 

Business benefits: 

  • Flexibility for multi-integration environments: Customers using ASTPP’s Click-to-Call in more than one application, for example, a CRM and a web widget simultaneously will no longer need separate accounts to avoid token collisions. 
  • Per-integration tracking: With separate tokens, usage analytics and billing attribution are cleaner. You can see exactly which integration is generating which call volume. 
  • Supports reseller and SaaS use cases: Resellers building applications on top of ASTPP can issue unique tokens per end-customer integration without multiplying account overhead. 

5. Dynamic Session Timeout Configuration

What it is: Session timeout values can now be configured dynamically from the admin settings panel. Previously, these were hardcoded values that required code-level changes to modify. 

How it works: A new settings field in the admin panel accepts a custom timeout duration. This value is applied at runtime, meaning changes take effect without redeployment. Admins managing environments with different security policies or usage patterns can tune timeout behavior to match their operational requirements. 

Business benefits: 

  • Better session management: Operators with strict security policies can enforce shorter timeouts. Environments with complex workflows can allow longer sessions without artificial interruptions. 
  • Scalability without code changes: Hardcoded values become friction points as platforms scale. Moving session timeout to a configurable setting removes one more reason to touch the codebase. 
  • Reduced dependency on development teams: Operational tuning that previously required a developer can now be handled by an admin. 

Ready to see these features in action? : Book a Demo Now 

Notable Improvements in v7.0.2

1. Simplified Call Recording Configuration

Call recording settings have been removed from the Provider entity. This is a deliberate UX improvement, not a feature reduction. Having call recording options inside the Provider configuration caused confusion because Provider-level settings often conflicted with or shadowed more specific settings elsewhere in the platform. 

Benefits for operators: 

  • Cleaner account management: The Provider configuration form now covers what it should and nothing more. Operators setting up new provider accounts face less cognitive overhead. 
  • Fewer misconfiguration incidents: Call recording conflicts were a recurring support issue. Removing the duplicate setting path eliminates the category of problem. 
  • Easier onboarding for new admin users: A simpler form is a faster form. Operators training new team members spend less time explaining why certain settings exist in unexpected places. 

2. Refactored DID Configuration Form

The DID configuration form has been rebuilt from scratch. The refactor covers layout, input validation, field grouping, and the underlying code structure that makes the form maintainable going forward. 

Benefits for operators: 

  • Faster DID setup: A cleaner layout with logical field grouping means fewer clicks and less time hunting for the right field. 
  • Better validation feedback: Improved inline validation catches errors at input time rather than after a failed save, reducing the back-and-forth that slowed configuration workflows. 
  • Foundation for future DID features: The refactored form is built to accommodate the DID-related features on the v7.1 roadmap without further structural work. 

3. Bug Fixes & System Enhancements

42 bug fixes is not a routine cleanup pass. It reflects disciplined quality control across the platform’s most traffic-sensitive modules. Here’s where the fixes landed: 

  • SIP Devices (5 fixes): Registration edge cases, device state handling, and profile assignment issues that affected certain deployment configurations.
  • DID & DID Forwarding (4 fixes): Routing inconsistencies and forwarding rule evaluation bugs that caused unexpected call behavior on affected DIDs.
  • PBX / IVR (3 fixes): Menu traversal and extension handling issues in IVR flows that caused dropped or misdirected calls.
  • CDRs  & Calls (4 fixes): Record generation accuracy improvements that directly affect billing integrity. Any CDR-level fix is a revenue assurance fix.
  • Auto Dialer (2 fixes): Campaign execution reliability improvements for operators running outbound calling operations.
  • Stripe Payment (1 fix): Resolved a payment processing edge case affecting account top-up reliability for operators using Stripe as a payment gateway.
  • Rate Simulator (1 fix): Corrected a simulation calculation issue that affected rate testing accuracy.
  • Click-to-Call (2 fixes): Reliability improvements for token-based call initiation flows.
  • Quality Routes (2 fixes): Route evaluation logic corrections that improve routing decision accuracy for quality-based routing configurations.
  • Other  (7 fixes): Miscellaneous stability and edge-case corrections across  multiple modules.

Infrastructure improvements in this release include PHP 8.2 monitoring support, migration to versioned SQL files for more reliable database update management, and version handling flow improvements that make upgrade paths cleaner for operators managing self-hosted deployments. 

These infrastructure changes matter operationally: versioned SQL files mean database migrations are trackable and reversible in a way they weren’t before. For operators managing compliance audits or change control processes, that’s a meaningful improvement. 

Business Benefits of ASTPP v7.0.2

1. Operational Efficiency

Automatic CLI assignment, dynamic session timeout configuration, default SIP profile enforcement, and DID trunk enforcement all reduce the volume of manual work that platform administrators handle daily. Across a multi-tenant environment serving dozens of resellers and hundreds of end customers, that adds up quickly. 

2. Compliance & Security

Country-specific KYC verification and SIP device limits address two distinct compliance and security concerns: regulatory identity requirements for number assignment and access control risk at the account level. Operators in regulated markets particularly benefit, as these are requirements they would otherwise have to solve through custom development or external tooling. 

3. Cost Optimization

DID Provider Trunk Enforcement and the CLI rating improvements directly affect per-call costs and billing accuracy. Controlling which trunk handles specific traffic eliminates unintended routing to higher-cost carriers. Accurate CLI rating ensures that non-standard traffic is priced correctly rather than rated at incorrect or default rates that distort margins. 

4. Transparency & Analytics

Origination rate history tracking with timestamp support gives operators a verifiable record of rate changes over time. For businesses managing complex carrier relationships or operating under billing dispute risk, this is a direct risk-reduction tool. Paired with the CDR bug fixes in this release, the billing accuracy picture in v7.0.2 is meaningfully cleaner than prior versions. 

5. Scalability

Dynamic session timeout configuration and multiple Click-to-Call tokens per account are both about removing hard limits that constrain growth. An operator scaling from 50 to 500 accounts should not have to file a development request to tune a timeout value or manage token conflicts in an integration layer. These features extend the platform’s operational ceiling without adding architectural complexity. 

Want to discuss how v7.0.2 fits your deployment? : Talk to our Experts 

Who Should Upgrade to ASTPP v7.0.2?

Any operator running an ASTPP deployment in a production environment should upgrade to ASTPP v7.0.2. However, it also depends on your business model. 

1. VoIP Service Providers

The CLI assignment automation, rate history tracking, and DID trunk enforcement features are directly relevant to providers managing volume traffic and carrier relationships. The CDR and routing bug fixes address stability issues that affect billing integrity on live traffic. 

2. Telecom Carriers & Wholesale Operators

Carrier-grade deployments will benefit most from the infrastructure improvements like PHP 8.2 monitoring, versioned SQL migrations, and the routing bug fixes. DID trunk enforcement is particularly valuable for wholesale operators running carrier specific DID pools on separate trunks. 

3. Call Centers & BPO Operators

The Auto Dialer fixes, IVR/PBX improvements, and the SIP device limit feature address operational concerns common in call center environments including campaign reliability, IVR call flows, and device fleet management under a multi-tenant billing model. 

4. Resellers & Multi-Tenant Operators

Multiple Click-to-Call tokens per account and SIP device limits are features built with reseller architectures in mind. KYC enforcement also matters for resellers operating in regulated markets where they carry compliance responsibility for their downstream customers. 

What’s Coming Next: ASTPP v7.1 Roadmap

The v7.0.2 release notes from the internal roadmap give a preview of where the platform is heading next. v7.1 has five confirmed new features and three performance improvements on the agenda: 

New features:

1.IP Security Module: A dedicated module for IP-level access control, addressing a recurring request from operators managing carrier and reseller access security.

2.MNP Lookup: Mobile Number Portability lookup integration, enabling the platform to correctly route and rate calls to ported numbers without manual carrier table updates.

3.Optional X-Header parameter for IP Authentication: Adds flexibility to SIP request authentication workflows without requiring structural changes to existing trunk configurations.

4.SIP CIDR: Network-level SIP authorization control, allowing admins to define authorized IP ranges rather than managing individual IP entries.

5.Auto Import Termination Rates: Automates the rate import workflow, eliminating manual uploads for carriers that deliver rate decks on a schedule.

Platform improvements:

1. Real-Time Data Table Updates via Inline Editor: Live editing of data records without page reloads, reducing admin friction on high-frequency configuration tasks.

2. Database Optimization & Performance Tuning: Query-level improvements targeting the database layer, where performance gains have the most direct impact on billing accuracy under high call volume.

3. Lua Routing Code Performance Optimization: Routing logic improvements at the script level, expected to reduce routing decision latency on large routing tables.

The v7.1 roadmap is consistent with the direction ASTPP has been moving while reducing manual operator overhead, extending compliance capability, and improving raw performance under scale. Operators who upgrade to v7.0.2 now will be better positioned to adopt v7.1 features incrementally as they ship. 

Conclusion:

ASTPP v7.0.2 is not a maintenance release. Across 9 new features, 12 improvements, and 42 bug fixes, it addresses real operational problems that telecom operators face in production. 

For operators evaluating whether to upgrade, the question is less about whether ASTPP v7.0.2 new features offer something relevant to your environment and more about which of the changes will have the highest immediate impact on your operations. The answer to that depends on your deployment model, but the CDR bug fixes and routing improvements alone are worth the upgrade cycle for any operator running live traffic. 

ASTPP continues to develop in the direction that matters most to carrier-grade operators. It ensures less manual work, more automation, better compliance tooling, and a platform architecture that scales with your business rather than constraining it. 

Ready to move your VoIP billing and softswitch platform forward? 

Upgrade to ASTPP v7.0.2

Book a Demo Now