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:
Jun 27 17:52:59 rtphost /usr/local/sbin/kamailio[30745]: INFO: [R-OUTBOUND-VENDOR-TRY:33DEF60F-53ADAF79000E9F75-1C569700] -> Channel utilisation for this gateway: 112/200 Jun 27 17:52:59 rtphost /usr/local/sbin/kamailio[30745]: INFO: [R-OUTBOUND-VENDOR-ROUTE-TRY:33DEF60F-53ADAF79000E9F75-1C569700] Sending media through rtpproxy Jun 27 17:52:59 rtphost /usr/local/sbin/kamailio[30745]: INFO: [R-OUTBOUND-VENDOR-ROUTE-TRY:33DEF60F-53ADAF79000E9F75-1C569700] -> Final request URI: sip:14045372369@18.54.79.82:5060;user=phone Jun 27 17:52:59 rtphost /usr/local/sbin/kamailio[30745]: INFO: [R-OUTBOUND-VENDOR-ROUTE-TRY-BRANCH:33DEF60F-53ADAF79000E9F75-1C569700] -> Sending P-Asserted-Identity Jun 27 17:52:59 rtphost /usr/local/sbin/kamailio[30745]: INFO: [R-OUTBOUND-VENDOR-ROUTE-TRY-BRANCH:33DEF60F-53ADAF79000E9F75-1C569700] -> Sending NPDI parameters Jun 27 17:53:01 rtphost /usr/local/sbin/kamailio[30745]: INFO: [R-MAIN:33DEF60F-53ADAF79000E9F75-1C569700] CANCEL received from 104.251.251.8 (RURI=sip:14045372369;npdi=yes;rn=14047890081@205.97.81.46:5060;user=phone) Jun 27 17:53:02 rtphost /usr/local/sbin/kamailio[30749]: INFO: [R-OUTBOUND-VENDOR-ROUTE-ADVANCE:33DEF60F-53ADAF79000E9F75-1C569700] Transaction cancelled
I have another crash with this exact same assertion failure. I'll try to look up its Call-ID (if I still have the logs) and see if it follows a similar pattern.