VOS3000 calls failing: what the error means
Every failed call has a reason in the CDR. Read it first: it tells you whether VOS3000 refused the call or the carrier did.
Updated · By the VOS3000 Web team
Quick answer: A failed VOS3000 call ends with a reason in the CDR. Negative codes such as -69 NoAvailableRouter or -6 CallAuthenticationFailure come from VOS3000 itself; codes from 300 to 606 such as 403, 404, 408 and 503 are SIP responses from the carrier. Find which side refused the call first, then fix that side.
- -69
- No routing gateway can take the number
- 403
- The carrier refused the call
- 408
- No answer in time
- 503
- The carrier is unavailable or out of capacity
Step 1: read the end reason
Open the call in Recent CDR and look at the end reason and the routing gateway. Negative codes are VOS3000's own reasons: the switch refused or ended the call. Codes from 300 to 606 are SIP responses, usually from the carrier. Codes up to 128 are Q.850 causes, often passed on by a carrier. Look up any code in the termination reason lookup.
VOS3000's own reasons
| Reason | Meaning | Check |
|---|---|---|
| NoAvailableRouter (-69) | No routing gateway could take the number. | Routing gateway prefixes, locks, line limits, rewrite rules. |
| CallAuthenticationFailure (-6) | The caller was not recognised. | The customer's IP on the mapping gateway, or the phone's password. |
| InsufficientBalance (-2) | The account's balance is too low. | Balance and overdraft limit. |
| ConnectionTimeout (-41) | No reply to SIP messages after all retries. | The carrier's IP and port, firewalls on both sides. |
| CallSetupTimeout (-27) | The call was not set up in time. | The mapping gateway's process timeout, a slow carrier. |
| NumberLengthRestricted (-35) | The number length is not allowed. | Number limit on the gateways. |
SIP responses from the carrier
| Code | Usual meaning | What to do |
|---|---|---|
| 403 Forbidden | The carrier refused the call: your IP is not allowed, no credit, the destination or caller ID is blocked. | Ask the carrier; check the caller ID and number format you send. |
| 404 Not Found | The number does not exist, or its format is wrong. | Check the callee number as sent out, and your rewrite rules. |
| 408 Request Timeout | No final answer in time. | The carrier's capacity, or your SIP timeouts. |
| 480 Temporarily Unavailable | The called user cannot be reached now. | Often normal; if it is on every call, ask the carrier. |
| 503 Service Unavailable | The carrier is overloaded, out of capacity or has no route. | Fail over to another route; ask the carrier. |
Step 2: make failover work for you
When a routing gateway fails a call, VOS3000 tries the next one in the list; see routing order. On a routing gateway's SIP settings:
- Stop switching response code: codes that should not fail over, for example 404, because the number is wrong on every route.
- Retry-After: if the carrier sends a Retry-After header, VOS3000 disables the gateway for that time; it then shows in Online routing gateway.
Step 3: control what your customer sees
On a mapping gateway, Replace failed reason sets which error is sent back to the customer for each failure. Audio prompts for can't connect plays the failure reason to the caller instead.
Still unclear?
Trace the call and read the full SIP exchange: see debug trace and SIP capture.
Questions about this topic
What does 503 Service Unavailable mean in VOS3000?
The carrier, or the next server, could not take the call: it was overloaded, out of capacity or had no route. Try another route and ask the carrier.
What does NoAvailableRouter (-69) mean?
VOS3000 found no routing gateway that could take the number: no prefix match, or every matching gateway was locked, full or refused it.
How do I send a different error code to my customer?
Use Replace failed reason on the mapping gateway to choose which error is sent back for each failure.
Run VOS3000 without the server work
Pick a VOS3000 server hosted by us, or have us install VOS3000 on your own server. VOS3000 Web and the Android app come with it.
Keep reading
Termination reason lookup
Type a code like -55 or 486, or a name, and see what it means.
Routing order and LCR
How VOS3000 sorts routing gateways: prefix, priority, ASR, lowest rate, and when it fails over.
Debug trace and SIP capture
Trace call signalling in the desktop client, read Call analysis, or capture SIP with tcpdump and sngrep.
SIP timeouts and call limits
INVITE and ringing timeouts, session timer, the 2-hour limit, no-media hang up and max call duration.