VitaminJ

Does that file exist inside the /usr/local/pbx folder? I can't seem to locate it.

Hi there, With regards to making changes to the home screen, would you be able to point me to the relevant template to customise? I know usr_portal.htm controls the general layout of the screen, and I've found the div element for the center section, however any code placed in this div is overwritten by whatever is displaying in the center section at the time. All the other User templates appear to be blank. (69.2)

Forgive me if I'm wrong, but I believe Ubuntu is a Debian-based linux distribution, so a Debian-based install script would work on Ubuntu, yes? It's installed in /usr/local/pbx, as defined in the install script from Installing in Linux (vodia.com) The firewall has been configured per Used Ports (vodia.com), but I fail to see how this would result in the content security policy blocking fonts being loaded by data:.

With regards to making changes to the home screen, would you be able to point me to the relevant template? I know usr_portal.htm controls the general layout of the screen, and I've found the div element for the center section, however any code placed in this div is overwritten by whatever is displaying in the center section at the time. All the other User templates appear to be blank. (69.2)

Can also confirm that tel: links are not working with 68.0.34 and app version 6.0.8.

Updated just now, and the same issue exists in 69.2. Have to add data: to any content security policy headers to resolve, per the error message in DevTools.

Fixed by adding data: to the Content-Security-Policy header for default-src in reg_head_css.html and welcome.html in Webpages (Administrator). reg_head_css.html: [[#header name="Content-Security-Policy" content="default-src 'self' data: ; style-src 'unsafe-inline' 'self'; frame-ancestors none"]] welcome.html: [[#header name="Content-Security-Policy" content="default-src 'self' data: https://accounts.google.com 'unsafe-inline'; child-src 'none'; frame-src https://accounts.google.com; frame-ancestors none"]]

Version: 69.1.4 OS: Ubuntu 18.04 Install method: Installing in Linux (vodia.com) using the Debian commands (with sudo ./install-debian.sh) The only steps taken to configure Vodia so far is to set the Administrator password and apply the licence. The custom fonts for menu items are failing to load, showing ▯ instead. Opening DevTools shows the following errors: I note there was a similar topic posted a few months ago for 69.0.8, however a permanent solution wasn't listed.

Internal calling has the same behaviour.

I've just tested on another iPhone (14 Pro Max), different extension/tenant but same PBX, and can confirm the same behaviour. EDIT: Same behaviour on our V69 staging server as well. Would appear to be the iOS app itself.

Would appear we didn't have all the information. Despite being asked about it previously, the user has admitted that she’s using a (wired) headset with her iPhone (just the standard earpods with lightning connector). If the headset is connected when answering a call, there’s no incoming audio, even if the headset gets disconnected/audio rerouted to speaker/handset. If the headset is disconnected when answering a call, the audio is fine, even when connecting the headset mid-call. Bizarre but we have a workaround.

Hi there! I've got a user who is having one-way audio issues with the Vodia iOS App. I've gathered call logs and PCAP traces, and as far as I'm able to determine, the issue lies in the iOS app selecting Opus/48000 as the codec, whilst the SIP trunk and the configured codecs for the extension are expecting PCMA/8000. Outgoing calls are unaffected. iPhone 14, iOS 16.2, App 1.24, PBX 68.0.26. I'm not able to locate anywhere in the iOS app that controls default codec selections. Extension (and the SIP trunk) are set per our provider's requirements, which is PCMA, G.729 and GSM in that order. At a bit of a loss and would appreciate any advice.

Not prepared to move to V69 in production at this stage. Will this functionality only be 69+?

This is a question that's been asked a few times in different forms; Is there a way to use the buttons on a Yealink WH6 series headset to answer calls in the Vodia App? I note there's a blog post about Vodia interoperability with these specific headsets - but I can't find a way to get the buttons working. Audio works fine as they're a Windows audio device. VODIA ANNOUNCES INTEROPERABILITY WITH THE YEALINK WH6 DECT WIRELESS HEADSET SERIES Can you shed some light on this?

Hi Michael, in the Windows app, if you go into Settings -> three dot menu -> Preferences and scroll to the bottom, you'll see the selection for the ringer device:

Thanks for this. Has resolved the issue.

PBX Version: 68.0.16 App Version: 4.0.1.0 (Microsoft Store) We've recently moved up to v68 from v67. Previously we had a "Calls in Domain" dialog in the bottom-right of the app window which is no longer visible in v68. A check in the HTM/CSS files shows this is simply hidden, however does not appear to work if brought back into view. What is necessary in order to make this work?

I've had a few users ask if devices such as the Jabra Busylight/Embrava Blynclight are supported with Vodia. https://www.jabra.com.au/accessories/jabra-busylight Embrava Products - Office Productivity Tools for Time Management in the workplace of the future I can see that both link in with a variety of voice apps but none explicitly support it. My question is, does Vodia support such devices, and if not, is such functionality planned? Embrava also provide an SDK for adding support - Embrava SDK for Windows, Mac and Linux | Embrava Developer Forum (proboards.com)

Microsoft have recently announced plans to retire the Store for Business in 2023, and have unveiled Windows Package Manager. Windows Package Manager | Microsoft Docs With the recent change to require a Microsoft account to install even free Store apps, it would be very handy (as someone that manages a fair few workstations with Vodia) if Vodia was submitted to the WinGet repository. Submit packages to Windows Package Manager | Microsoft Docs

Happily using the latest Store version of Vodia on Windows 11. I think I needed to reset the app when I upgraded from 10, but it's been faultless since.

Following. Have encountered this myself.

Bit of a bump but I've noticed that if you attempt to scan a QR code from Outlook while Outlook is in Dark Mode, Android devices won't scan and just return you to the login/scan QR page. Light mode Outlook scans first time, every time.

I'd be keen to test this out.

Any ideas?

Same with 67.0.5.