Summary:	ASTERISK-12291: Asterisk Now browser compatibility.
Reporter:	Kamil Czajko (kactus)	Labels:
Date Opened:	2008-06-30 20:38:04	Date Closed:	2008-07-05 18:18:51
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	. I did not set the category correctly.
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Asterisk Now has poor browser compatibility. Under Internet Explorer 7, sub pages do not load. Ie clicking on users will just keep the loading animating at the top but the active pages never load. Under Fire Fox 3, you can not select any thing from a multi list box. For example adding users is fine, but trying to select one to edit is not possible as it highlights all the entries and does not load any. It would also be nice if it had a few more built in smarts like freepbx in that placing an outbound dialing rule would check against numbers on the local pbx first. IE to check if this is a valid number on the pbx before passing it through the dialing rules. This would make Australian dial plans so much cleaner since 4 digit numbers are valid telephone numbers. All the best - Kamil
Comments:	By: Brandon Kruse (bkruse) 2008-06-30 23:09:45 Next time, try the mailing list. IE compatibility is not, and will never be on this version. The firefox 3 bug has been fixed, and committed. (This will come in the future) As far as the features, those features already exist, you just need to update. http://asteriskNOW.org/install-related By: Kamil Czajko (kactus) 2008-07-04 01:42:27 Hello Bkruse, I did not mean you any offense, however the system was updated using the console based update system, which mearly flashed and did not appear to change the issues reported. Since the system was installed from iso, svn recompile did not seem second nature for the project esp since the only options listed on the download page are isos and a link to digium "complete asterisk directory" which I did look through briefly but could not see where the source would be logically located. Finally as far as setting the not correct category/project, no revision information etc I selected the options that seemed to fit, from those that are available. None of them seemed to actually apply that closely to Asterisk Now so PBX General was the best fit. The asterisk version was the one returned by the console. It appears that bugs.digium.com is not really setup for reporting asterisk now issues, and that may be due to this being the wrong location. However this is where the "Report a bug" link (http://www.asterisknow.org/bugs) in Asterisk Now interface redirects to, so I can hardly be blamed for that either. I am aware of the irony that I'm probably going to be karma punished for reopening a case just to justify the reasons for the last karma punishment, but there is no other way for me to either respond or place a note without doing so. (As far as I can see at least) I might need to lookup the definition for bug, but I figured if it wasn't accessible from 80% of the browser marketshare it was worth reporting, esp since I couldn't see any documentation which specified browser requirements in the quickstart or support section. The appeal of Asterisk Now was to give end users more control over thier telephony without having to contact support for simple changes and that had less bloat then trixbox. Many of them are going to have difficulty understanding why they need to use a different browser for this. In any case all the best, hopefully you reverse your policy on IE in future. I don't see why active ajax-like controls would be breaking IE compatibility but I haven't had a chance to take a look at the source yet. Cheers - Kactus - I'm just a messenger :) By: Brandon Kruse (bkruse) 2008-07-05 18:18:49 IE has major problems, and obviously you are not a javascript developer :P Ya, support will come for it, give it some time. As far as updating, check the link I gave you. http://asteriskNOW.org/install-related