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 ContentsVOS3000 Call End Reasons: Complete Error Code Reference Guide Understanding VOS3000 Call End Reasons Where to Find VOS3000 Call End Reasons Complete VOS3000 Server-Side Termination Reasons Account-Related Termination Reasons Routing-Related Termination Reasons (VOS3000 Call End Reasons) Timeout-Related Termination Reasons Number Restriction Termination Reasons Forwarding-Related Termination Reasons Protocol and System Termination Reasons SIP Response Code to VOS3000 Mapping SIP 4xx Client Error Mapping SIP 5xx Server Error Mapping H.323 Cause Codes Complete Reference H.323 Q.931 Cause Codes Table (VOS3000 Call End Reasons) CDR Analysis and Diagnosis Flow VOS3000 Call End Reasons Diagnosis Workflow VOS3000 Support Services Related Resources (VOS3000 Call End Reasons) Frequently Asked QuestionsWhat is the difference between “Response Timeout” and “Connection Timeout”?Why do I see different error codes for similar failures?How can I filter CDR to see only failed calls?What causes “Codec Mismatch” errors?How do I interpret H.323 cause codes in CDR? Get Expert VOS3000 Troubleshooting Support Need Professional VOS3000 Setup Support?

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 AvailableRecent CDRData Query → Recent CDRLatest calls with termination reason columnCDR QueryData Query → CDRHistorical CDR with advanced filteringCall AnalysisOperation Management → Business AnalysisDetailed SIP/H.323 signaling traceDebug TraceSystem → Debug traceReal-time SIP message captureDatabase DirectMySQL vos3000_cdr tableRaw 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 PageAccount LockedThe account is currently locked/disabledAdmin locked account, security triggerAccount Management → Change Status to Active244Account DisabledAccount status is disabledAccount deactivated by adminEnable account in account management244Account ExpiredAccount validity period has endedExpiry date passedExtend expiry date (set to 2099-12-31)244Insufficient BalanceAccount balance too low for callBalance < rate for destinationAdd credit to account244No Matching AccountNo account found to bill the callCaller ID not mapped to accountCreate account or fix caller ID mapping245Account Not OnlineCalled account not registeredPhone endpoint offlineCheck phone registration status245

Routing-Related Termination Reasons (VOS3000 Call End Reasons)

Termination Reason Description Typical Cause Solution PageNoAvailableRouterNo routing gateway availableNo gateway configured for destinationAdd routing gateway with correct prefix245Not FoundDestination number not foundPrefix mismatch in gatewayCheck gateway prefix configuration245No Matching RateNo rate found for destinationRate table missing prefixAdd rate entry for destination prefix245The Called Not OnlineCalled device not reachableGateway offline or no capacityCheck gateway status and capacity245Connection Limit ExceededMaximum concurrent calls reachedLine limit reached on account/gatewayIncrease line limit or add capacity246UnregisteredEndpoint not registeredRegistration expired or failedVerify device registration settings246Rate Table Not FoundNo rate table assignedAccount missing rate tableAssign rate table to account246

Timeout-Related Termination Reasons

Termination Reason Description Related Parameter Solution PageResponse TimeoutNo answer from called partySS_TIMEOUT_PHONE_HANGUPIncrease alerting timeout, check endpoint246Connection TimeoutNo SIP response after retriesSS_SIP_SEND_RETRY, SS_SIP_RESEND_INTERVALCheck network, firewall, gateway status246Proceeding TimeoutNo 100 Trying progressGateway proceeding timeoutCheck gateway connectivity247Session TimeoutSession timer refresh failedSS_SIP_SESSION_TTLCheck session timer config, NAT keep-alive247Connection Establishment TimeoutCall setup incompleteMapping gateway timeoutCheck gateway response time247Alerting TimeoutRing timeout exceededGateway alerting timerIncrease ring timeout in gateway config247

Number Restriction Termination Reasons

Termination Reason Description Trigger Solution PageCaller’s Number RestrictedCaller ID length exceeds limitSS_CALLERALLOWLENGTH exceededAdjust caller length parameter247Called Number RestrictedCallee number too longNumber length limitAdjust called number length settings247Caller’s Number Prefix RestrictedCaller prefix not allowedGateway prefix filterUpdate allowed prefixes in gateway248Called Number Prefix RestrictedDestination prefix blockedGateway prefix restrictionCheck gateway prefix settings248Call RestrictionCall blocked by policyAccount authorization settingsUpdate account call authorization248

Forwarding-Related Termination Reasons

Termination Reason Description Configuration PageNo-Answer Forwarding by CallerCaller has no-answer forwardingPhone Management → Call Forwarding248No-Answer Forwarding by CalledCalled has no-answer forwardingCalled phone forwarding settings248Timed ForwardingTime-based forwarding activeTime period forwarding config248On-Busy ForwardingCalled busy, forwardedBusy forwarding config248Call Forwarding by CalledUnconditional forwardingForwarding unconditional setting249Forwarding LoopInfinite forwarding loopForwarding chain creates loop249Do-Not-Disturb from CalledCalled has DND enabledDND setting on phone249

Protocol and System Termination Reasons

