[asterisk-bugs] [Asterisk 0018781]: [patch] segfault with remote_bridge_loop seems to be when transferring call

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Feb 17 03:31:40 CST 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18781 
====================================================================== 
Reported By:                alecdavis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18781
Category:                   Core/RTP
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.8.2.3 
JIRA:                       SWP-3081 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-02-09 19:18 CST
Last Modified:              2011-02-17 03:31 CST
====================================================================== 
Summary:                    [patch] segfault with remote_bridge_loop seems to be
when transferring call
Description: 
Bug reported on 1.8.2 tag release, after experiencing similar on 1.8.2.3
tagged release.

core dump attached for 1.8.2


====================================================================== 

---------------------------------------------------------------------- 
 (0132070) alecdavis (manager) - 2011-02-17 03:31
 https://issues.asterisk.org/view.php?id=18781#c132070 
---------------------------------------------------------------------- 
This is with SVN-trunk-r308157M with bug18781.diff.txt applied

Setup:

   FXS
ASTERISK-myhome
   IAX2
    ||
    ||
   IAX2
ASTERISK-work
 SIP/GXP8923 SIP/GXP8922

console output:
 with simple call, note patch has extra debug prints.

   -- Accepting AUTHENTICATED call from XXX.YYY.ZZZ.AAA:
       > requested format = alaw,
       > requested prefs = (alaw|ulaw|gsm),
       > actual format = alaw,
       > host prefs = (alaw|ulaw|gsm),
       > priority = mine
    -- Executing [8923 at trusted:1] Dial("IAX2/myhome-2102",
"SIP/GXP8923,,r") in new stack
  == Using SIP RTP CoS mark 5
    -- Called GXP8923
    -- SIP/GXP8923-00000006 is ringing
    -- SIP/GXP8923-00000006 answered IAX2/myhome-2102
    -- Started music on hold, class 'default', on IAX2/myhome-2102
  == Using SIP RTP CoS mark 5
    -- Executing [8922 at trusted:1] Dial("SIP/GXP8923-00000007",
"SIP/GXP8922,,r") in new stack
  == Using SIP RTP CoS mark 5
    -- Called GXP8922
    -- SIP/GXP8922-00000008 is ringing
    -- SIP/GXP8922-00000008 answered SIP/GXP8923-00000007
    -- Remotely bridging SIP/GXP8923-00000007 and SIP/GXP8922-00000008
[Feb 17 22:20:51] WARNING[3043]: rtp_engine.c:1078 remote_bridge_loop:
Channels c0->'SIP/GXP8923-00000007' c1->'SIP/GXP8922-00000008' in
remote_bridge_loop
    -- Started music on hold, class 'default', on SIP/GXP8922-00000008
    -- Stopped music on hold on IAX2/myhome-2102
    -- Stopped music on hold on SIP/GXP8922-00000008
[Feb 17 22:20:53] WARNING[3043]: rtp_engine.c:1086 remote_bridge_loop:
Oooh, something is weird, backing out
<b><u>>>>>>>>>>>>>>>> Normally would segfault here
<<<<<<<<<<<<<<<<<<<<<<</u></b>
[Feb 17 22:20:53] WARNING[3043]: rtp_engine.c:1276 remote_bridge_loop:
Channel c0->'IAX2/myhome-2102' changed, in bridge with
c1->'SIP/GXP8922-00000008'
  == Spawn extension (trusted, 8923, 1) exited non-zero on
'SIP/GXP8923-00000007<ZOMBIE>'
  == Spawn extension (trusted, 8922, 1) exited non-zero on
'IAX2/myhome-2102'
    -- Hungup 'IAX2/myhome-2102' 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-02-17 03:31 alecdavis      Note Added: 0132070                          
======================================================================




More information about the asterisk-bugs mailing list