Hi, I've been looking into the one bad thing about * which is there's no practical solution to running a console. You know the kind where you have rows of buttons each representing an extension. You press the button of the extension you want to transfer the call to, and it's done. There's the beginnig of GUI version but it's going to eat resources for running X which can become less than desirable, besides it's not very competitive having to use a mouse to handle calls. Too slow. So my idea is to have a text window. We can run at a higher res than 25x80 and squeeze a fair number of extensions onto it. The idea is to either use the extension number to access an extension or for less than 100 station system, use a two digit number for each person. This way there's minimum typing for the operator. This have enough space to easily display busy, hold, vmail etc. as the status of each extension. This way with a flatscreen monitor, or dual for bigger systems we can even run the console away from the server and use minimum bandwidth. The other status screen would be a voice mail screen where you can A) see the status of voicemail. Lines in use etc. B) change the name and features associated with voice mail. -- Steve Szmidt ___________________________________________________________ HTML in e-mail is not safe. It let's spammers know to spam you more, and sets you up for online attack through IE 4.x and above. Using HTML in e-mail only promotes it as safe to the uninitiated.
On Wed, 2003-04-23 at 14:28, steve wrote:> Hi, > > I've been looking into the one bad thing about * which is there's no > practical solution to running a console. You know the kind where > you have rows of buttons each representing an extension. You press > the button of the extension you want to transfer the call to, and > it's done.Couple of points here. What you point out isn't a bad thing. It may not live up to the expectation you have for asterisk right now, but it can't be everything to everybody. There are many of us using it just fine right now without that kind of functionality. This isn't to say it shouldn't be written and distributed at some point.> There's the beginnig of GUI version but it's going to eat resources > for running X which can become less than desirable, besides it's > not very competitive having to use a mouse to handle calls. Too > slow.This gui version, are you refering to gastman? if so, it is able to be run remotely. I run it on a free monitor here so I can track system usage. I rarely use it for call routing.> So my idea is to have a text window. We can run at a higher res than > 25x80 and squeeze a fair number of extensions onto it. > > The idea is to either use the extension number to access an > extension or for less than 100 station system, use a two digit > number for each person. This way there's minimum typing for the > operator. This have enough space to easily display busy, hold, > vmail etc. as the status of each extension. > > This way with a flatscreen monitor, or dual for bigger systems we > can even run the console away from the server and use minimum > bandwidth.Maybe go to a GUI, but without all the cutesy icons. The icons would get in the way in a larger system. Also if you could go touchscreen and IAX VoIP, you could have an answer button and the next icon click is the transfer. This shouldn't be too hard to write up in perl or so once someone wrappers up the manager communication.> The other status screen would be a voice mail screen where you can > A) see the status of voicemail. Lines in use etc. B) change the > name and features associated with voice mail.Voicemail doesn't use lines so part A is not exactly needed. As for B, why would a receptionist do this when it is available to each user via the phone line. -- Steven Critchfield <critch@basesys.com>
On Wed, 23 Apr 2003 15:28:54 -0400, steve wrote:>Hi, > >I've been looking into the one bad thing about * which is there's no >practical solution to running a console. You know the kind where >you have rows of buttons each representing an extension. You press >the button of the extension you want to transfer the call to, and >it's done.and operators keystation ...>There's the beginnig of GUI version but it's going to eat resources >for running X which can become less than desirable, besides it's >not very competitive having to use a mouse to handle calls. Too >slow. > >So my idea is to have a text window. We can run at a higher res than >25x80 and squeeze a fair number of extensions onto it.Why not use a text (or simple) windows (GUI) interface ?>The idea is to either use the extension number to access an >extension or for less than 100 station system, use a two digit >number for each person. This way there's minimum typing for the >operator. This have enough space to easily display busy, hold, >vmail etc. as the status of each extension.well from experience running pabx systems, it is a rare to use 2 digit extensions so don't restrict yourself.>This way with a flatscreen monitor, or dual for bigger systems we >can even run the console away from the server and use minimum >bandwidth. > >The other status screen would be a voice mail screen where you can >A) see the status of voicemail. Lines in use etc. B) change the >name and features associated with voice mail. > >Steve SzmidtGreat idea Steve, but whynot havea look at changing gastman ? I'm not a programmer, but I would have thought is might be better simplifying whats there now (particularly the windows version) and make the screen look more like an operators console, removing the funny graphics and standardising the layout... (instead of lines etc, light boxes which change colour and have the link details etc.... don't restrict yourself too much. Gary .
Well this may sound odd for the blind guy to say this but why not use a Touch screen system like one of those POS systems that restaurants use. And either run X with a MinWM or some such and give the user big colored buttons for functions. This way she/he has only one thing added to the desk. If you took it a step further you could eliminate the phone and have it do IAX or SIP for audio. Shawn -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of steve Sent: Wednesday, April 23, 2003 15:29 To: Asterisk-Users@lists.digium.com Subject: [Asterisk-Users] PBX Console Hi, I've been looking into the one bad thing about * which is there's no practical solution to running a console. You know the kind where you have rows of buttons each representing an extension. You press the button of the extension you want to transfer the call to, and it's done. There's the beginnig of GUI version but it's going to eat resources for running X which can become less than desirable, besides it's not very competitive having to use a mouse to handle calls. Too slow. So my idea is to have a text window. We can run at a higher res than 25x80 and squeeze a fair number of extensions onto it. The idea is to either use the extension number to access an extension or for less than 100 station system, use a two digit number for each person. This way there's minimum typing for the operator. This have enough space to easily display busy, hold, vmail etc. as the status of each extension. This way with a flatscreen monitor, or dual for bigger systems we can even run the console away from the server and use minimum bandwidth. The other status screen would be a voice mail screen where you can A) see the status of voicemail. Lines in use etc. B) change the name and features associated with voice mail. -- Steve Szmidt ___________________________________________________________ HTML in e-mail is not safe. It let's spammers know to spam you more, and sets you up for online attack through IE 4.x and above. Using HTML in e-mail only promotes it as safe to the uninitiated. _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com lists.digium.com/mailman/listinfo/asterisk-users