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
Table of Contents
🔍 Understanding VOS3000 Call End Reasons
Reference: VOS3000 2.1.9.07 Manual, Section 4.5 (Pages 244-249)
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.
📊 Where to Find VOS3000 Call End Reasons
| 📍 Location | 🧭 Navigation Path | 📋 Information Available |
|---|---|---|
| Recent CDR | Data Query → Recent CDR | Latest calls with termination reason column |
| CDR Query | Data Query → CDR | Historical CDR with advanced filtering |
| Call Analysis | Operation Management → Business Analysis | Detailed SIP/H.323 signaling trace |
| Debug Trace | System → Debug trace | Real-time SIP message capture |
| Database Direct | MySQL vos3000_cdr table | Raw CDR data for custom analysis |
📋 Complete VOS3000 Server-Side Termination Reasons
Reference: VOS3000 2.1.9.07 Manual, Section 4.5 (Pages 244-249)
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)
| 🚨 Termination Reason | 📋 Description | 🔍 Typical Cause | ✅ Solution | 📖 Page |
|---|---|---|---|---|
| NoAvailableRouter | No routing gateway available | No gateway configured for destination | Add routing gateway with correct prefix | 245 |
| Not Found | Destination number not found | Prefix mismatch in gateway | Check gateway prefix configuration | 245 |
| No Matching Rate | No rate found for destination | Rate table missing prefix | Add rate entry for destination prefix | 245 |
| The Called Not Online | Called device not reachable | Gateway offline or no capacity | Check gateway status and capacity | 245 |
| Connection Limit Exceeded | Maximum concurrent calls reached | Line limit reached on account/gateway | Increase line limit or add capacity | 246 |
| Unregistered | Endpoint not registered | Registration expired or failed | Verify device registration settings | 246 |
| Rate Table Not Found | No rate table assigned | Account missing rate table | Assign rate table to account | 246 |
🔴 Timeout-Related Termination Reasons
| 🚨 Termination Reason | 📋 Description | ⚙️ Related Parameter | ✅ Solution | 📖 Page |
|---|---|---|---|---|
| Response Timeout | No answer from called party | SS_TIMEOUT_PHONE_HANGUP | Increase alerting timeout, check endpoint | 246 |
| Connection Timeout | No SIP response after retries | SS_SIP_SEND_RETRY, SS_SIP_RESEND_INTERVAL | Check network, firewall, gateway status | 246 |
| Proceeding Timeout | No 100 Trying progress | Gateway proceeding timeout | Check gateway connectivity | 247 |
| Session Timeout | Session timer refresh failed | SS_SIP_SESSION_TTL | Check session timer config, NAT keep-alive | 247 |
| Connection Establishment Timeout | Call setup incomplete | Mapping gateway timeout | Check gateway response time | 247 |
| Alerting Timeout | Ring timeout exceeded | Gateway alerting timer | Increase ring timeout in gateway config | 247 |
🔴 Number Restriction Termination Reasons
| 🚨 Termination Reason | 📋 Description | 🔍 Trigger | ✅ Solution | 📖 Page |
|---|---|---|---|---|
| Caller’s Number Restricted | Caller ID length exceeds limit | SS_CALLERALLOWLENGTH exceeded | Adjust caller length parameter | 247 |
| Called Number Restricted | Callee number too long | Number length limit | Adjust called number length settings | 247 |
| Caller’s Number Prefix Restricted | Caller prefix not allowed | Gateway prefix filter | Update allowed prefixes in gateway | 248 |
| Called Number Prefix Restricted | Destination prefix blocked | Gateway prefix restriction | Check gateway prefix settings | 248 |
| Call Restriction | Call blocked by policy | Account authorization settings | Update account call authorization | 248 |
🔴 Forwarding-Related Termination Reasons
| 🚨 Termination Reason | 📋 Description | ⚙️ Configuration | 📖 Page |
|---|---|---|---|
| No-Answer Forwarding by Caller | Caller has no-answer forwarding | Phone Management → Call Forwarding | 248 |
| No-Answer Forwarding by Called | Called has no-answer forwarding | Called phone forwarding settings | 248 |
| Timed Forwarding | Time-based forwarding active | Time period forwarding config | 248 |
| On-Busy Forwarding | Called busy, forwarded | Busy forwarding config | 248 |
| Call Forwarding by Called | Unconditional forwarding | Forwarding unconditional setting | 249 |
| Forwarding Loop | Infinite forwarding loop | Forwarding chain creates loop | 249 |
| Do-Not-Disturb from Called | Called has DND enabled | DND setting on phone | 249 |
🔴 Protocol and System Termination Reasons
| 🚨 Termination Reason | 📋 Description | 💡 Notes | 📖 Page |
|---|---|---|---|
| Protocol Limit | Server cannot process protocol | Check protocol compatibility | 249 |
| Busy | Called number is busy | Normal termination | 249 |
| Forcible Hang-Up | Server terminated session | Admin action or system limit | 249 |
| Hang-Up by Caller | Caller ended normally | Normal termination | 249 |
| Hang-Up by Called | Called party ended call | Normal termination | 249 |
| Session Closed by Called | TCP closed without BYE | Network/endpoint issue | 249 |
| Session Closed by Caller | Caller TCP closed | Check caller network | 249 |
| Codec Mismatch | No common codec | Enable transcoding | 249 |
📞 SIP Response Code to VOS3000 Mapping
Reference: VOS3000 2.1.9.07 Manual, Section 4.5.2 (Page 247-248)
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)
📊 SIP 4xx Client Error Mapping
| 📞 SIP Code | 📋 SIP Name | 🔄 VOS3000 Mapping | ⚡ Typical Cause |
|---|---|---|---|
| 400 | Bad Request | Protocol Error | Malformed SIP message |
| 401 | Unauthorized | Auth Failed | Invalid credentials |
| 403 | Forbidden | Account Locked / IP Blocked | Access denied by policy |
| 404 | Not Found | Not Found | User/destination unknown |
| 405 | Method Not Allowed | Protocol Limit | SIP method rejected |
| 406 | Not Acceptable | Codec Mismatch | SDP negotiation failed |
| 407 | Proxy Auth Required | Auth Failed | Proxy authentication needed |
| 408 | Request Timeout | Response Timeout | No SIP response received |
| 415 | Unsupported Media | Codec Mismatch | Media format rejected |
| 422 | Session Interval Too Small | Session Timer Error | Session timer too short |
| 480 | Temporarily Unavailable | Unregistered / Not Online | Endpoint unavailable |
| 484 | Address Incomplete | Number Restricted | Incomplete number |
| 486 | Busy Here | Busy | User busy |
| 487 | Request Terminated | Cancelled | Call cancelled |
| 488 | Not Acceptable Here | Codec Mismatch | SDP negotiation failed |
📊 SIP 5xx Server Error Mapping
| 📞 SIP Code | 📋 SIP Name | 🔄 VOS3000 Mapping | ⚡ Typical Cause |
|---|---|---|---|
| 500 | Server Internal Error | Protocol Error | Remote server error |
| 502 | Bad Gateway | Gateway Error | Invalid response from upstream |
| 503 | Service Unavailable | NoAvailableRouter | Server overloaded/maintenance |
| 504 | Server Time-out | Connection Timeout | No response from upstream |
📞 H.323 Cause Codes Complete Reference
Reference: VOS3000 2.1.9.07 Manual, Section 4.5.3 (Page 248-249)
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.
| 📦 Service | 📝 Description | 💼 Scope |
|---|---|---|
| CDR Analysis | Deep dive into call failure patterns | Error patterns, ASR/ACD analysis |
| Configuration Audit | Review VOS3000 settings | Parameters, gateway, routing |
| Technical Support | 24/7 remote assistance | Troubleshooting, optimization |
📞 Contact us for VOS3000: WhatsApp: +8801911119966
🔗 Related Resources (VOS3000 Call End Reasons)
- 📖 VOS3000 SIP Call Flow Complete Guide
- 📖 VOS3000 ASR ACD Analysis
- 📖 VOS3000 Gateway Analysis Reports
- 📖 VOS3000 Account Management
- 📥 VOS3000 Downloads – Manual and Software
❓ Frequently Asked Questions
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.
📱 WhatsApp: +8801911119966
Contact us today for professional VOS3000 installation, configuration, and technical support services!
📞 Need Professional VOS3000 Setup Support?
For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:
📱 WhatsApp: +8801911119966
🌐 Website: www.vos3000.com
🌐 Blog: multahost.com/blog
📥 Downloads: VOS3000 Downloads
 | | |
