The ASTPP v7 launch webinar brought together telecom operators, ITSPs, and wholesale carriers looking to explore how modern VoIP billing software can improve billing automation, routing efficiency, and reseller management.

The live Q&A session generated several important ASTPP v7 webinar questions focused on scalability, deployment, billing, compliance, and carrier operations.

This blog post will cover the most interesting questions asked during the webinar with complete answers based on how the ASTPP VoIP billing platform helps operators increase revenue, simplify operations, and scale without rebuilding their infrastructure. 

If you participated in the webinar and would like to learn more about the topics discussed, you’re in the right place. Here, you’ll find expanded insights, explanations, and additional information related to the webinar session. 

So, let’s get into the questions asked during ASTPP v7 webinar. 

Q1: What Makes ASTPP v7 Genuinely Different from Previous Versions? 

This came up in different forms throughout the session. The short answer is that v7 treats revenue and operations as two separate priorities rather than bundling everything under general improvements. 

The platform introduces 21 new features and more than 30 enhancements across billing, routing, DID management, reporting, and security. These updates strengthen ASTPP as a carrier-grade VoIP billing platform for telecom operators looking to modernize billing and routing workflows. 

On the revenue side, operators can now bill for SMS alongside voice, apply time-based surge charges, support vanity number assignments, run an auto dialer with AMD detection, and offer weekly billing cycles in addition to daily and monthly ones. These are not edge features. They represent real monetization options that previously required third-party tools or custom builds. 

On the operations side, rate templates reduce the work of managing bulk rate updates. Origination rate history now gives operators an audit trail. Scheduled report delivery automates the weekly or monthly reporting workflow.  

These are not just feature upgrades. They directly improve operational efficiency and revenue management for operators using enterprise-grade VoIP billing software. 

Q2: How Does the SMS Billing Feature Work for a Telecom Operator? 

Several attendees asked about the mechanics behind SMS billing, particularly whether it required separate infrastructure. 

It does not. ASTPP v7 integrates SMS billing and delivery directly into the existing billing engine. Operators can manage SMS origination and termination rates the same way they manage voice call rates. Customers receive consolidated invoices covering both voice and SMS usage, which simplifies billing administration significantly. 

Nexmo (now Vonage) is supported by default as an SMS gateway, and the platform allows custom third-party SMS gateways to be added. Operators can offer free or paid SMS bundles, one-time or recurring, and track inbound and outbound usage through comprehensive reporting. 

For operators already running a VoIP billing platform for telecom operators and looking to grow revenue per customer, SMS bundling is a practical step. 

Q3: Can ASTPP Handle Real-Time Billing Across Prepaid and Postpaid Accounts? 

This question comes up in almost every platform evaluation. The concern is usually about whether the Online Charging System can keep pace with call volume in real time without impacting routing performance. 

ASTPP includes a built-in OCS that handles real-time VoIP billing for both prepaid and postpaid customers from the same platform. Prepaid accounts are charged in real time during the call, with balance checks and automatic disconnection when credit runs out. Postpaid accounts accumulate usage and are billed at the end of the cycle. Both models run in parallel within the same multi-tenant environment. 

This is one area where ASTPP differs from platforms that handle one model well but force workarounds for the other. The OCS and billing engine were built together, not integrated after the fact, which is why the real-time billing and routing system performs consistently at scale. 

Q4: How Does Multi-Tenant Billing Work in Practice? 

ASTPP is built as a multi-tenant VoIP billing platform from its core, not retrofitted. The hierarchy runs from Super Admin through Admin to Reseller to Customer. Each level has its own rate plans, balance visibility, billing configuration, and portal access. Resellers can manage their own customers without needing admin-level access to the parent system. 

What this means operationally is that a wholesale carrier running 50 resellers does not need to build custom isolation logic. Rate templates added in v7 make bulk rate management across reseller groups faster. A reseller can receive a rate update across all their customers in a single configuration step rather than updating each account individually. 

Businesses looking for a reliable wholesale VoIP billing solution need advanced routing, real-time charging, accurate invoicing, and fraud management capabilities.

Q5: What Deployment Options Are Available, and Is Cloud Deployment Production-Ready? 

Deployment flexibility came up repeatedly, particularly from operators who had experienced rigid installation requirements with other platforms. 

ASTPP v7 supports four deployment models: single-node deployment for smaller operations, cloud-native for operators prioritizing flexibility and managed infrastructure, on-premises for operators who need physical control over their environment, and HA cluster with geographic redundancy for carriers that require continuous uptime. 

Cloud deployment is production-ready and used by operators in live environments today. The platform runs on standard Linux-based infrastructure and was updated to PHP 8.2 as part of v7 to improve performance and security across all deployment types. For operators looking to learn how to deploy a VoIP billing system, ASTPP documentation covers each deployment model with configuration guidance. 

