Summary: | ASTERISK-10293: Crash after second try to transfer, during atxfer | ||
Reporter: | the-chopper (the-chopper) | Labels: | |
Date Opened: | 2007-09-13 15:57:33 | Date Closed: | 2007-09-16 21:02:18 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Resources/res_features |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) asterisk.conf ( 1) bt ( 2) bt-full ( 3) bt-threadapply ( 4) extensions.conf ( 5) features.conf ( 6) fulllog ( 7) log ( 8) sip.conf | |
Description: | Test-Situation: Sipura SPA-941 (SIP/80) Grandstream GXV-3000 (SIP/81) X-Lite/Windows (SIP/82) I will use the SIP-Numbers to explain the Problem. The 82 calls the 81, 81 answers. The 82 initiates an atxfer to the 80 and hangs up. The 80 rings 5-times,no answer. The * tries to callback the 82 after that, now answer. Now * tries to transfer the call again, and during that 81 hangs up. After this try to transfer * chrashes. ****** ADDITIONAL INFORMATION ****** Exept the crash, everything is part of the scenario. | ||
Comments: | By: Joshua C. Colp (jcolp) 2007-09-14 09:33:54 Please provide the complete console output and a backtrace. By: the-chopper (the-chopper) 2007-09-14 13:05:57 Ok here are the information. I also uploaded the files i modified after 'make samples'. By: Digium Subversion (svnbot) 2007-09-16 21:02:18 Repository: asterisk Revision: 82546 ------------------------------------------------------------------------ r82546 | file | 2007-09-16 21:02:17 -0500 (Sun, 16 Sep 2007) | 4 lines (closes issue ASTERISK-10293) Reported by: the-chopper Don't bother hanging up the new channel if it does not exist yet. ------------------------------------------------------------------------ |