[asterisk-bugs] [JIRA] (ASTERISK-22802) MeetMe: crash when ast_check_hangup is called on a NULL conference channel

[Asterisk Team (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team closed ASTERISK-22802.
------------------------------------

    Resolution: Suspended

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> MeetMe: crash when ast_check_hangup is called on a NULL conference channel
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-22802
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22802
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_meetme
>    Affects Versions: 1.8.23.0
>         Environment: CentOS 5.8, 64bit System, 2GB RAM, 
>            Reporter: Grace Okafor 
>            Assignee: Joshua Colp
>         Attachments: backtrace.txt
>
>
> I installed an application Web-meetme on the server. I schedule a conference, which works well, I can login one user. but when a second user tries to join the conference, it gives the error:
> {noformat}
> /usr/sbin/safe_asterisk: line 145: 1732 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY}
> Asterisk ended with exit status 139
> Asterisk exited on signal 11.
> Automatically restarting Asterisk.
> {noformat}
> After checking severally online for a  solution, I decided to submit the issue here. Thanks



--
This message was sent by Atlassian JIRA
(v6.2#6252)