Virtual Testing Phones
Testing your application with Naxai
When integrating Naxai into your application, testing is critical. While sending real messages through the platform can help validate your integration, it should not be your primary testing strategy. Using real SMS for testing has two main limitations:
- Cost: Each request sent through real networks may generate charges, making iterative testing expensive.
- Limited control: Reproducing specific scenarios—especially error cases or edge conditions—can be difficult or impossible in real-world communication flows.
To address this, Naxai provides Virtual Testing Phones specifically designed for development and testing.
What are Virtual Testing Phones?
Virtual Testing Phones allow you to simulate realistic interactions with Naxai services without sending messages over carrier networks. This enables you to:
- Send fully simulated requests
- Validate your application behavior in a predictable environment
- Test success and failure scenarios that are hard to reproduce with real devices
- Run tests without any cost
By using Virtual Testing Phones, you can safely build, debug, and validate your integration before moving to production.
How to test with Virtual Testing Phones
Each Virtual Testing Phone is associated with a specific SMS Status.
For example: Sending a message to 32450500200 will always be delivered successfully.
You can use the Virtual Testing Phones in all SMS applications like SMS API, Quick SMS, SMS Broadcasts... and you will receive the SMS events via webhook if configured.
Virtual Testing Phone will be associated with the MCC 206 (Belgium) and MNC 90 (Virtual Testing Phones).
List of Virtual Testing Phones
Here is the list of supported Virtual Testing Phones.
The 3 last digits of the number represent the SMS Status code associated as a response.
See https://docs.naxai.com/docs/status-error-codes
| Virtual Testing Phones | Status |
|---|---|
| 32450500200 | 200-delivered |
| 32450500302 | 302-no-premium |
| 32450500303 | 303-no-premium-roaming |
| 32450500305 | 305-no-credit |
| 32450500309 | 309-no-provider |
| 32450500320 | 320-network |
| 32450500321 | 321-refused-operator |
| 32450500322 | 322-wrong-number |
| 32450500323 | 323-invalid-source |
| 32450500324 | 324-operator-policy |
| 32450500342 | 342-unknown-ack |
| 32450500343 | 343-unknown-dlr |
| 32450500344 | 344-absent |
| 32450500345 | 345-invalid-destination |
| 32450500351 | 351-expired |
| 32450500402 | 402-no-ack |
| 32450500403 | 403-no-dlr |
| 32450500540 | 540-fraudulent |
| 32450500541 | 541-spam |
| 32450500801 | 801-invalid-number |
| 32450500802 | 802-message-parts-exceeded |
| 32450500803 | 803-length-exceeded |
| 32450500804 | 804-trial-restriction |
| 32450500805 | 805-insufficient-credit |
| 32450500806 | 806-country-restriction |
| 32450500808 | 808-blacklisted |
| 32450500850 | 850-customer-canceled |
| 32450500851 | 851-system-canceled |
| 32450500852 | 852-system-failure |
| 32450500853 | 853-operator-failure |
| 32450500854 | 854-system-expired |
Remarks and Limitations
Virtual Testing Phones come with some limitations
- Virtual Testing Phones are only available for SMS products.
- SMS sent to Virtual Testing Phones will appear in Activity Logs, Metrics and Billing
- SMS sent to Virtual Testing Phones is free but will appear as a billed quantity.
Updated about 2 hours ago

