VOS3000 Call End Reasons: Complete Error Code Reference Guide
VOS3000 call end reasons provide the definitive diagnostic information for understanding why VoIP calls fail, disconnect, or terminate abnormally. Every call processed through VOS3000 generates detailed termination data in the CDR (Call Detail Record) that identifies the exact reason for call completion. This comprehensive reference guide documents all server-side termination reasons, client error codes, SIP response mappings, and H.323 cause codes based on the official VOS3000 2.1.9.07 manual.
📞 Need help diagnosing VOS3000 call failures? WhatsApp: +8801911119966
When a call terminates in VOS3000, the system records the termination reason in multiple CDR fields. Understanding these reasons is essential for maintaining call quality, optimizing routes, and troubleshooting recurring issues. The termination reason indicates whether the call ended normally, was rejected, timed out, or failed due to system configuration.
Server-side termination reasons are generated by VOS3000 when the softswitch itself terminates or rejects the call. These reasons provide the most detailed diagnostic information as they indicate the exact condition that prevented call completion. (VOS3000 Call End Reasons)
🔴 Account-Related Termination Reasons
🚨 Termination Reason
📋 Description
🔍 Typical Cause
✅ Solution
📖 Page
Account Locked
The account is currently locked/disabled
Admin locked account, security trigger
Account Management → Change Status to Active
244
Account Disabled
Account status is disabled
Account deactivated by admin
Enable account in account management
244
Account Expired
Account validity period has ended
Expiry date passed
Extend expiry date (set to 2099-12-31)
244
Insufficient Balance
Account balance too low for call
Balance < rate for destination
Add credit to account
244
No Matching Account
No account found to bill the call
Caller ID not mapped to account
Create account or fix caller ID mapping
245
Account Not Online
Called account not registered
Phone endpoint offline
Check phone registration status
245
🔴 Routing-Related Termination Reasons (VOS3000 Call End Reasons)
When SIP responses are received from endpoints or gateways, VOS3000 maps these standard SIP codes to internal termination reasons. Understanding this mapping helps correlate SIP traces with CDR data. (VOS3000 Call End Reasons)
For H.323 protocol calls, VOS3000 uses ITU-T Q.931 cause codes. These standard cause codes provide detailed information about call failures in traditional telephony and H.323-based VoIP systems.
📊 H.323 Q.931 Cause Codes Table (VOS3000 Call End Reasons)
🔢 Code
📋 Name
📝 Meaning
🔄 VOS3000 Action
1
Unallocated Number
Number not assigned to any destination
Record as Not Found
2
No Route to Transit Net
No route through transit network
Record as NoAvailableRouter
3
No Route to Destination
No route to called number
Record as NoAvailableRouter
6
Channel Unacceptable
Channel not acceptable for call
Record as Connection Limit
7
Call Awarded
Call awarded, delivered to endpoint
Normal call handling
8
Preemption
Call preempted by higher priority
Record as Forcible Hang-Up
16
Normal Call Clearing
Call cleared normally
Record as Hang-Up by Caller/Called
17
User Busy
User is busy
Record as Busy
18
No User Responding
No response from user
Record as Response Timeout
19
No Answer from User
User alerted but no answer
Record as Response Timeout
20
Subscriber Absent
Subscriber not available
Record as Unregistered
21
Call Rejected
Call was rejected
Record as call rejection
22
Number Changed
Number has been changed
Record as Not Found
26
Non-Selected User Clearing
User not selected for call
Normal termination
27
Destination Out of Order
Destination cannot be reached
Record as Gateway Error
28
Invalid Number Format
Number format invalid
Record as Number Restricted
29
Facility Rejected
Facility rejected
Record as Protocol Error
30
Response to STATUS ENQUIRY
Response to status inquiry
Status response
31
Normal, Unspecified
Normal event, no specific cause
Normal termination
34
No Circuit Available
No channel available
Record as Connection Limit
38
Network Out of Order
Network not functioning
Record as Gateway Error
41
Temporary Failure
Temporary network problem
Record as temporary error
42
Switch Congestion
Network congestion
Record as Connection Limit
44
Requested Circuit Not Available
Requested circuit unavailable
Record as Connection Limit
47
Resource Unavailable
Insufficient resources
Record as Connection Limit
49
QoS Not Available
Requested QoS not available
Record as Protocol Error
50
Requested Facility Not Subscribed
Facility not subscribed
Record as Call Restriction
52
Outgoing Call Barred
Outgoing calls barred
Record as Call Restriction
54
Incoming Call Barred
Incoming calls barred
Record as Call Restriction
57
Bearer Capability Not Authorized
Capability not authorized
Record as Account Locked
58
Bearer Capability Not Available
Capability not available
Record as Codec Mismatch
63
Service Not Available
Service not available
Record as NoAvailableRouter
65
Bearer Capability Not Implemented
Capability not implemented
Record as Codec Mismatch
69
Requested Facility Not Implemented
Facility not implemented
Record as Protocol Limit
70
Only Restricted Digital Bearer
Only restricted digital available
Record as Codec Mismatch
79
Service Not Implemented
Service not implemented
Record as Protocol Limit
81
Invalid Call Reference
Call reference invalid
Record as Protocol Error
88
Incompatible Destination
Destination incompatible
Record as Codec Mismatch
95
Invalid Message
Message invalid
Record as Protocol Error
96
Mandatory IE Missing
Mandatory element missing
Record as Protocol Error
97
Message Not Implemented
Message type not implemented
Record as Protocol Limit
98
IE Not Implemented
Information element not implemented
Record as Protocol Limit
99
Invalid IE Contents
Information element invalid
Record as Protocol Error
100
Invalid Message for State
Message invalid for call state
Record as Protocol Error
101
Recovery on Timer Expiry
Timer expired
Record as Response Timeout
102
Protocol Error
Protocol error unspecified
Record as Protocol Error
111
Protocol Error, Unspecified
Unspecified protocol error
Record as Protocol Error
🔧 CDR Analysis and Diagnosis Flow
🔍 VOS3000 Call End Reasons Diagnosis Workflow
STEP 1: IDENTIFY THE PROBLEM
├── Open CDR Query (Data Query → CDR)
├── Filter by time period, account, or gateway
├── Look at "Termination Reason" column
└── Note patterns: same error repeatedly?
STEP 2: CLASSIFY ERROR TYPE
├── Account Issue?
│ ├── Account Locked → Account Management
│ ├── Insufficient Balance → Balance Management
│ └── Account Expired → Extend Expiry Date
│
├── Routing Issue?
│ ├── NoAvailableRouter → Add Gateway
│ ├── Not Found → Check Prefix Config
│ └── No Matching Rate → Add Rate Entry
│
├── Network Issue?
│ ├── Connection Timeout → Firewall/Connectivity
│ ├── Response Timeout → Gateway Response
│ └── Session Timeout → NAT/Session Timer
│
└── Protocol Issue?
├── Codec Mismatch → Enable Transcoding
├── Protocol Limit → Check Compatibility
└── Protocol Error → Debug Trace Analysis
STEP 3: ANALYZE CALL TRACE
├── Find problematic call in CDR
├── Right-click → Call Analysis
├── Review SIP/H.323 message sequence
└── Identify exact point of failure
STEP 4: IMPLEMENT SOLUTION
├── Apply fix based on diagnosis
├── Document changes made
├── Test with sample calls
└── Verify in CDR that issue resolved
STEP 5: MONITOR
├── Check ASR improvement
├── Monitor for recurrence
└── Adjust configuration as needed
💰 VOS3000 Support Services
Need professional assistance with VOS3000 call failure diagnosis? Our team provides comprehensive VOS3000 support including CDR analysis, error code troubleshooting, and system optimization.
What is the difference between “Response Timeout” and “Connection Timeout”?
Response Timeout occurs when the called party does not answer within the configured alerting time (phone rings but nobody picks up). Connection Timeout occurs when VOS3000 sends SIP INVITE but receives no SIP response at all after multiple retries, typically indicating network connectivity issues, firewall blocks, or the gateway being offline.
Why do I see different error codes for similar failures?
VOS3000 records different termination reasons based on the exact point of failure and the protocol used. A SIP 404 Not Found from a gateway produces “Not Found” while a routing table miss produces “NoAvailableRouter”. The distinction helps pinpoint whether the issue is with routing configuration or the remote endpoint’s response.
How can I filter CDR to see only failed calls?
In CDR Query, you can filter by Session Time = 0 to see calls that never connected, or create custom queries against the database to filter by specific termination reasons. The vos3000_cdr MySQL table contains all termination information for advanced analysis.
What causes “Codec Mismatch” errors?
Codec Mismatch occurs when the caller and callee have no common audio codec. This typically happens when one side only supports G.711 (alaw/ulaw) and the other only supports G.729 without transcoding enabled. Enable transcoding in VOS3000 or configure compatible codecs on both endpoints.
How do I interpret H.323 cause codes in CDR?
H.323 cause codes follow ITU-T Q.931 standard. Common codes include 16 (normal call clearing), 17 (user busy), 18 (no response), 21 (call rejected), and 34 (no circuit available). Use the complete cause code table in this guide to interpret specific values in your CDR.
📞 Get Expert VOS3000 Troubleshooting Support
Need help diagnosing VOS3000 call failures or understanding error codes? Our VOS3000 experts provide comprehensive support for CDR analysis, error code interpretation, and system optimization.
Some of vos3000 users ask me how we will stop one specific gateway to send call vendor side when we do not have balances! Because when prepaid amount finish we do not want to move our calls hitting that vendor & sometime it kills call as well. VOS3000 have solution for that as well, please note for this you must have to maintain proper Clearing Account/Vendor Account/Provider Account – if you do not have this properly set then your call will fail with error code “NoAvailableRouter” – this error can come for many reason in VOS3000 but one of the reason is this. You can set this basically from “System Parameter” options in VOS3000.
It will help to not kill clients valuable traffic which coming at your server.
Please see the below images to set that option:
You have yo make it “On” from here, so vos3000 will check first if you have balances in vendor side or not, if no balances then it will not send calls in that vendor or routing gateway. Please remember: VOS3000 can check only your clearing account balance – so you must have to set your clearing gateway properly in VOS3000 Switch.
Please knock me in whatsapp for all kind helps/queries for vos3000: +8801911119966
