On 06/27/2014 05:28 PM, Richard Fuchs wrote:
On 06/27/14 17:26, Alex Balashov wrote:
Hi Richard,
Yes indeed, I am able to pull sfd->call->callid.s in frame 4.
The assert is, of course, stream != NULL:
547 assert(stream != NULL);
And that's where it blows up:
(gdb) print stream
$6 = (struct packet_stream *) 0x0
I seem to have some "interesting" calls going through this system, such
that I can deliver you a "monologue == NULL" crash bug one week and a
stream-NULL abrt/exit the next. :-)
I looked up that Call-ID in the logs and saw this kind of call flow:
...
Also look up the call-id in the rtpengine logs please. The full log (esp
including the SDP) might allow me to reproduce this.
I will. I'm just afraid they may have been rotated out or that the entry
for this was rate-limited out. We forgot to disable rate-limiting on
rsyslogd, and this is a very high call pace installation.
--
Alex Balashov - Principal
Evariste Systems LLC
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Please be kind to the English language:
http://www.entrepreneur.com/article/232906
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
