Linux users have a new way to get help, without being talked down to or berated for not putting in enough effort before asking for help!

I saw this post on Mastodon, authored by @SirBoostALot, and got permission from the author to repost it here, because I think it makes some good points:

Struggling to remember all those commands? You’re not the only one – and the Linux “experts” need to understand that. Linux “experts” who look down on GUI users are missing the point – not everyone has a photographic memory.

For over a decade I have wondered why some Linux users, particularly those of the somewhat “elitist” variety, keep saying on the one hand that everyone should consider switching to Linux but then in the next breath suggest that they need to learn how to do things from the Linux command prompt or in a terminal window. You can almost hear the contempt in their voice whenever they mention a . Worse yet, some of them seem to have the belief that everyone over the age of 5 and under the age of 75 needs to learn how to write code.

The problem with such people is that they have the same logical fallacy that many people have, which is that we think everyone’s experience is similar to our own. Objectively we know this isn’t true (well, at least most of us do) but still there is a part of us that believes that if “if I could do it, anyone can”, and worse yet, they think that if “it” was easy for them it will be easy for everyone else. And even if “it” wasn’t easy, everyone should still be able to do it with sufficient dedication and motivation. And if anyone isn’t as motivated as they are, well then they are just being lazy, or are just wanting to be “spoon-fed” information.

What I believe such people don’t realize is they have one big advantage over many of the other people they share the planet with, and that is that they have good memories, maybe even near-photographic memories. When I was in school, in the pre-internet era, many of the classes involved a lot of rote memorization. I would generally pull A’s and B’s in any subject that wasn’t highly dependent on memorization, but if memorization was involved I was lucky if I could pull a D rather than failing the class completely. Some other students would ace those kinds of classes with no sweat, because they had good memories, and I imagine some of them may have gone on to become computer programmers. Nowadays they would be the kind of people who love using the command line rather than a GUI.

See, it takes a good memory to remember all those commands and all their options. In a GUI you are shown all your options, and often if you mouse over an option there is explanatory text. And some of us really need that, because again, we don’t have good memories. We simply can’t remember all those commands and options, even if we just read a man page or help screen ten minutes ago. Some people get around this by having “cheat sheets” of the commands and options they use the most, but then that limits them to a subset of all available commands (to the ones they have previously used).

When people with poor memories ask a question about how to do something in a Linux forum and the resident Linux “expert” respond in a dismissive way, implying they didn’t search hard enough or are just wanting to be “spoon-fed” answers, that is really upsetting. Not only do they probably have no idea which search terms to use, but that is not how users respond to each other in Windows or MacOS forums. In those forums, if someone asks a question and you don’t know the answer or don’t want to give it, you keep your hands off the damn keyboard and move on to the next post. This is a skill many Linux users don’t seem to have developed, at least in some forums. If you feel it is beneath you to “spoon feed” an answer to someone then just move on, because once you have insulted someone they will never appreciate anything you have to say, and they will always think of you as an arrogant donkey’s patootie.

And that brings us to , and why it is becoming so popular. A lot of Linux “experts” seem to hate AI, or see no use for it. They correctly point out that it sometimes hallucinates answers, and if you ask it a coding question you have to check pretty much every single line of code it spits out because that code may contain errors. AI’s are actually pretty stupid sometimes; they will make logical errors that most humans with any experience would not make. But still, AI’s are becoming more and more popular, and leading to decreased usage of forums such as StackExchange, for better or worse, and in my opinion there are two big reasons why.

First, they know most or all Linux commands, and have nearly perfect memories. If you have an average to poor memory, and you ask them to write a bash script to do something, they will like spit out code in a few seconds that would have taken you hours to research, and they will sometimes use Linux commands or statements that you had no idea even existed (and as time goes by, fewer and fewer of those are hallucinated commands that don’t actually exist). You may not have even known that there was a Linux command that will do a certain thing, but the AI does, particularly if it was trained on code.