Termination Reason Description Notes PageProtocol LimitServer cannot process protocolCheck protocol compatibility249BusyCalled number is busyNormal termination249Forcible Hang-UpServer terminated sessionAdmin action or system limit249Hang-Up by CallerCaller ended normallyNormal termination249Hang-Up by CalledCalled party ended callNormal termination249Session Closed by CalledTCP closed without BYENetwork/endpoint issue249Session Closed by CallerCaller TCP closedCheck caller network249Codec MismatchNo common codecEnable transcoding249

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 Cause400Bad RequestProtocol ErrorMalformed SIP message401UnauthorizedAuth FailedInvalid credentials403ForbiddenAccount Locked / IP BlockedAccess denied by policy404Not FoundNot FoundUser/destination unknown405Method Not AllowedProtocol LimitSIP method rejected406Not AcceptableCodec MismatchSDP negotiation failed407Proxy Auth RequiredAuth FailedProxy authentication needed408Request TimeoutResponse TimeoutNo SIP response received415Unsupported MediaCodec MismatchMedia format rejected422Session Interval Too SmallSession Timer ErrorSession timer too short480Temporarily UnavailableUnregistered / Not OnlineEndpoint unavailable484Address IncompleteNumber RestrictedIncomplete number486Busy HereBusyUser busy487Request TerminatedCancelledCall cancelled488Not Acceptable HereCodec MismatchSDP negotiation failed

SIP 5xx Server Error Mapping

SIP Code SIP Name VOS3000 Mapping Typical Cause500Server Internal ErrorProtocol ErrorRemote server error502Bad GatewayGateway ErrorInvalid response from upstream503Service UnavailableNoAvailableRouterServer overloaded/maintenance504Server Time-outConnection TimeoutNo 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 Action1Unallocated NumberNumber not assigned to any destinationRecord as Not Found2No Route to Transit NetNo route through transit networkRecord as NoAvailableRouter3No Route to DestinationNo route to called numberRecord as NoAvailableRouter6Channel UnacceptableChannel not acceptable for callRecord as Connection Limit7Call AwardedCall awarded, delivered to endpointNormal call handling8PreemptionCall preempted by higher priorityRecord as Forcible Hang-Up16Normal Call ClearingCall cleared normallyRecord as Hang-Up by Caller/Called17User BusyUser is busyRecord as Busy18No User RespondingNo response from userRecord as Response Timeout19No Answer from UserUser alerted but no answerRecord as Response Timeout20Subscriber AbsentSubscriber not availableRecord as Unregistered21Call RejectedCall was rejectedRecord as call rejection22Number ChangedNumber has been changedRecord as Not Found26Non-Selected User ClearingUser not selected for callNormal termination27Destination Out of OrderDestination cannot be reachedRecord as Gateway Error28Invalid Number FormatNumber format invalidRecord as Number Restricted29Facility RejectedFacility rejectedRecord as Protocol Error30Response to STATUS ENQUIRYResponse to status inquiryStatus response31Normal, UnspecifiedNormal event, no specific causeNormal termination34No Circuit AvailableNo channel availableRecord as Connection Limit38Network Out of OrderNetwork not functioningRecord as Gateway Error41Temporary FailureTemporary network problemRecord as temporary error42Switch CongestionNetwork congestionRecord as Connection Limit44Requested Circuit Not AvailableRequested circuit unavailableRecord as Connection Limit47Resource UnavailableInsufficient resourcesRecord as Connection Limit49QoS Not AvailableRequested QoS not availableRecord as Protocol Error50Requested Facility Not SubscribedFacility not subscribedRecord as Call Restriction52Outgoing Call BarredOutgoing calls barredRecord as Call Restriction54Incoming Call BarredIncoming calls barredRecord as Call Restriction57Bearer Capability Not AuthorizedCapability not authorizedRecord as Account Locked58Bearer Capability Not AvailableCapability not availableRecord as Codec Mismatch63Service Not AvailableService not availableRecord as NoAvailableRouter65Bearer Capability Not ImplementedCapability not implementedRecord as Codec Mismatch69Requested Facility Not ImplementedFacility not implementedRecord as Protocol Limit70Only Restricted Digital BearerOnly restricted digital availableRecord as Codec Mismatch79Service Not ImplementedService not implementedRecord as Protocol Limit81Invalid Call ReferenceCall reference invalidRecord as Protocol Error88Incompatible DestinationDestination incompatibleRecord as Codec Mismatch95Invalid MessageMessage invalidRecord as Protocol Error96Mandatory IE MissingMandatory element missingRecord as Protocol Error97Message Not ImplementedMessage type not implementedRecord as Protocol Limit98IE Not ImplementedInformation element not implementedRecord as Protocol Limit99Invalid IE ContentsInformation element invalidRecord as Protocol Error100Invalid Message for StateMessage invalid for call stateRecord as Protocol Error101Recovery on Timer ExpiryTimer expiredRecord as Response Timeout102Protocol ErrorProtocol error unspecifiedRecord as Protocol Error111Protocol Error, UnspecifiedUnspecified protocol errorRecord 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 ScopeCDR AnalysisDeep dive into call failure patternsError patterns, ASR/ACD analysisConfiguration AuditReview VOS3000 settingsParameters, gateway, routingTechnical Support24/7 remote assistanceTroubleshooting, optimization

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

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