[asterisk-bugs] [Asterisk-GUI 0015422]: Incoming Calling Rules can't be saved

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15422 
====================================================================== 
Reported By:                novazur
Assigned To:                awk
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   15422
Category:                   General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk GUI Version:       SVN 
Asterisk Version:           1.6.1.1 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 4951 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-06-29 18:56 CDT
Last Modified:              2009-07-24 09:52 CDT
====================================================================== 
Summary:                    Incoming Calling Rules can't be saved
Description: 
I'm very new with asterisk-gui.
I'm not sure that's a bug, but I don't understand what to do if I do
something bad.
I'm configuring my asterisk 1.6.1.1 with asterisk-gui (svn 4951). I want
to add a incoming calling rule.
I set
trunk = one trunk existing
timer interval = none
destination : user extension 102 (this only one I have for the moment)
and whatever I put in pattern (_X. , _XXXX, 1000 ...) I can't validate
(update). This only way to get out it cancel. And it doesn't show me any
field to complete or change.

Is it a bug ?

(sorry for my poor english)
====================================================================== 

---------------------------------------------------------------------- 
 (0108175) timeshell (reporter) - 2009-07-24 09:52
 https://issues.asterisk.org/view.php?id=15422#c108175 
---------------------------------------------------------------------- 
I've seen this happen too.  It seems to possibly occur when one attempts to
save without making sure all the fields are present.  Where upon fixing the
missing fields, it still won't save. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-24 09:52 timeshell      Note Added: 0108175                          
======================================================================