Vodia PBX

There was a problem with the permissions — if you were logged in as admin and switch to the user mode it would work, but when doing that logged in as user it did not do it. That was supposed to be fixed in 67.0.1.

If you can control the code in the CRM system you could use the <pbxcall> tag mentioned in https://doc.vodia.com/docs/click2dial. The formatting of that page was broken with the migration from our previous documentation platform — we have to work in re-formatting it.

You can use something like 8201*2 to select the greeting "2". 8201 is the same like 8201*0.

For the Windows app, it would be great if you can proceed to version 67. There were a lot of changes in the area.

On which page is the time zone missing? What time zone?

What Android are you running? What model? Was this installed through the Google Play store?

iOS and Android run a completely different code base. iOS has CallKit which makes the whole VoIP app space a lot more enjoyable, Android has a completely different approach. Because only few users use both Android and iOS, having them look alike is usually not as important as functionality. What Android are you running? What model? Was this installed through the Google Play store?

Yes that's on the to-do list.

There was a problem with the Android app when using the headset for accepting calls. Bluetooth was actually working. We opened a ticket with Google and as it seems, the fix will be rolled out in a few days. This was affecting users on Android 11.

So the Android app is not starting automatically? That would indeed be a major problem! We are using mostly Google Pixel and Samsung for testing where this was not a topic so far.

I would not use E164, just NANPA (probably 11 digits). Most US- and Canada-based SIP trunk providers expect that form anyway.

There is a option the dial plan that tells the system how to present numbers into the pattern field ("Number presentation in dial plan"). If you select "For NANPA (10 digits)" the PBX will do all the work for you and present everything national with 10 digits. I would check for 011* first, then you don't have to deal with all the exceptions. BTW we have also patterns like [usa]xxxxxxx, which takes out Canada and potentially other expensive and hazardous area codes (only contintental USA). There is a another pattern called [fre] that contains all the free numbers (800 888 877 866 855 844 833). So you could use: 100 x11 110 011* 011* 120 [usa]xxxxxxx 130 [fre]xxxxxxx

Yes we had discussed that internally. It is a little bit counter intuitive to other applications running on the PC (close means end the application), but for VoIP the user expectation is that the application just goes out of sight. If the user really wants to end the application they will have to dig in some menu to make that happen.

Its now also available at the old location https://doc.vodia.com. There was a glitch with the certificate that seems to be resolved now.

Thanks, there is indeed a permission problem. We'll fix it in the next build.

Absolutely. It all comes down to "fetch". We are trying to get a test environment so that we can incorporate this.

You can also set things up manually. Click on the account title at the top of the app, this will open the settings (there you can also trigger another scan). iOS allows only secure connections to the PBX, which requires that the PBX has a valid certificate.

Yea, when you use the + in the MAC list field, you don't actually have to save it any more. Although it should not hurt either. Its important to make sure that the MAC is ready for pairing, which you can do below in the history tab (or in the extension list with the action dropdown). In the history tab, we have added a count-down timer where you can see how long the pairing is still on.

You can trigger sending a new email with the "try" (rocket) button. Then you don't have to wait for timeouts. If I remember correctly, the documentation includes description for gmail and Office 365, which are obviously very popular. E.g. for gmail, you have to explicitly allow SMTP. Or what email server are we talking about?

Yes that is somewhere on the list... If it's possible!

This is because the * matches only the part after the prefix. If you out 07* into the replacement it should work the way it should.

67 is mostly an evolution of version 66. With the increasing need to work from home, we made a few tweaks here and there to make that not only possible, but also more productive. One example is the ability to set the working hours not only on extension level, but also on domain level. This increases the user acceptance significantly. We have also added the possibility to use a second factor for the users to log in. Emails are a simple way for this, but where SMS is available, the PBX can now also send a message to the user's cell phone with the login code. Even if the user used a trivial password, this will significantly increase the security of the account. SMS is another area of activity. We have added more SMS providers, including a simple "GET" provider that can send SMS out. With additional scrutiny on the big chat providers for their privacy practices, SMS and especially MMS are seeing a revival, especially in the business world. Old school telecom providers don’t sell their users data. Another highlight is the ability to upload ringtones easily through the web interface, also on domain level. Even though this sounds like a small change, it does make a big difference for many partners that use the ring melody for tailoring their customers' experience. We have also made it possible to upload customers logos in PNG format; SVG looks better but many clients simply don’t have it. This again will help give businesses a better experience. We had also updated the apps in the app stores in between the release cycles. On the Microsoft store, we were able to list the Vodia app both on the Windows Store and in the Microsoft Store for Business. This is very useful for companies that want to control what apps users may install on their PC. If you are upgrading from version 66 this should be a smooth upgrade. Nevertheless, an upgrade is as always a great opportunity to make a backup of the working directory. Builds are available for CentOS64, Debian64, MIPS (Vodia IO), ARM( Vodia IOP), Windows64 and MacOS (Intel).

Ok we should keep UK and EN (which is en-US) separate and do this only for the UK. We can make this dependent on the audio language, its better than the web language because also in the UK most users actually use en-US. Starting in 67.0 you can just put this into the Yealink general parameter, it will override whatever is in the template so that there is no need to change the template for this.

The "enable call pickup from extension BLF" is making the BLF for the extension blink when the call comes in on that ACD. So you would put the extension on a key, not the ACD. If you put the ACD on a BLF button, the "enable call pickup extension BLF" has no effect for that button. At least that is how it should be. I am not sure if the login status makes a difference—its an interesting idea to limit the pickup possibility only to agents.

Do they support pulling from a REST API? Then you could take a look what the browser is pulling from the PBX and use the same API. Instead of using a session, you can use Basic authentication.