[Blink] Hangup on Timeout

Adrian Georgescu ag at ag-projects.com
Thu Nov 29 08:13:08 CET 2012


A 487 is sent as a response to a Cancel. The call was simply canceled by the other end.

There is nothing timeout related, or depends what you understand by timeout.

The core trace is a bit useless for analyzing this, use the SIP trace and notifications trace to understand the sequence of events instead.

Adrian

On Nov 28, 2012, at 11:24 PM, Bryan Miller wrote:

> Hi,
> 
> Is there a known issue regarding dropped calls and timing? I've encountered a number of users that have random dropped calls. 
> 
> During a time I was trying to duplicate the problem, I encountered a problem where a call would come in, ring once in the headset, the popup to accept/reject/busy the call would not come up, and then a split second before going to VM the popup would finally come up (but disappear due to the call going to VM).
> 
> I was able to pull this from the logs:
> 
> 2012-11-27 17:20:30.009000 (5) sip_endpoint.c: Processing incoming message: Request msg ACK/cseq=102 (rdata0x3d66014)
> 2012-11-27 17:20:30.009000 (5)   tsx0xfa9f064: Incoming Request msg ACK/cseq=102 (rdata0x3d66014) in state Completed
> 2012-11-27 17:20:30.009000 (5)   tsx0xfa9f064: State changed from Completed to Confirmed, event=RX_MSG
> 2012-11-27 17:20:30.009000 (5)   dlg0xfb77a64: Transaction tsx0xfa9f064 state changed to Confirmed
> 2012-11-27 17:20:30.034000 (5)   tsx0xfa9f064: Timeout timer event
> 2012-11-27 17:20:30.034000 (5)   tsx0xfa9f064: State changed from Confirmed to Terminated, event=TIMER
> 2012-11-27 17:20:30.034000 (5)   dlg0xfb77a64: Transaction tsx0xfa9f064 state changed to Terminated
> 2012-11-27 17:20:30.034000 (5)   tsx0xfa9f064: Timeout timer event
> 2012-11-27 17:20:30.034000 (5)   tsx0xfa9f064: State changed from Terminated to Destroyed, event=TIMER
> 2012-11-27 17:20:30.034000 (5)  tdta0xfb39600: Destroying txdata Response msg 487/INVITE/cseq=102 (tdta0xfb39600)
> 2012-11-27 17:20:30.034000 (5)   tsx0xfa9f064: Transaction destroyed!
> 
> So, within less than a second, it would timeout. Am I correct in reading the log that blink sent a 487? I wasn't able to get a sip trace for this at the time, so I didn't see what direction the 487 was sent in. 
> 
> I unchecked the "Hangup on Timeout", and I wasn't able to duplicate the problem afterwards.
> 
> I've set this for the users that are experiencing random dropped calls and waiting for feedback, but I wanted to get some input on this problem scenario. 
> 
> Thanks,
> 
> Bryan Miller
> socialserve.com
> _______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
> 




More information about the Blink mailing list