[Home]

Summary:ASTERISK-18638: Crash when using chan_unistim
Reporter:Jonn Taylor (jonnt)Labels:
Date Opened:2011-09-28 15:03:29Date Closed:2011-10-11 11:04:36
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_unistim
Versions:1.8.7.0 Frequency of
Occurrence
Constant
Related
Issues:
Environment:CentOS 5 x86Attachments:( 0) asterisk-1.8.7.0-crash-trace.txt
Description:Asterisk segfaults when using a unistim phone. SIP phones seem to be ok. This was an upgrade from 1.6.2.x
Comments:By: Jonn Taylor (jonnt) 2011-09-28 15:04:50.318-0500

back trace

By: Jonn Taylor (jonnt) 2011-09-28 15:55:57.418-0500

Rolled back one version to 1.8.6.0 and applied patch from ASTERISK-16890 and problem went away.

https://issues.asterisk.org/jira/secure/attachment/41132/chan_unistim.c.1.8.6.0.diff

By: Igor Goncharovsky (igorg) 2011-09-28 23:36:11.804-0500

It is known issue, caused by not specified ip address protocol information. I'll fix it shortly

By: Leif Madsen (lmadsen) 2011-10-03 12:07:02.629-0500

Assigned to the chan_unistim maintainer.

By: Jonn Taylor (jonnt) 2011-10-05 15:30:45.486-0500

Got 1.8.6.0 patch applied to current 1.8 branch(r335064). This seems to have resolved the crash at this point. Will do more testing.

By: Jonn Taylor (jonnt) 2011-10-10 08:47:41.241-0500

Worked ok for about an hour and the asterisk crashed. Went back to 1.8.6.0.

By: Igor Goncharovsky (igorg) 2011-10-10 08:55:42.675-0500

If asterisk crashed in other function then ast_sockaddr_copy, please create new bug report with attached new trace

By: Jonn Taylor (jonnt) 2011-10-10 09:04:51.480-0500

Crashed the same way.

By: Igor Goncharovsky (igorg) 2011-10-10 09:08:41.152-0500

Please attach backtrace, I'll reopen issue

By: Igor Goncharovsky (igorg) 2011-10-10 09:09:58.621-0500

And what exact branch and revision you have used for testing?

By: Jonn Taylor (jonnt) 2011-10-11 11:00:24.778-0500

I am using asterisk-1.8.7.0.tar.gz

By: Igor Goncharovsky (igorg) 2011-10-11 11:04:26.713-0500

Change made in 1.8 branch and it'll be released in 1.8.8.0 or 1.8.9.0. Issue closed

By: Jonn Taylor (jonnt) 2011-10-11 12:03:02.508-0500

Tested 1.8 branch and no problems so far.