getmp3s

Would very much appreciate a Windows build for 68.0.37 please and thank you!

Anyone know if Fanvil X210-V2 button template was added to the 68.0.37 build, I'm desperately waiting on that? @Vodia PBX will there be a WINDOWS build of 68.0.37 or is this only coming to Linux?

Which 68.0.XX version includes support for the Fanvil X210-V2 phone please?

Hi is there an update to this? I'm using the web browser GUI i can't search anything beyond the first page. Using 68.0.30.

the X7 and i53w use 800x480 resolution, the way you have the template now it tries to push an 800x400 resolution wallpaper to the phone which is not accepted by the phone, so i just wrote in a manual IF model X7 or i53w and pushing my own bmp file hosted locally since I dont know the vodia generated bmp filename . I'd rather correct the template to use the vodia generated wallpaper if i knew it's filename.

yes thats correct, I want to add Fanvil phone models that use the 800x480 resolution image instead of the 800x400 resolution image, but I don't know what the bgimage filename is called. for example, for 800x400 the template calls for this file: "fanvil4.bmp" so i want to know what is the filename for the 800x480 picture since its not currently included in the fanvil-sysconf.xml file but its in the Logo upload section so we know Vodia built a framework to generate an 800x480 resolution image for Fanvil phones but just didn't include it in the sysconf file. Should be easy enough for me to add to the template if i know what the image filename is. Thanks.

Hi, in 68.0.28 the fanvil-sysconf.xml file is currently unable to correctly provision the 800x480 resolution background, on phones that use this resolution the template is currently trying to push the 800x400 resolution file called logo-fanvil3.bmp which is ignored by the phone since its the wrong resolution resolution. Vodia has a 800x480 resolution file that it is capable of generating, I have even uploaded a custom image under logos but its not called for in the sysconf.xml template so i can't access it. I would like to modify the sysconf.xml file so that I can correctly assign the 800x480 resolution logo to phones like the X7 and i53w which are currently trying to use logo-fanvil3.bmp. Could you tell me what is the generated file name for the 800x480 Fanvil logo so I can edit the xml accordingly so that my phones will pull the correct resolution wallpaper please? Thanks.

Thanks! that worked like a champ!

Thanks for the updates. We work heavily with the XU series phones such as X3U, X5U, X6U and X210/X210i so I've confirmed the ldap stopped working on all these models. Using latest Fanvil FW 2.4.5.2 and with TCP protocol. I could test the V series next week and let you know. As for software provisioning firmware updates, the current method Vodia is using for Fanvil devices doesn't work as your using the <fwcheck> method which only prompts the user on screen to update the FW. I rewrote my template to use the <ota> method which is true zero touch updating just like snom/yeakink etc.... And I pull the firmware files from here: http://download.fanvil.com/Firmware/Release/ but that's a whole different topic to the ldap one I'm hoping to get fixed.

Just upgraded to 68.0.24 and still no LDAP on Fanvil devices. Moved the Fanvil device back to a 68.0.14 server and LDAP works there using same provisioning file. How soon can this be fixed for us Fanvil folks?

Confirmed LDAP not working on Fanvil phones either on 68.0.22. cannot search either, it finds no records.

Fanvil X210 and X210i button syntax appears to be wrong in all 68.xx branches I've tested. You can configure the buttons on the sidecar portion of the phone fine, but not the 10 buttons that surround the main display. The X210 and X210i phones should be using the same button provisioning syntax as the XU series phones but Vodia is forcing an unrecognized tag called “SidekeyConfig” for the X210 and X210i buttons that are around the main display where the expected syntax is "Fkey index" which the same as what is being used for X5U, X6U phones. Fanvil just ignores anything with "SidekeyConfig" since its not relevant. This is preventing the buttons on the screen of the X210 from provisioning. Vodia is Configuring the screen buttons like this: <dssSide index="1"> <SidekeyConfig1 index="1"> <Type>2</Type> <Value>SIP1</Value> <Title>Outgoing Line</Title> <ICON>Green</ICON> </SidekeyConfig1> </dssSide> This is the correct configuration Syntax: <dssSide index="1"> <Fkey index="1"> <Type>2</Type> <Value>SIP1</Value> <Title>Outgoing Line</Title> <ICON>Green</ICON> </Fkey> </dssSide>

my 67.06 looks the same and behaves the same as @RichardDCG

Realizing that this is a WindowsApp thread and I'm asking about tenant branding in the WebApp which may or may not even be possible, it was in version 65 but is that something that has been depreciated now as I've not been able to reproduce specific tenant branding in the Web User Portal (using chrome browser) since version 65. The logo in the Web user portals seems to pull from the system not the tenant. Perhaps this is more of a feature request then: We would like the User Web Portal to pull logo from the tenant, not the system - in the same way the Windows App, Android/iOS App and Domain Portal do.

