[asterisk-bugs] [JIRA] (ASTERISK-23310) bridged channel crashes in bridge_p2p_rtp_write

[Jeremy Lainé (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215273#comment-215273 ] 

Jeremy Lainé commented on ASTERISK-23310:
-----------------------------------------

I have seen "bag magic number" errors in the following situation:

- leg B (contact) is issued a Bridge to leg A (operator)
- leg B is sent a reinvite
- leg A is sent a reinvite
- leg A accepts the reinvite with a 200 code
- leg B fails to reinvite with a 500 code
- leg B says BYE
- leg A goes back to the Wait
- leg B is destroyed
- bad magic number
                
> bridged channel crashes in bridge_p2p_rtp_write
> -----------------------------------------------
>
>                 Key: ASTERISK-23310
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23310
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 11.7.0
>         Environment: Debian wheezy
>            Reporter: Jeremy Lainé
>         Attachments: crash-backtrace.txt
>
>
> I have encountered numerous crashes using Bridge, which always involve bridge_p2p_rtp_write. To sumarize the setup:
> - two calls are fired up via Originate (one to an operator, one to a contact)
> - the operator gets put into an extension which basically does Answer + Wait(1800)
> - when the contact picks up, he gets bridged to the operator
> - the contact hangs up => the operator returns to the extension and waits some more
> .. and at some point things fall apart, and I start getting "bad magic number" warnings and eventually asterisk crashes, but always in bridge_p2p_rtp_write.
> An example:
> [Feb 14 15:47:15] DEBUG[25480][C-00000196] res_rtp_asterisk.c: Remote address is null, most likely RTP has been stopped
> [Feb 14 15:47:15] DEBUG[25480][C-00000196] res_rtp_asterisk.c: Remote address is null, most likely RTP has been stopped
> [Feb 14 15:47:15] DEBUG[25480][C-00000196] res_rtp_asterisk.c: Remote address is null, most likely RTP has been stopped
> [Feb 14 15:47:15] DEBUG[24287] chan_sip.c: Auto destroying SIP dialog '13e862723108b2aa2dbf50f14b7327ed at MY.IP.ADDRESS.HERE:5060'
> [Feb 14 15:47:15] DEBUG[24287] chan_sip.c: Destroying SIP dialog 13e862723108b2aa2dbf50f14b7327ed at MY.IP.ADDRESS.HERE:5060
> [Feb 14 15:47:15] VERBOSE[24287] chan_sip.c: Really destroying SIP dialog '13e862723108b2aa2dbf50f14b7327ed at MY.IP.ADDRESS.HERE:5060' Method: BYE
> [Feb 14 15:47:15] DEBUG[24287] rtp_engine.c: Destroyed RTP instance '0x7f5b980d17b8'
> [Feb 14 15:47:15] ERROR[25480][C-00000196] astobj2.c: bad magic number for object 0x7f5b98146488. Object is likely destroyed.
> [Feb 14 15:47:15] ERROR[25480][C-00000196] astobj2.c: bad magic number for object 0x7f5b98146488. Object is likely destroyed.
> [Feb 14 15:47:15] DEBUG[25480][C-00000196] res_rtp_asterisk.c: Unsupported payload type received

--
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