Second, they always just deliver answers, They don’t chide the user for not having researched the question before asking, or for not reading a FAQ or a man page or some other piece of documentation that the user may not have known existed, or might not understand even if he had somehow stumbled across it. And they never complain that the user is being lazy, nor do that answer in that condescending tone that a few Linux “experts” that haunt various online forums seem to have adopted. I have never understood why some Linux “experts” complain that users want to be “spoon fed” answers, as if that’s a bad thing. Not everyone wants their operating system to be a puzzle, with new challenges to solve on an intermittent and unpredictable basis. Especially in the case of people coming from MacOS or Windows, most people are wanting their operating system to be as trouble-free as possible.

If you have a good memory, and if you really enjoy being presented with new challenges that can only be solved after a lot of effort and frustration, then you won’t get that most people want their operating system to be as invisible as possible, and to “just work”. And that most folks don’t want to ever have to use the command line, and they certainly don’t want to “learn” an operating system. When was the last time you heard someone say that people should “learn” Windows, or “learn” MacOS? I’m not saying that never happens, but it is a pretty rare thing to hear.

What would really be helpful, and I know some old-time Linux guys will consider this anathema, is a freely-accessible AI trained specifically on Linux and related subjects (the various Linux shells and maybe even programming languages commonly used in Linux, but with preference given to subjects that matter to users). Someplace that a new Linux user can go and ask questions and just get correct answers all day long. But also one that would that would learn and receive correction based on user input, for example if it offers a solution and nearly every user that tries that solution reports that it doesn’t work, the AI would start to prefer alternative solutions. In other words, don’t force the user to “learn Linux”; instead let the AI do it and then it can assist users in their time of need, with no condescension or other snarkiness.

And for those who would complain that AI’s use too much power, I say, seriously? How much power is consumed when users search web page after web page for an answer, mostly finding irrelevant information? And isn’t it worth using a little power so people can get their issues solved and get on with their lives, rather than spending an entire day or two trying to resolve one issue (and being insulted in the process)? And maybe to actually help those of us with terrible memories, so that we are not made to feel as if we are unworthy of using Linux?

Not all Linux “experts” are of the type mentioned in that post. I have encountered many that have been willing to go out of their way to be helpful! But, unfortunately, I have also encountered the type described above, and that’s never been pleasant.

But speaking of AI, here’s what I’d like to see. Imagine having an AI assistant that can just dive into all your past notes, articles, and even those old BASIC programs from back in the day, and then use that knowledge to help you out whenever you need it. That’s like having a personal librarian, tech support, and brainstorming partner all rolled into one!

I mean, think about it – you could just ask that AI thing, “Hey, remember that old file renaming program I had back in the day? Can you help me update that for modern Linux?” and BOOM, it’s got your back. No more digging through piles of old files and trying to piece it all together. The AI just takes care of it, using all the info it’s got stored up from your past experiences.

And the security aspect is super important, too. I mean, we all want to keep our personal stuff, well, personal, you know? So having something that runs locally and doesn’t send your data out to the internet is a must. That way, you can just feed it whatever you want, and it’ll be your own little knowledge base, ready to help you out whenever you need it.

The more I think about it, the more I’m convinced this is the kind of thing that could really change the game. It’s like having a personal assistant, but one that’s tailored specifically to your own experiences and knowledge. Someone’s probably already working on something like this as I write this. At least I hope so, because it could make our lives a whole lot easier!

Ted Cruz Pushes Bill to Hinder Community Broadband

Ordinarily, this is not a political blog – there are plenty of political blogs out there for those into that sort of thing, and there are also “Faux News” outlets for the racists, religious zealots, and just plain hateful people among us. Assuming you are not a total idiot (hopefully you would not be reading this blog if you are), you understand how important it is to prevent huge corporations such as Comcast and AT&T from enacting policies that are increasingly anti-consumer, and from successfully preventing new competition in areas where they have near-monopoly status. So, the last thing we need is a president that is in the pockets of the huge incumbent ISP’s and cable providers, and apparently that is exactly what you’d get with Ted Cruz (not to mention that many reports from former acquaintances indicate he’s just an awful person; kind of like the schoolyard bully you probably hated as a kid – if you want a repeat of a Richard Nixon or Lyndon Johnson presidency, Ted is probably your guy).

