[Home]

Summary:ASTERISK-16869: Asterisk crash using PickUp Application
Reporter:Andre Luis (andrel)Labels:
Date Opened:2010-10-25 08:49:36Date Closed:2011-07-27 12:46:42
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) backtrace.tar.gz
( 1) backtrace.txt
( 2) full.log-backtrace
( 3) full-1
( 4) full-leak-full
( 5) valgrind1.tar.gz
( 6) valgrind-1.txt
( 7) valgrind-full.txt
( 8) valgrind-leak-full.tar.gz
Description:Asterisk crash when using PickUp() in DialPlan
logs as attachments.
Comments:By: Andre Luis (andrel) 2010-10-25 08:50:35

DialPLAN on Server 1

context voip {
_90XX => {
Dial(SIP/${EXTEN},40);
};

_9003 => {
PickUp(9002@voip);
};
};

context advdundi {
_01190XX => NoOp;
};

DialPLAN on Server 2

context voip {
_80XX => {
Dial(SIP/${EXTEN},40);
};

};

context advdundi {
_01180XX => NoOp;
};
ScenĂ¡rio

3 Asterisk Servers
1 = DUNDi Concentrator
2 = Normal PBX IP

Server 1:
- 9001 = sip user
- 9002 = sip user

Server 2:
- 8001 = sip user
- 8002 = sip user

8001 dials 0119002 (goes thru DUNDi IAX)
9001 dials 9003 (Local SIP)

Asterisk crash.

gdb and valgrind logs as attachements.

By: Andre Luis (andrel) 2010-10-25 08:51:09

btw in the compressed files are the debug log(full) and gdb or valgrind log.

By: Leif Madsen (lmadsen) 2010-11-01 14:48:09

Is there any chance you can re-send these as uncompressed archives? Attaching text files makes it much easier to work with.

By: Andre Luis (andrel) 2010-11-04 15:47:11

files resend as requested.

By: Russell Bryant (russell) 2011-07-27 12:46:35.773-0500

Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions

If this is still an issue, please open a new issue so it can be re-triaged appropriately. Thanks!