[VoiceOps] SIP calls that aren't torn down

anorexicpoodle anorexicpoodle at gmail.com
Tue Jun 7 16:55:44 EDT 2011

Nope probably not. 

Im not familliar with Broadsofts method, but Metaswitch does something
similar, and instead of using session timers, uses regular re-invites to
detect if all involved endpoints are still alive. 

We found this a little heavy handed with their stock timers, so we
fiddled with it until we were happy. 

I suspect the rationale here is that using RFC 4028 depends on both far
ends supporting that RFC, and implementing it properly, which takes the
control out of the softswitch's hands. Using a re-invite as a polling
mechanism guarantees the polling works with even older (or cheaper) SIP
endpoints that dont support session timers. 

On Tue, 2011-06-07 at 16:44 -0400, Alex Balashov wrote:

> On 06/07/2011 04:42 PM, Scott Berkman wrote:
> > 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.
> This is BroadSoft marketing bullshit for SSTs, right?  (i.e. RFC 4028)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110607/0388d608/attachment.html>

More information about the VoiceOps mailing list