[WM: Still a work in progress. Stay tuned.]

[WM: By design, Wazo uses substantial computing resources because of its Asterisk RealTime implementation. We don’t believe it is well suited for Google’s free tier which limits RAM to .6 GB. If cost is a concern, we have had excellent results with the 2GB platform at HiFormance which offers $13/year pricing to Nerd Vittles readers.]

I have just one question. In my mailbox I have recorded my own greetings in my own language. But after my message, the "female robot" keeps on telling the caller which number they have called and to leave a message after the bib?

How do I disable this "kind" lady?

Best regards Kristian

[WM: Hi, Kristian. Please head over to the PIAF Forum or Wazo Forum and post this. Lots of terrific gurus to lend a hand. Glad everything is working well for you.]

Wazo seems nice and has a lot of potential. I like the potential of the WebRTC client, and have a few suggestions to minimize the friction of getting it set up.

First off, I set up Let’s Encrypt to get a legitimate certificate for my phone server, hoping that it would eliminate the certificate hoops that one has to jump through the first time connecting via RTC. Unfortunately, the UNICOM software as it’s currently written requires you to refer to your phone server by IP address and not it’s name, so the cert still doesn’t match.

Also, even though UNICOM is provided as SaaS, it is GPL3 software, and in my opinion, would be better deployed on my own phone server. I’ve started working on that as well, but haven’t made much progress yet. Ideally, it would be served from nginx just like the management interface, and be preprogrammed to connect to the APIs on the same server.

These few tweaks would allow anybody to set up a wazo server and be online from anywhere in the world just by visiting a webpage and entering their credentials.

[WM: Hi Victor, There is a simple upgrade procedure that only takes a couple minutes. Here’s the link.]

[WM: Thanks for the kind words, Jon. And your financial support is greatly appreciated as well. Good luck in the real estate business!]

[WM: That is, in fact, on the drawing board. 🙂 ]

[WM: Snapshots are embedded in the Incredible PBX for Wazo installer. You can review the source code if you’d like to use the snapshots independently of the installer or if you’d like to mimic the methodology.]

…didn’t realize till just then that the provided ISO links to the latest version which is 17.04.

Install of IncrediblePBX completed without errors, but told me ahead of time I’d have to configure everything manually. Upon logging in, nothing was configured (no trunks, etc.).

Any timeline for 17.04 support?

[WM: Finally out the door. Try again. Our apologies.]

[WM: Running a few days late this week. Sorry. All should be well now.]

[WM: Thanks for your work on this. Keep us posted on your progress, and we’ll be happy to publish your results.]

[WM: Sorry but we don’t support AWS for security and cost reasons. Take a look at OVH.com. You can’t beat $3.49/month, and the performance is terrific.]

[WM: If they are SIP-compatible devices, there shouldn’t be a problem. Do they work with Asterisk already?? If so, they should be fine.]

[WM: Free support is provided in the PIAF Forum. If you followed ALL the steps in our Vultr tutorial, the install completes successfully. We just retested it minutes ago without any problems.]

Thanks again for the wonderful tutorials.

[WM: Fixed in all of the tutorials. Here is the correct download link to the ISO. Thanks.]