Now Presidential candidate Ted Cruz is the latest to rush to the defense of AT&T, Comcast, and other large providers with a new amendment aimed at defending these bills, which sometimes even ban communities from striking public/private partnerships to shore up broadband coverage.

Source: Ted Cruz Pushes Bill to Hinder Community Broadband | DSLReports

Not such a great deal on a VoIP PBX?

Is this the worst deal ever on a VoIP PBX? Probably not, but in our opinion it’s certainly not the best deal by a long shot, unless maybe they are providing a GREAT support package. See this thread on the PBX in a Flash forum. Interesting that their ad says “All products are sold on a No Return Basis.”

In case you’re not quite getting the picture, we’ll point you to this totally unrelated article. 😉 Compare what you see there with what’s pictured in the ad at the above link. We cannot know for sure that the innards of that ~$350 PBX are actually a ~$35 Raspberry Pi, at least not unless someone purchases one and disassembles it to find out, but you can definitely spot some similarities in the placement of the various input/output ports.

Rather than purchase any device costing a few hundred dollars on a “No Return Basis”, you might want to consider just getting a Raspberry Pi and using one of the distributions mentioned in our article, Asterisk on a Raspberry Pi – which distribution is best?. Even if you don’t agree with our conclusions in that article, any of the distributions mentioned there would probably be a better choice in the long run. But, that is just our opinion.

I no longer recommend using Asterisk’s Google Voice support — try these methods instead!

 

Important
This is an edited version of a post that originally appeared on a blog called The Michigan Telephone Blog, which was written by a friend before he decided to stop blogging. It is reposted with his permission. Comments dated before the year 2013 were originally posted to his blog.

EDIT (May, 2018): FreePBX and Asterisk users that wish to continue using Google Voice after Google drops XMPP support should go here: How to use Google Voice with FreePBX and Asterisk without using XMPP or buying new hardware.

This article was originally written in January of 2012, and has been heavily edited in an attempt to update it a bit.

Not that anyone probably cares what I think, but anyone who regularly reads this blog (or any of the other VoIP-related blog that cover Asterisk) may have noticed that prior to the release of Asterisk 11, Asterisk’s support for Google Voice had become less and less reliable over time, particularly for incoming calls. You have to do all sorts of “tricks” to make it work, and these usually involve adding delays that don’t always fix the problem, inconvenience your callers, and possibly cause more hangups as people get tired of waiting for you to answer the phone.

Therefore, I suggest that if you are using a version of Asterisk earlier than Asterisk 11, you stop using Asterisk’s Google Voice support completely. Assuming that you feel you must keep using an older version of Asterisk, I suggest trying one or more of the following:

  1. Use YATE as a gateway between Asterisk and Google Voice. See Using YATE to overcome Google Voice issues in FreeSWITCH and Asterisk, this article and this forum thread on YATE in a Flash, and this thread on YATE Tips & Tricks). YATE is what powers Bill Simon’s gateway (mentioned below). See comments by Bill and pianoquintet under this article.
  2. Use Bill Simon’s Google Voice-SIP gateway to handle your Google Voice calls. Some people may not want to rely on an external service for this, while others may very much appreciate having the option. I mention it for those in the latter group. For more information see Bill Simon’s Free SIP-to-XMPP Gateway Easily Puts Google Voice on Your VoIP Phone (Voxilla). While the linked articles talk about using the gateway with a SIP device, it can be used as an Asterisk trunk.  EDIT: As of April 7, 2015 the Google Voice Gateway has been relaunched and there is now a one-time fee to sign up.
  3. If your only issue is with incoming calls, you could use a DID to bring the calls into your system.  But keep in mind that Google Voice does not like it when calls are answered the moment they connect, so in your FreePBX Inbound Route be sure to set the “Pause Before Answer” option to at least 1.  I have found that a 1 second pause is sufficient, but I’m not saying that is the correct value for everyone, or even that everyone will need to include such a pause (some DID providers may delay the call sufficiently before connecting through to your system that the pause isn’t needed).

