On Fri, Jul 11, 2008 at 1:21 PM, Will Davies <will at hugthebubble.co.uk> wrote: > > Yeah I know what you mean about the log. But look for the part where BYE > > message is sent or received, and see who sends it. If the sender is > pjsip, > > scan few lines before that, normally it should print out why it hangs up > the > > call (unless of course if it's user who hangs up the call). > > There is no BYE until one of us hangs up. I have a log that include several > minutes after the sound stopped. The only think I have managed to learn from > it is that the > 18:37:45.594 strm0x823ce04 Starting silence > 18:37:45.595 strm0x823ce04 Start talksprut.. > messages on the machine with the high cpu utilisation stop at the same time > that the call stops working. > I continue to get these messages at the other end but neither of us can > hear anything > > That should be fine. These messages are just to report that the VAD is kicking in. So this is not a call drop in the usual sense then since signaling seems to be still in place (calls are still CONFIRMED on both ends), but rather lost of audio after few minutes of conversation. Is that right? In that case then these links will probably help: http://trac.pjsip.org/repos/wiki/audio-problem-local-no-audio http://trac.pjsip.org/repos/wiki/audio-problem-remote-no-audio Cheers Benny -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080711/e8cc0f1a/attachment.html
