|
Good advice for me. I think my plan (I am not sure if it was others)
was that this page would purely discuss the accessibility of the
clients and possibly more generally the systems (eg. the skype
protocol, SIP, jingle (gtalk), etc) by referring to the clients for
those systems. As an example: ===== Skype ===== The official skype client is currently inaccessible as it uses QT. You may have success using some features of skype by using the skype4pidgin or bitlbee-skype plugins. (may be a little more detail on these plugins and links to the various websites) ========= TeamSpeak ========= While there is a linux client made by TeamSpeak it is inaccessible as it doesn't use GTK. (I may mention the TeamBlittityBlattity client if anyone could say that they got it working) === SIP === There are many clients for SIP, some of the accessible ones follow with some details of how accessible they are. Linphone ======== Linphone has both command line and graphical interfaces. The command line client poses no accessibility issues. The graphical interface seems to be accessible and no obvious accessibility issues have been noticed. (may change status if anyone notices accessibility issues) Ekiga ===== Ekiga is reasonably accessible. Some problems have been noticed in version 2. It is reported that version 3 is better to use if possible. Some of that might need expanding, but as I hope I indicated I don't intend to go into quality of the system, how to use the system (IE needing a SIP provider if you aren't going to run your own SIP server, etc), I will only cover the accessibility of them with the various software. I feel I should do some grouping (eg. by protocol) simply to help in structuring it incase users find one client not suitable but want a client to work with the protocol they used in the past (eg. if they are moving from windows and are looking for a suitable linux client). So how does this sound? Should I be including server software or just stick with the clients? Michael Whapples On 16/03/09 15:00, Janina Sajka wrote: > Michael Whapples writes: >> A slight aside, is SIP audio quality dependent on the SIP provider? >> > > Not exactly. It's dependent on the codec you employ. My current high > quality favorite codec is CELT. > > I would suggest carefully delineating protocols, codecs, clients, > servers, and gateways, and service providers. If you're going to > maintain a page, I would suggest carefully defining these so that > you can then name which are provided by any particular "system," as > you used the term previously. Else, you might confuse things by > lumping Skype and SIP together. Yes, there's an intersection of the > two in that they are both communication protocols, but SIP provides > no clients on the one hand, whereas Skype is also a client which > supports SIP in addition to its own proprietary communications > protocol on the other hand. > > There's an important web site you should know if you mean to become > a Vo/IP mayven: > > http://voipinfo.org > > Let me add that I have used only Vo/IP solutions for my telephony > needs for the past three or more years. The only exception to this is > my cell phone. There's plenty accessibility to be had if you're > willing to work with ASCII or XML config files and CLI. I have not > found GUI apps to be satisfactory, for one reason or another. Some > examples: > > In Clients -- > > Twinkle: Fully accessible via CLI, but not on the GUI as it's QT > based. > > Linphone: Fully accessible on the cli, and possibly close on the > GUI. Worth checking into further as it does run with Orca. > > I'm currently using linphone with a Sennheiser PC166 USB headset for > all my teleconferences. > > In Hardware Clients: > > I like Snom: http://snom.com. I have three Snom 320's and a couple > Snom 300's. You configure these through their builtin web servers > which are very accessible via Orca and FF (or even Lynx). > > > In Servers: > > Free Switch is the current fa vorite because it supports CELT. > Asterisk is also fully accessible. Note that these can be used as > clients as well. > > In gateways and service providers: > > I'm currently liking Vitelity, http://vitelity.net. Their web based > management screens are pretty bad from an accessibility point of > view, but this seems generally the case in the Vo/IP industry. I have > learned to deal with them. I buy phone numbers from Vitelity, and I > use them as my gateway to the "Public Switched Telephone Network > (PSTN)." One can, however, also use Vitelity as a service provider. > |