| Summary: | ASTERISK-07721: Call disconnect from Queue causes Seg Fault | ||
| Reporter: | Dennis Skinner (dcskinner) | Labels: | |
| Date Opened: | 2006-09-11 18:11:36 | Date Closed: | 2006-09-13 11:40:18 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) gdb.txt | |
| Description: | New Asterisk Installation running on CentOS4 (fully updated). Asterisk was compiled (along with zaptel) from the svn trunk. Setup a single queue and some agents. I have a Polycom phone and a softphone for testing. Polycom (extension 201) logs in via AgentCallbackLogin. Xlite calls in and gets to the Queue. Polycom rings, I answer and hit #. The call is connected fine. If either party hangs up, asterisk Seg Faults. The CLI output, and config file mods are attached along with the gdb and backtrace. I didn't include the sip debug. | ||
| Comments: | By: Dennis Skinner (dcskinner) 2006-09-12 11:26:36 Confirmed still seg faulting on r42827. By: jmls (jmls) 2006-09-12 12:34:16 have you tried the same thing with dynamic agents ? I can't reproduce this using them By: wunderkin (wunderkin) 2006-09-12 14:25:47 I'm having the same problem but with trunk. I did not see this one first, so I ended up submitting bug 7944. I am able to use a static member (member => SIP/2) fine. I tried to revert app_queue.c and chan_agent.c back as far as I could but I could only go back to the new loader changes. I think something there might have messed it up? By: Dennis Skinner (dcskinner) 2006-09-12 14:44:58 I compiled 1.2.12.1 and the corresponding zaptel and it seems to be working fine now. 2 things I did notice: 1. I forgot that I did not update this box, so CentOS was slightly out of date, most notably for asterisk (I think) would be the kernel (oh and they fixed the typo in spinlock.h). Now running 2.6.9-42. 2. This version complained about leftover asterisk modules, so I moved the modules dir out of the way and redid "make install". Could have been the kernel or conflicting modules or something else entirely. It was a long day yesterday and I can't recall if I rebooted after upgrading zaptel. Not sure if having the older kernel mods loaded would cause that or not. I only have SIP phones, so it is only loaded for meetme to work. By: Serge Vecher (serge-v) 2006-09-13 11:40:04 ok, closing this bug then, since the problem is not present in 1.2.12.1. Keeping 7944 open to find a solution for trunk. | ||