I think we are missing a step or not understanding how to upload the logo onto the PBX in the first place. On the domain admin logo upload page it says "the light theme logo will be used for the web interface" so just to clarify, this is where we put the logo that we want to appear on the USER PORTAL web page right? Assuming yes, then the behavior I'm noticing is that I can select a SVG file with dimensions 210x55 and preview the logo looks terrific in this window, i click SAVE and it appears to have saved, but if I refresh the page or navigate back to it, the preview is no longer displayed and all I see is the screen shot below with blank previews. Is this normal behavior that lgoo preview is no longer displayed when returning to this page or should it be showing me the logos currently applied?

Hi, since version 66 we have not been able to get custom logos back into the WEB user portal, it displays on domain admin, Android, iOS and Chrome Container apps great! But just not on the WEB user portal. We just upgraded to 67.02 but that did not help. what is the process to customize logo for the web portal - what could we be doing wrong if we upload the logo and it displays on the domain admin and apps but not web user portal? Thanks for your help.

Thanks - 2 questions: Q1: what is the min PBX version required for this build of the app? Q2: stated app version for Windows EXE is 3.5.3 within the app, (did fresh sandbox install of the link provided above) can you confirm if this is for sure version 4.0.1?

That's great. Looking forward to the download links.

how can i completely purge the old app from my computer and re-install. I've used add/remove programs to uninstall the app and then gone to the business store, linked my work account, purchased and re-installed the app and it still shows in the lower left hand corner running version 2.0.0 and my park button is shaded disabled which i was hoping the new version would fix. I think the windows store isn't actually upgrading my app but keeping it the same.

Hi Anton, could you post updated DL links for windows, Mac and Linux container apps. There are some fixes in the new version such as call parking I would like to test. Many thanks.

I am using the Android app and getting constant random alerts as shown in this screen shot saying they have a new voicemail that they sent themselves. (from their own extension to their extension) and yet no voicemail is there, its just a pop-up that can alert anytime, I'm using a Samsung S7 when it started and just upgraded today to a S20 and says the problem persists. I was able to reproduce this myself on my Samsung S10 by just installing the app, logging in and then sure enough about an hour later a random alert popped up saying i had sent myself a voicemail (i did not and there was no voicemails or calls of any type). This is new behavior since v4.0.8 update. Is it a settings issue perhaps? Will one of Android 10 OS notification settings disable this particular notification and still allow phone calls and actual voicemail notifications to come through? using PBX v66

Hi, I understand from the webinar some bug fixes are out in version 66.3 but there are no release notes - could we get some updates to the vodia doc release notes please so I can review for known and fixed issues. Thanks.

Hi Team; What are all the possible ways a user might be able to park a call within the latest Vodia App or Chrome browser user mode? If I roll back to app version 1 then I can use the "P" button within the app to park a call and at the bottom right there is an option to retrieve the parked call and this works on both incoming and outgoing calls. If i upgrade to any version in the 2.0 or 3.0 branch then the "P" button no longer functions like this and I can't figure out how its supposed to function. In the case of an incoming call, the "P" button can be selected and will either display the preferred park orbits in the window above, or if no preferred park orbits are defined then it will say "undefined". If you do get presented with a list of park orbits and you click one, it displays in the bottom right of the app or browser window that there is a call parked, but you cannot click on it to retrieve it. However you can dial the park orbit extension and it will retrieve - but then you can never park a call again until your next incoming call and the "P" option will become deactivated after its first use. In the case of an outgoing call, the "P" button is shaded out and not available to be pressed at all. I had also attempted a work around by trying to transfer a call into a park orbit as if I were transferring to another extension, but this will fail and call will be dropped. The text at the bottom of the screen that indicates a call is parked does not indicate what park orbit the call is parked on and since its not clickable text, the user will have to guess what parking extension to dial manually. Tested on platform Vodia PBX 66.0.1 multi-tenant hosted Chrome Browser 85.0.4183.102 , Windows Store App 3.0.1, MSI install App 3.2.0 At this time I can't figure out the way to park calls in the apps or browsers listed above unless downgrading user to MSI install App 1.1.0 and then the park button works perfectly and so does the parking retrieve functionality, but as there are notification issues with version 1.10 I'm trying to figure out how to make it work in the latest builds please.

The test environment I used to test the MSI above was within Windows Sandbox, when installing the 3.1.0 or 3.2.0 MSI it ends up saying 2.0.0 at the bottom as pictured above. So not sure this version is actually newer or older then whats on Windows Store. On my main operating computer i went to check what Windows Store has installed automatically for me after checking that all windows and store updates are applied and there are inconsistencies there too. For example, the windows store installed app reports 3.0.1 at the bottom, and device manager reports version 3.0.2 is installed and Windows Store "What's new in this version" page says the latest build is version 3.0.0. Anyway, they all work for me - its just impossible to know what version is actually in use for situations where we need to troubleshoot.

how come regardless of what version of the app you install, 3.1 or 3.2 it always says version 2.0.0 along the bottom left hand side of the window.