One point worth noting: operators moving from shared hosting or legacy infrastructure sometimes ask about minimum requirements. The answer depends on call volume and reseller count. The Inextrix team provides sizing guidance as part of the deployment conversation. 

Q6: How Does the LCR Engine Work and How Do Operators Manage Routing Across Multiple Carriers? 

ASTPP includes a built-in Least Cost Routing engine that evaluates routes by cost, quality, and priority. Operators configure carriers, assign rate decks, and set failover rules. When a call comes in, the LCR engine selects the best available route based on the configured logic, without requiring manual intervention per call. 

In v7, the CLI Assignment feature extends routing control further. Operators can assign caller line identification based on destination country and configure the system to use a random DID as the CLI when no specific rule applies. This reduces manual configuration overhead and ensures calls route with the correct presentation regardless of destination. 

For wholesale carriers managing high call volumes, the combination of LCR and CDR-level reporting gives full visibility into where calls are routing, what they cost, and where margin is being lost. Therefore, getting LCR right is not a technical detail. It is a margin decision. 

Q7: What Security and Compliance Features Are Included in ASTPP v7? 

ASTPP v7 added Single Sign-On (SSO) with Google and Microsoft, which addresses an access control requirement that many operators need before deploying to enterprise customers. Do Not Call list management, Allow and Deny list filtering by prefix, and KYC-based country-specific DID verification round out the compliance layer. 

The fraud detection engine received improvements as part of this release, with enhanced checks and alerts for suspicious call activity. Call control in the live report screen allows operators to manually stop calls during switch maintenance, returning controlled 503 responses rather than abrupt disconnections. 

On the infrastructure side, frameworks were updated for security hardening and debug log auto-disable functionality was added to prevent CPU and disk overload from prolonged debug sessions. 

Q8: Is ASTPP a Genuine Open-Source VoIP Billing Platform, and What Does That Mean for Customization? 

ASTPP is an open-source VoIP billing platform. Operators have access to the codebase, which means the platform can be modified to fit the business model rather than forcing the business model to fit the platform. This is where ASTPP differs most sharply from commercial platforms like PortaOne or Cerillion, where customization requires going through the vendor. 

In practice, open-source means operators can build features unique to their market, integrate with their existing CRM or ERP systems, and extend the API layer. The REST API supports integrations with Zoho, WHMCS, Vtiger, Salesforce, and Stripe. Custom development work is available through Inextrix directly or through community resources. 

For operators who want platform capabilities rather than just billing software, the open-source model is not just a cost consideration. It is a strategic one. 

Q9: What Is the Upgrade Path from Community Edition to ASTPP v7 Enterprise? 

The upgrade path is handled through the Inextrix account management and sales team. The process typically involves a review of the current installation, data migration planning, and a staged upgrade that minimizes downtime. The team provides guidance on what changes between versions and what configuration updates are needed. 

For Community Edition users specifically, the transition to Enterprise brings access to the full feature set including all v7 revenue and compliance capabilities, direct support, and access to the development roadmap. Given that v7 includes 21 new features not available in the Community Edition, the upgrade conversation is worth having. 

Q10: How Does ASTPP Compare to Platforms Like PortaOne for a Wholesale Carrier? 

The practical differences center on cost, customization, and deployment speed. PortaOne targets large enterprise carriers with corresponding licensing costs and implementation timelines that can run 12 to 18 months. ASTPP delivers carrier-grade VoIP billing and softswitch capabilities at a fraction of that cost, with deployments that go live in weeks rather than months. 

From a feature standpoint, ASTPP covers Class 4 and Class 5 softswitch, BSS with OCS, real-time billing, LCR, SBC, multi-tenant reseller billing, CDR processing, and DID management. The VoIP softswitch platform FAQ question that comes up most often is whether ASTPP handles carrier-scale call volumes. The answer is yes. The platform is deployed across 20,000 operators in more than 95 countries, including wholesale carriers managing high concurrent call loads. 

Key Takeaways from the ASTPP v7 Webinar 

The webinar reinforced a simple reality: telecom operators do not need more disconnected VoIP billing software tools. They need a complete platform that improves revenue, simplifies operations, and scales efficiently. 

ASTPP v7 is designed with that in mind. Features like SMS billing and surge charges support revenue growth. Rate templates and scheduled reporting improve daily operations. SSO, KYC, and fraud management strengthen compliance and security.  

By combining carrier-grade functionality with the flexibility of an open-source VoIP billing platform, ASTPP helps operators scale without rebuilding their billing stack every few years. 

Ready to see ASTPP v7 in action?

Book a Demo

Contact Us Now