VOS3000 SIP timeouts and call duration limits
Calls that fail after a few seconds, drop at the same minute every time, or never end: most of the time a timer is the cause.
Updated · By the VOS3000 Web team
Quick answer: VOS3000 gives a carrier 10 seconds to answer an INVITE and 120 seconds of ringing by default. Calls from SIP devices without session timer support are ended after 7200 seconds (2 hours), and calls with no audio for 2 minutes are hung up. All of these are system parameters, and most can be changed per routing gateway.
- INVITE timeout
- 10 seconds
- Ringing timeout
- 120 seconds
- No session timer
- Call ended after 7200 seconds
- No audio
- Hung up after 2 minutes
All values below are softswitch parameters in the VOS3000 desktop client, under Operation management → Softswitch management → Additional settings → System parameter. Most are only defaults: a routing gateway can override them in Additional settings → Protocol → SIP, where Default means use the system value. Defaults are from the VOS3000 2.1.9.07 manual.
Call setup timeouts
| Parameter | Default | What it limits |
|---|---|---|
| SS_SIP_TIMEOUT_INVITE | 10 s | Time for the carrier to respond to INVITE. |
| SS_SIP_TIMEOUT_TRYING | 20 s | Time to wait after 100 Trying. |
| SS_SIP_TIMEOUT_SESSION_PROGRESS | 20 s | Time to wait after 183 Session Progress without SDP. |
| SS_SIP_TIMEOUT_SESSION_PROGRESS_SDP | 120 s | Time to wait after 183 Session Progress with SDP. |
| SS_SIP_TIMEOUT_RINGING | 120 s | How long a call may ring. |
| SS_SIP_RESEND_INTERVAL | 0.5,1,2,4,4,4,4,4,4,4 | When to resend a SIP message that got no reply; after the last try the call fails and the next gateway is tried. |
If a slow carrier needs more time before it answers, raise the INVITE or progress timeout on that routing gateway only, not system-wide. When a timeout fails over to the next gateway, see routing order.
Session timer and the 2-hour limit
A session timer checks that a connected call still exists, so a lost BYE does not leave a call (and its bill) running for hours.
- SS_SIP_SESSION_TTL (600 s): for SIP devices that support session timers, VOS3000 checks the call within this interval and hangs up if it gets no confirmation.
- SS_SIP_SESSION_UPDATE_SEGMENT (2, range 2 to 10): how often re-INVITE or UPDATE is sent within that interval.
- SS_SIP_NO_TIMER_REINVITE_INTERVAL (7200 s): for SIP callers that do not support session timers, VOS3000 ends the call when this time is up.
That last one is why calls from some customers end at exactly 2 hours. If long calls are normal for that customer, raise the value or ask them to enable session timers on their device.
Calls with no audio
SS_MEDIA_CHECK_TIMEOUT (2 minutes) hangs up a call when VOS3000 receives no media for that long. Gateways also have RTP interrupt detection (None, Server to remote, Remote to server or Bidirection) to end calls whose audio stops. These calls end with reasons such as NoAudioDataTimeout (-55). The cause is almost always the audio path, so start with one-way audio and media proxy.
Maximum call duration
SS_MAX_CALL_DURATION (none by default) ends any call after a set number of seconds. Each gateway has its own Conversation limitation. A limit of a few hours protects you from calls that never end because of a fault or fraud.
Phones and registrations
- SS_TIMEOUT_PHONE_NO_ANSWER (120 s): hang up a call to a phone that does not answer.
- SS_TIMEOUT_CALL_FORWARD_NO_ANSWER (20 s): forward on no answer after this time.
- SS_ENDPOINT_EXPIRE and SS_ENDPOINT_NAT_EXPIRE: registration expiry for phones, with a shorter one for phones behind NAT so the NAT mapping stays open.
- SS_SIP_NAT_KEEP_ALIVE_MESSAGE (HELLO) and SS_SIP_NAT_KEEP_ALIVE_PERIOD (30 s): small UDP packets VOS3000 sends to devices behind NAT that do not re-register often enough. Leave the message empty to send none.
Questions about this topic
Why do VOS3000 calls end at exactly 2 hours?
The caller's SIP device does not support session timers, so VOS3000 ends the call after SS_SIP_NO_TIMER_REINVITE_INTERVAL, 7200 seconds by default. Raise the value, or enable session timers on the device.
Why do VOS3000 calls drop after about 2 minutes?
Usually no audio reached VOS3000 for 2 minutes (SS_MEDIA_CHECK_TIMEOUT), often a NAT or firewall problem. Check the end reason in the CDR.
How long does VOS3000 let a call ring?
120 seconds by default (SS_SIP_TIMEOUT_RINGING), and each routing gateway can override it.
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
One-way or no audio
Why audio fails on some calls and how to fix it with media proxy and codecs.
Termination reason lookup
Type a code like -55 or 486, or a name, and see what it means.
Media proxy
What On, Off, Auto and Must on do, how Auto decides, and what it costs in bandwidth.
System parameters
Where the SERVER_ and SS_ parameters are, and the billing, CDR and call ones worth knowing.