| Summary: | ASTERISK-01435: Asterisk coredump | ||
| Reporter: | tan (tan) | Labels: | |
| Date Opened: | 2004-04-19 18:19:53 | Date Closed: | 2004-09-25 02:51:25 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) core.4659.txt | |
| Description: | Asterisk coredumped on one of our asterisk gateways. The cvs is 18/12/04 so is near enough recent. The bt and bt full is attached. We have sip phones registered on this gateway. | ||
| Comments: | By: Mark Spencer (markster) 2004-04-19 18:25:37 This is a double AsyncGoto. AsyncGoto is not a normal event on a VoIP gateway. Do you have any event you can correspond to it (e.g. some sort of 302 Moved Temporarily)? Is it possible that it called a user who had forwarded their phone to their own extension? Finally, would you be okay with us creating an option to disable "REFER"? By: Mark Spencer (markster) 2004-04-19 18:25:51 err sorry, not just REFER but 302 Moved By: Mark Spencer (markster) 2004-04-19 18:58:36 I believe this was caused by the same REFER being received twice and our again intiating the async_goto on the line. I also fixed some locking that might have been related. Anyway this problem should be gone with one or both of the fixes that are in place. Reopen if it happens again. | ||