| Summary: | ASTERISK-08541: Cannot create incoming call route in AsteriskNOW - GUI does not store it. | ||
| Reporter: | mark_dammer (mark_dammer) | Labels: | |
| Date Opened: | 2007-01-10 09:23:42.000-0600 | Date Closed: | 2007-05-16 18:21:01 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | It is impossible to set up an incoming call route via the GUI. The route shows up in the list, but the system does not store it. After Clicking on another item in the menu and then returning to the Incoming Call Routes the rule has disappeared. Several users are reporting the same issue in the forums. This is a major issue as it is impossible to handle incoming calls with AsteriskNOW. The issue persisted after installing the latest AsteriskNOW updates this morning (10.01.2007). | ||
| Comments: | By: Pari Nannapaneni (pari) 2007-01-10 12:47:18.000-0600 James, when I did a conary update on asterisknow beta2, only some of the HTML files (like the astman.js and incoming.html ) were updated but some other files are not updated (trunks.html etc) which is causing this problem. So if you can build a new update for beta2 users with all of the files in "config" folder and also which updates their /etc/asterisk/gui_sysinfo with the latest one from the trunk, it would be great. -Pari By: mark_dammer (mark_dammer) 2007-01-16 09:06:43.000-0600 Pari, would it be possible to offer a source to download the missing files, so that there is at least a quick fix for this issue. thanks Mark By: Carlton O'Riley (funnymanva) 2007-02-14 16:38:51.000-0600 I've seen this as well and it is linked to the wizard not establishing a default DID entry in extensions.conf when it runs. If you delete whatever incoming lines the wizard detected and then readd, this problem goes away. By: Pari Nannapaneni (pari) 2007-05-16 18:21:01 the gui has more than a couple of hundred commits since this bug was reported. Please try with the latest gui and reopen if the problem still exists. thanks Pari | ||