[asterisk-bugs] [Asterisk 0013341]: [patch] Problem using UpdateConfig AMI command when dstfilename points to non-existing file
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Aug 20 16:38:54 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13341
======================================================================
Reported By: vadim
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13341
Category: Core/ManagerInterface
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.4.22
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 135996
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-08-19 08:43 CDT
Last Modified: 2008-08-20 16:38 CDT
======================================================================
Summary: [patch] Problem using UpdateConfig AMI command when
dstfilename points to non-existing file
Description:
I'm running following putconfig command:
======
Action: updateconfig
reload: no
SrcFilename: extensions.conf
DstFilename: extensions.conf.new
Action-000000: newcat
Cat-000000: ami-test-01
Action-000001: append
Var-000001: exten
Value-000001: 888,1,Noop(888)
Cat-000001: ami-test-01
Action-000002: append
Var-000002: exten
Value-000002: 999,1,Noop(999)
Cat-000002: ami-test-0
=======
And getting following as result:
============
Response: Error
Message: Save of config failed
============
======================================================================
----------------------------------------------------------------------
(0091611) dbailey (administrator) - 2008-08-20 16:38
http://bugs.digium.com/view.php?id=13341#c91611
----------------------------------------------------------------------
A branch was made that has the mwi_send_thread functionality rolled back
into d0_monitor.
The original mwi_send_thread was not releasing resources (such as in
do_monitor) when asterisk initiated calls were being made. This led to
resource conflicts which in tunr caused this error.
By rolling the functionality into do_monitor, only the do_monitor thread
need be killed to prevent the resource conflict.
https://origsvn.digium.com/svn/asterisk/team/dbailey/13341_mwi
Issue History
Date Modified Username Field Change
======================================================================
2008-08-20 16:38 dbailey Note Added: 0091611
======================================================================
More information about the asterisk-bugs
mailing list