Is anyone else having trouble accessing it with something besides IE on a Windows box? Opera on Mac/FreeBSD/Linux just hangs at the login page, IE on Mac and Netscape on Solaris & Linux explode when loading login_page.php.
Hehe, that's slightly ironic... =P -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of James Sharp Sent: Monday, August 04, 2003 3:16 PM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] bugs.digium.com Is anyone else having trouble accessing it with something besides IE on a Windows box? Opera on Mac/FreeBSD/Linux just hangs at the login page, IE on Mac and Netscape on Solaris & Linux explode when loading login_page.php. _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users
On Monday 04 August 2003 02:16 pm, James Sharp wrote:> Is anyone else having trouble accessing it with something besides > IE on a Windows box? Opera on Mac/FreeBSD/Linux just hangs at the > login page, IE on Mac and Netscape on Solaris & Linux explode when > loading login_page.php.No, it works just fine on both Mozilla on Linux and Konqueror on Linux. -Tilghman
Works fine with Safari on MacOS X, FWIW. JT>Is anyone else having trouble accessing it with something besides IE on a >Windows box? Opera on Mac/FreeBSD/Linux just hangs at the login page, IE >on Mac and Netscape on Solaris & Linux explode when loading >login_page.php.
I opened bug #0007490 the other day. The issue was that when you do a 'sip debug' on the Asterisk console, there was no way to have this output go _only_ to the messages file. Someone with the id of 'russell' in his infinite wisdom has deemed that this isn't a bug, closed it, and given me -2 karma points. WTF??? It clearly is a bug, or at the VERY least, a limitation that needs to be fixed. So why the hell did he give me -2 karma points and say 'not actually a bug'. Fine... so how do you file an enhancement request then? If there's no way to file an enhancement request, then this is the most appropriate place to file this. Its damn irritating not being able to have 'sip debug' output go to a file only, and this is what the options in logger.conf imply you should be able to do, which is another reason I don't understand why he took this irrational action. In a PRODUCTION environment, you can't be running a sip debug to your console. Doug. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060727/a5510858/attachment.htm
> -----Original Message----- > From: Andrew Kohlsmith [mailto:akohlsmith-asterisk@benshaw.com] > Sent: Thursday, July 27, 2006 8:48 AM > To: asterisk-users@lists.digium.com > Subject: Re: [asterisk-users] bugs.digium.com > > > On Thursday 27 July 2006 10:32, Douglas Garstang wrote: > > It clearly is a bug, or at the VERY least, a limitation > that needs to be > > fixed. So why the hell did he give me -2 karma points and > say 'not actually > > a bug'. Fine... so how do you file an enhancement request > then? If there's > > no way to file an enhancement request, then this is the > most appropriate > > place to file this. > > When I report a bug, I can say it's for a "Feature Request". > Perhaps that's > what you should have done? > > > Its damn irritating not being able to have 'sip debug' > output go to a file > > only, and this is what the options in logger.conf imply you > should be able > > to do, which is another reason I don't understand why he took this > > irrational action. > > It's perfectly rational. You posted a bug that is at best a > feature request. > That's where the -2 came from. I agree with you in the sense > that it should > not have been closed but simply readdressed, but that's not my call.I really don't believe that it's a feature request. I belive it's a bug. By putting 'debug' against messages, and not against console, any sane person would think that debug (ie as a result of typing 'sip debug' would go to the messages file, and not to the console.> > > In a PRODUCTION environment, you can't be running a sip > debug to your > > console. > > In a PRODUCTION environment you have all of these issues > worked out in your > test lab before deploying to production.In a PRODUCTION environment, you will encounter issues. It happens. That's life. You need to be able to debug these problems. You can't possibly think that when you roll this out from dev to production, that there will be no issues.
> -----Original Message----- > From: Steven [mailto:asterisk@tescogroup.com] > Sent: Friday, July 28, 2006 6:44 AM > To: asterisk-users@lists.digium.com > Subject: [asterisk-users] Re: bugs.digium.com > > > "This is not a bug. It is just the way it works. > > The "sip debug" output is "verbose" output in asterisk > console terminology. Also, the "verbose" setting in > logger.conf has no effect > for the console in logger.conf. Printing verbose output is > only controlled by the "set verbose" CLI command. " > > I do not think that this is true. > > If I turn on "sip debug", it doesn't matter what I set "set > verbose" to, it will still go to console. > > I tried it with "set verbose 1" and "set verbose 0". > either way, it still went to console.Here! Here! :)