At this point, any of those would likely produce better results than using the Google Voice support in any version of Asterisk prior to Asterisk 11.

EVERYTHING in this article is my personal opinion.  Nothing here should be taken as a statement of fact.

EDIT:  Ward Mundy reports that he just may have found a workaround for the incoming calls issue — see this thread in the PBX in a Flash forum.

Mini-review of Sangoma U100 USBfxo device

 

Important
This is an edited version of a post that originally appeared on a blog called The Michigan Telephone Blog, which was written by a friend before he decided to stop blogging. It is reposted with his permission. Comments dated before the year 2013 were originally posted to his blog.

This article was originally posted in June, 2010.

I recently had the experience of trying to help someone make a Sangoma USBfxo device (model U100) work on a server that runs FreePBX and Asterisk. The advertised features of this device are as follows:

  • Dual FXO ports
  • Easy installation, no need to open up computer to install PCI/PCIe card
  • Supports up to 2 simultaneous calls
  • Compact plastic enclosure
  • Low power consumption, takes power from USB bus
  • USB 2.0 compliant (compatible with USB 1.1)

The first thing I would note is that although you don’t have to open up the computer, it’s definitely not “plug and play.” At the very least you have to install driver software, and on an Asterisk server you will also need to install and configure DADHI or ZAPTEL (unless this has already been done). Depending on your level of expertise, this might be easy, or quite daunting. I would certainly take issue with the claim of “easy installation” although I can understand how a true Linux geek might consider it a walk in the park. It wasn’t so much that there were any major hitches in the installation as that it was time consuming and required quite a bit of mental effort to figure out what needed to be done — someone who has just set up a PBX using a “load and go” distribution like Elastix, PBX in a Flash, AsteriskNOW, Trixbox, etc. might not find it all that easy to get this thing working.

The major issue we had was with the performance. We initially discovered that it was “clipping” speech severely, causing audio artifacts that are difficult to describe in print, but unpleasant to hear. We got in touch with Sangoma customer support and finally traced the problem to the built in hardware echo cancellation. By disabling the hardware echo cancellation, the speech was clear, but of course we then had mild echo. Enabling echo cancellation in Zaptel fixed that on a temporary basis, but about a week later Sangoma customer support e-mailed us and suggested that we try OSLEC, the open source echo canceler. We might have actually done that had we not discovered another issue in the meantime, that made us decide we didn’t want to mess with this unit anymore.

This new issue was that initially, it did not pick up incoming caller ID on incoming calls. We discovered that this could be fixed by changing the gain settings in Zaptel, but even when we did that it still wasn’t 100% reliable (I’d say it worked about 90% of the time). And, the downside of that was that we had to reduce the incoming gain, so that it was harder to hear callers.

We’ve used Sipura SPA-3000’s before for this same function, although they are only single line units (they have one FXS port and one FXO port) and have never had any of these issues. The main reason we tried the USBfxo was because we wanted two FXO ports, and also liked the idea that it was powered off the USB cable, and didn’t require us to have yet another device with a “wall wart” to plug in. But the difficulties with Caller ID, volume levels, and the fact that Sangoma had apparently given up on getting the hardware echo cancellation to work without distorting the audio led us to get frustrated with this device fairly quickly. The non-techies that had to make and receive calls that went through this device were not very understanding of the issues, especially since the SPA-3000’s (now superseded by the Linksys SPA-3102, which is essentially an updated version of the Sipura SPA-3000) had always worked much more reliably. We finally gave in and found another Sipura SPA-3000 on eBay and put it into service, and within a relatively short time (part of which was spent locating and installing updated firmware) it was working like a champ. Unlike the Sangoma, it detects the Caller ID 100% of the time, and we can tweak the transmit and receive gain to comfortable levels.

