[asterisk-bugs] [JIRA] (ASTERISK-22258) Queue crashes when publishing message to Stasis after ringing busy Agent

Matt Jordan (JIRA) noreply at issues.asterisk.org
Wed Aug 7 08:27:03 CDT 2013


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

Matt Jordan updated ASTERISK-22258:
-----------------------------------

    Attachment: ASTERISK-22258-trunk.diff

It looks like a call to {{rna()}}, which handles raising the Stasis message, occurred after the agent channel was hung up. This patch reorders the calls so that the message indicating that the agent channel failed to answer occurs prior to hanging up the channel.

Can you give this patch a try and see if it resolves the issue?

Thanks!
                
> Queue crashes when publishing message to Stasis after ringing busy Agent
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-22258
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22258
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: SVN
>         Environment: openSUSE 12.2 (x86_64)
>            Reporter: Kiril Valchev
>            Severity: Critical
>         Attachments: ASTERISK-22258-trunk.diff, backtrace.txt, core.7z
>
>
> Application exit with signal 11 Segmentation fault after reject call from agent.
>  -- Executing [1234 at ael-q:1] Queue("Console/dsp", "test") in new stack
>     -- Music class  requested but no musiconhold loaded.
>   == Using SIP RTP TOS bits 184
>   == Using SIP RTP CoS mark 5
>     -- Called SIP/115
>     -- SIP/115-00000000 connected line has changed. Saving it until answer for Console/dsp
>     -- SIP/115-00000000 is ringing
>     -- SIP/115-00000000 is busy
> [Aug  6 09:43:55] ERROR[24877][C-00000000]: lock.c:140 __ast_pthread_mutex_destroy: astobj2.c line 483 (internal_ao2_ref): Error destroying mutex &obj_mutex->mutex.lock: Device or resource busy
> [Aug  6 09:43:55] ERROR[24877][C-00000000]: astobj2.c:165 INTERNAL_OBJ: bad magic number for object 0x7f83100403b8. Object is likely destroyed.
>     -- Nobody picked up in 7000 ms

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list