[Home]

Summary:ASTERISK-07694: RTCP trying to remove non-existent schedule when its transmission failed
Reporter:Paul Cadach (pcadach)Labels:
Date Opened:2006-09-08 04:50:51Date Closed:2011-06-07 14:08:21
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/RTP
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Last Asterisk's messages:
RTCP SR transmission error, rtcp halted Interrupted system call
[Sep  8 15:14:00] NOTICE[21212]: sched.c:283 ast_sched_del: Attempted to delete nonexistent schedule entry 59!
!! Forcing immediate crash a-la abort !!
Segmentation fault (core dumped)


****** ADDITIONAL INFORMATION ******

(gdb) bt full
#0  0x080e984a in ast_sched_del (con=0xa5900a20, id=59) at sched.c:285
       s = (struct sched *) 0x0
#1  0x080ce8ae in ast_rtcp_write_sr (data=0x820e410) at rtp.c:2152
       rtp = (struct ast_rtp *) 0x820e410
       res = -1498614920
       len = 0
       now = {tv_sec = -1498614920, tv_usec = 135177851}
       now_lsw = 135554471
       now_msw = 2777680416
       rtcpheader = (unsigned int *) 0x80ea2c3
       lost = 2796352376
       extended = 0
       expected = 2796688092
       expected_interval = 2796352376
       received_interval = 0
       lost_interval = 5
       fraction = -1498615000
       dlsr = {tv_sec = -1498614984, tv_usec = 135237134}
       bdata = "..."
#2  0x080cf752 in ast_rtcp_write (data=0x820e410) at rtp.c:2345
       rtp = (struct ast_rtp *) 0x820e410
       res = -1498614848
#3  0x080e9b98 in ast_sched_runq (con=0xa5900a20) at sched.c:358
       current = (struct sched *) 0xa5902ce8
       tv = {tv_sec = 1157706840, tv_usec = 439873}
       numevents = 0
       res = 41

Comments:By: Paul Cadach (pcadach) 2006-09-12 11:35:39

This ticket marked as 'minor' instead of 'crash' because my test system have enabled DO_CRASH compiler option.
By: jmls (jmls) 2006-11-01 06:11:23.000-0600

would you be able to have a quick look at this ? Thanks
By: Olle Johansson (oej) 2006-11-10 07:55:08.000-0600

I think this was fixed earlier. Has it re-appeared?
By: Joshua C. Colp (jcolp) 2006-11-15 14:53:58.000-0600

According to oej this should have already been fixed and we have not heard anything to say otherwise yet. If this is not the case - please reopen and provide information for labbing it up. Thanks!