My personal opinion is that Sangoma should be ashamed to put their name on the USBfxo.  The hardware echo cancellation, in a word, sucks.  And one of the big reasons you’d buy a brand like Sangoma in the first place is because of the supposedly superior echo cancellation.  Echo cancellation is supposed to cancel echo, not make it sound like your words are clipped.  My guess is that the hardware echo cancellation is far too aggressive and they don’t give you any way to “tune” it — you can either enable or disable it, but that’s all.  The USBfxo is a great idea, but it needs to go back to the drawing board. Sangoma’s motto (shown on their Wiki pages, etc.) is “Because it must work!”, but apparently that motto does not imply that it must work well!

Also, a note to Sangoma customer service — next time a customer is dropping hints that they’d like you to take your defective unit back and send a replacement, you might want to be a bit more responsive to that request. We were willing to work with you up to a point but the message came through loud and clear that you really didn’t want to replace this dog of a device unless you absolutely had to.  We didn’t sign up to be beta testers, we just wanted the damn thing to work. Given Sangoma’s (perhaps undeserved) reputation we really thought you’d be more agreeable to making sure that we got a unit that worked, not making us try a bunch of different things and then ultimately told to try OSLEC, effectively giving up hope that the hardware echo cancellation would ever work properly.

Another suggestion to Sangoma (or any other manufacturer that may be listening) — most of us who did not cut our teeth on Linux would probably prefer not to have to mess with ZAPTEL or DADHI.  The nice thing about the Linksys/Sipura devices is that they sit out on the network and appear as just another SIP-based device, and in FreePBX you configure them pretty much as you would any other SIP trunk.  I’m not saying that installing any of these devices is the proverbial “piece of cake”, especially if you have never done it before, but when you have to start installing and configuring drivers, that goes outside of the realm of what I would consider easy to install. What someone really needs to come out with is an inexpensive four to six-port SIP based FXO device that sits out on your local network, like the SPA-3000/3102.

If you are in need of one or two FXO ports for your Asterisk server, my advice would be to first try one or two Sipura SPA-3000 or Linksys SPA-3102 devices (following these instructions if you are a FreePBX user) — if those do not work the way you’d like, you can always resell them on eBay and then try a more expensive solution.  If your server doesn’t have card slots (as is increasingly the case, as users turn to small computers like the Acer Aspire Revo to use as small, power-efficient PBX’s) then your choices are limited to external devices such as the aformentioned units. However, if your system can accept internal cards, then you can buy cards that provide FXO ports from several manufacturers, including Digium and Sangoma (if you need eight or more FXO ports than I believe there are other external options, but they are quite a bit more pricey and I have not really investigated them, so I won’t comment on them at this point.  However, if any manufacturer would care to send a review sample, I’d be more than happy to give it a try!). 😉

The one caveat I will add is that not every device will work on every line.  If you have a very long line from a traditional telephone company, your requirements (and experience with a particular device) may be quite different from someone who is sitting 500 feet from the central office, or someone who’s trying to take the output of a cable company’s VoIP adapter and pipe it over to the FXO card or device using twenty feet of copper wire. Just because the Sipura devices have worked better for us does not mean they will for you. I’m guessing that some people have purchased the exact same Sangoma device that we tried and were able to get it working well enough for their needs, but I just cannot recommend this device — at least not until Sangoma fixes the echo cancellation, and makes it read the incoming Caller ID reliably 100% of the time, preferably without having to change the incoming gain in DADHI or ZAPTEL.

EDIT: For more comments/opinions on this device (and on this review), see this thread on the PBX in a Flash forum.