[cisco-voip] CUBE SIP-to-SIP Call Leg Hangs

Mark Holloway mh at markholloway.com
Sun Nov 7 13:42:12 EST 2010


One thing you could do is try and modify your SIP audit timer interval to a shorter duration.  If the remote side (receiver of the audit message) doesn't respond (or responds with a 4xx/6xx message) the call is disconnected.

On Nov 7, 2010, at 11:12 AM, ash AD wrote:

> Have any expirienced call leg hangs using 12.4(24)T3 or 4? The issue seems to happen when a remote party terminates the call without a 200 BYE message. I have remote offices separated by satellite links. These sites occasionally lose connectivity to the centralized CUBE gatways that extends connectivity to ITSPs. When thier path is drops and the centralized CUBEs, and they don't see the call taredown, the dead call legs don't timeout. I have try playing with multiple timers but have had no luck. This is issue snowballs to get worst and worst until the CUBE hits CPU peg because it is exceding its IP-IP capabilities. These are SIP EO-to-EO calls.
>  
> Pete
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101107/bfb4d22a/attachment.html>


More information about the cisco-voip mailing list