[Asterisk-bugs] [Asterisk 0010096]: "Maximum PBX stack exceeded" raised by including more than AST_PBX_MAX_STACK *not nested* contexts
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Jul 2 10:33:31 CDT 2007
email_notification_title_for_action_bugnote_submitted
======================================================================
http://bugs.digium.com/view.php?id=10096
======================================================================
Reported By: AlexB
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 10096
Category: PBX/General
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.2.19
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: No
Request Review:
======================================================================
Date Submitted: 07-02-2007 04:54 CDT
Last Modified: 07-02-2007 10:33 CDT
======================================================================
Summary: "Maximum PBX stack exceeded" raised by including
more than AST_PBX_MAX_STACK *not nested* contexts
Description:
Including more than 127 contexts causes
Jul 2 11:16:22 WARNING[5561] pbx.c: Maximum PBX stack exceeded
Please note they are not nested, but just included in one single context.
The value depends by AST_PBX_MAX_STACK, which is set to 128. Anyway this is
supposed to be the maximum depth, not the number of includes.
This behaviour has already been pointed out on the dev mailing list:
http://lists.digium.com/pipermail/asterisk-dev/2007-June/028164.html
There are also other threads opened, but unfortunately the discussion was
not fed by any developer. However this is a bug and plain Asterisk files to
reproduce it are attached.
======================================================================
----------------------------------------------------------------------
Corydon76 - 07-02-07 10:33
----------------------------------------------------------------------
Seems rather contrived. Wouldn't it be easier simply to use contexts as
classes of extensions, rather than to assign one extension to each context?
Issue History
Date Modified Username Field Change
======================================================================
07-02-07 04:54 AlexB New Issue
07-02-07 04:54 AlexB Asterisk Version => 1.2.19
07-02-07 04:54 AlexB SVN Branch (only for SVN checkou => N/A
07-02-07 04:54 AlexB Disclaimer on File? => No
07-02-07 04:56 AlexB File Added: extensions.conf
======================================================================
More information about the Asterisk-bugs
mailing list