[VoiceOps] SIP calls that aren't torn down

Scott Berkman scott at sberkman.net
Tue Jun 7 16:42:30 EDT 2011

BroadSoft normally uses "Session Audits" (defaults to 5 minutes) which is
really a SIP RE-INVITE to make sure the other end is still there.  If no
response is received, the call is torn down.  "Hung" calls can still happen
due to software bugs, and the vendor should provide a low-level tool to
manually kill the calls.

The reason BroadSoft doesn't do RTP detection is because it (really the AS
and/or NS) are almost never involved in the media stream unless the call is
to a MS for say IVR, MOH, etc or a conferencing server.


-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Jon Radel
Sent: Tuesday, June 07, 2011 3:30 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] SIP calls that aren't torn down

That's pretty much what Broadworks does with its configurable idle watchdog
timer.  Of course, every now and then it gets confused and tears down lots
of conference bridge legs if the conference runs over 2 hours.....which is
the maximum we can set the timer to.

--Jon Radel

On 6/7/11 3:25 PM, Frank Bulk wrote:
> Over the last few months our softswitch has accumulated 10 "stuck" 
> calls where there's no media traffic.  From what the softswitch vendor 
> can tell or guess, it just didn't receive a BYE to tear down the call.
> We know that most SIP traffic on 5060 is UDP, and UDP is connectionless.
> How are other vendors and systems managing such scenarios?  I 
> suggested a "no media" test where after x hours of no media, to tear 
> down the call and log the info.
> Thoughts?
> Frank
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops

More information about the VoiceOps mailing list