Understanding VOS3000 server end reasons is essential for any VoIP operator who needs to diagnose call failures, resolve billing disputes, and improve overall network quality. VOS3000 records 25 distinct server-side end reason codes in its CDRs, each representing a different cause for call termination as observed from the softswitch perspective. These codes go beyond simple SIP response codes or Q.850 cause values — they represent the VOS3000 internal decision for why a call ended, providing the most granular insight into call lifecycle events. Need help analyzing your CDRs? Contact us on WhatsApp: +8801911119966.
Unlike SIP response codes (which are protocol-level) or Q.850 cause codes (which are network-level), VOS3000 server end reasons are application-level codes generated by the softswitch itself. They capture scenarios that are unique to the VOS3000 platform, such as billing-related terminations, route selection failures, and account management events. By analyzing these codes across your CDR data, you can identify systemic issues affecting ASR, pinpoint billing discrepancies, and understand exactly why calls fail at the softswitch level.
The following table lists all 25 VOS3000 server-side end reason codes as documented in §4.5 of the administration manual. Each code has a specific meaning that maps to an internal VOS3000 decision point in the call processing pipeline.
| Code | End Reason | Category |
|---|---|---|
| 1 | Normal Clearing | Normal |
| 2 | User Busy | Normal |
| 3 | No Answer | Normal |
| 4 | Unallocated Number | Number Error |
| 5 | Network Congestion | Network |
| 6 | Route Not Found | Routing |
| 7 | Rate Not Found | Billing |
| 8 | Balance Insufficient | Billing |
| 9 | Account Expired | Account |
| 10 | Account Disabled | Account |
| 11 | Caller Hangup | Normal |
| 12 | Callee Hangup | Normal |
| 13 | Server Forced Release | System |
| 14 | Session Timeout | Timeout |
| 15 | Media Timeout | Timeout |
| 16 | Authentication Failed | Security |
| 17 | Unauthorized IP | Security |
| 18 | Concurrent Limit Exceeded | Capacity |
| 19 | CPS Limit Exceeded | Capacity |
| 20 | Blacklist Match | Security |
| 21 | Gateway Unavailable | Routing |
| 22 | No Available Route | Routing |
| 23 | Call Rejected | Network |
| 24 | Prepaid Duration Exceeded | Billing |
| 25 | Service Not Subscribed | Account |
The 25 VOS3000 server end reasons can be grouped into six functional categories. Understanding these categories helps operators quickly identify whether call failures are due to billing issues, routing problems, security blocks, or normal call completion events. For more on how these codes affect your quality metrics, see our VOS3000 ASR ACD analysis guide.
| Category | Codes | Impact Level | Action Required |
|---|---|---|---|
| Normal | 1, 2, 3, 11, 12 | Low | No action needed |
| Routing | 6, 21, 22 | High | Check rate table and gateway config |
| Billing | 7, 8, 24 | High | Review rates and account balances |
| Account | 9, 10, 25 | Medium | Verify account status and subscriptions |
| Security | 16, 17, 20 | Critical | Investigate unauthorized access attempts |
| Capacity/Timeout | 5, 14, 15, 18, 19 | Medium-High | Scale resources or adjust limits |
The most frequently encountered VOS3000 server end reasons in production environments typically fall into a handful of codes. Understanding what each means and how to address it is critical for maintaining healthy ASR and ACD metrics. For detailed SIP-level troubleshooting, see our VOS3000 SIP debug guide.
| Code | End Reason | Common Cause | Resolution |
|---|---|---|---|
| 6 | Route Not Found | No matching prefix in route table | Add prefix to routing configuration |
| 7 | Rate Not Found | Dialed prefix not in rate table | Add rate entry for missing prefix |
| 8 | Balance Insufficient | Prepaid account depleted | Recharge account balance |
| 22 | No Available Route | All gateways busy or offline | Add more gateways or check existing |
| 15 | Media Timeout | No RTP received after call setup | Check NAT/firewall, media proxy settings |
Certain VOS3000 server end reasons directly affect billing calculations. Code 8 (Balance Insufficient) and Code 24 (Prepaid Duration Exceeded) are billing-driven terminations initiated by the VOS3000 billing engine. Code 7 (Rate Not Found) means the call was never rated and generates no revenue. Understanding which end reasons produce billable vs non-billable CDRs is essential for revenue assurance. For more on billing configurations, see our VOS3000 billing system guide.
| End Reason | CDR Generated | Billable | Billing Mode Code |
|---|---|---|---|
| Normal Clearing (1) | Yes | Yes | 0 or 1 |
| Rate Not Found (7) | Yes | No | -1 |
| Balance Insufficient (8) | Yes | No | -1 |
| Prepaid Duration Exceeded (24) | Yes | Yes (partial) | 1 |
| Route Not Found (6) | Yes | No | -1 |
VOS3000 server end reasons are internal to the platform, but they often have corresponding SIP response codes or Q.850 cause codes in the signaling layer. Understanding these mappings helps correlate CDR end reasons with protocol-level traces captured by tools like Wireshark or tcpdump. For protocol-level analysis, message us on WhatsApp: +8801911119966.
| Server End Reason | SIP Response | Q.850 Cause |
|---|---|---|
| Normal Clearing | 200 OK (BYE) | 16 |
| User Busy | 486 Busy Here | 17 |
| No Answer | 408 Request Timeout | 18 or 19 |
| Route Not Found | 404 Not Found | 1 or 3 |
| Balance Insufficient | 403 Forbidden | 21 |
| Network Congestion | 503 Service Unavailable | 42 |
VOS3000 server end reasons are 25 internal codes that the softswitch records in CDRs to indicate why a call was terminated from the server’s perspective. These codes cover normal call completion (like user hangup and normal clearing), routing failures (like route not found and no available route), billing issues (like balance insufficient and rate not found), security events (like authentication failed and unauthorized IP), and system-level terminations (like server forced release and session timeout). They are documented in §4.5 of the VOS3000 administration manual.
VOS3000 server end reasons are application-level codes generated by the softswitch itself, while SIP response codes are protocol-level status indicators defined in RFC 3261. A single SIP response code like 503 Service Unavailable could map to multiple VOS3000 end reasons depending on the internal context — it could be Network Congestion (code 5), No Available Route (code 22), or Gateway Unavailable (code 21). Server end reasons provide more granular insight into the VOS3000 internal decision process than SIP codes alone.
The primary billing-related end reasons are Code 7 (Rate Not Found — no matching rate entry), Code 8 (Balance Insufficient — prepaid account depleted), and Code 24 (Prepaid Duration Exceeded — call ended because maximum allowed duration was reached). These codes directly indicate that billing engine decisions terminated the call. High volumes of code 7 suggest missing rate table entries, while high code 8 volumes indicate accounts running out of balance frequently.
You can analyze VOS3000 server end reasons by querying the CDR database and grouping records by end reason code. This reveals the distribution of call termination causes and helps identify systemic issues. For example, if code 22 (No Available Route) dominates, you need more gateway capacity. If code 7 (Rate Not Found) is frequent, you have gaps in your rate tables. Use the VOS3000 CDR query tools or export CDRs to an external analytics platform for detailed analysis.
Code 13 (Server Forced Release) indicates that the VOS3000 softswitch actively terminated the call for an internal reason, such as a system-level resource constraint, administrative intervention, or a forced disconnect triggered by a monitoring rule. Unlike timeout-based terminations, Server Forced Release is an active decision by the softswitch to end the call. Investigating the system logs around the time of the CDR can reveal the specific trigger for the forced release.
Yes, the 25 VOS3000 server end reason codes are protocol-independent and apply to both SIP and H.323 calls. The same internal end reason code is recorded in the CDR regardless of the signaling protocol used. However, the corresponding protocol-level codes differ — a SIP call with end reason 2 (User Busy) will show 486 Busy Here in the SIP layer, while an H.323 call with the same end reason will show Q.850 cause code 17. The server end reason provides a unified view across both protocols.
Analyzing VOS3000 server end reasons across millions of CDRs requires both technical expertise and the right analytical approach. Our VOS3000 specialists can help you build CDR analysis workflows, identify the root causes of call failures, and optimize your routing and billing configurations to improve ASR and reduce revenue leakage.
Contact us on WhatsApp: +8801911119966
Whether you need help interpreting end reason distributions, troubleshooting high failure rates, or building automated CDR monitoring dashboards, our team is here to assist. Reach out today at +8801911119966 and take control of your VOS3000 call quality.
For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:
📱 WhatsApp: +8801911119966
🌐 Website: www.vos3000.com
🌐 Blog: multahost.com/blog
📥 Downloads: VOS3000 Downloads
VOS3000 replace failed reason overrides SIP and H.323 error responses with custom codes. Replace 503 with 486 to prevent failover… Read More
VOS3000 call forward signal recognition with SS_RECOGNIZE_CALL_FORWARD_SIGNAL. Detect 181 Call Is Being Forwarded and 302 Moved Temporarily for billing. Read More
VOS3000 remote ring back mode configures ringback tone delivery with Passthrough, 183+SDP, or 180+SDP modes. Control early media and ringback… Read More
This website uses cookies.