Jump to content

anton

Members
  • Posts

    84
  • Joined

  • Last visited

Everything posted by anton

  1. Found the issue. Should be a relatively easy fix. Will update you when the next build is available
  2. That setting already exists. In Android app go to Settings -> Call forwarding -> Disable device types Which has the same 3 options as the iOS app.
  3. It was a bug within the PDF processing library. Once the build is ready we'll update this thread with the build version
  4. Hi Chuck, are you running the latest version of the Windows app (settings->apps->apps & features-> advanced options)? And what's your PBX version?
  5. Thank you for the info. We'll look into this
  6. We are yet to run compatibility test for Windows 11. Will keep you posted.
  7. We have this feature implemented for the macOS app and already working on adding to the Windows app too.
  8. Please check the app version on the OS level. Version on the bottom left is for the UI.
  9. The Windows app version can be checked on the OS level. What you see on the bottom left is pretty much referred to the UI version.
  10. macOS app is now available at the App Store:https://apps.apple.com/de/app/vodia-phone-desktop/id1559550570
  11. We do have an option for our customers to write their own JS/HTML/CSS combo for the user portal. In terms of customization this is the ultimate solution which has no limits of what can be achieved. You can write a small snippet, or a whole new section for the home/main view of the user portal. And the best part - it will be applied to both Web browser and all the Desktop apps
  12. In the windows app/ browser simply click on the missed call in Calls view and it will be labeled as seen. Same goes for vm.
  13. We have a dedicate thread for this already, check it out:
  14. Settings -> 3 dots -> Preferences
  15. Hi, here you go: http://portal.vodia.com/downloads/app/win/VodiaPhone-4.0.1.msi
  16. Version 4.0.0/1: macOS: http://portal.vodia.com/downloads/app/mac/VodiaPhone-4.0.0.dmg Linux - http://portal.vodia.com/downloads/app/lin/VodiaPhone-4.0.0.AppImage Windows .exe - http://portal.vodia.com/downloads/app/win/VodiaPhone-4.0.1.exe
  17. Please update one more time! Starting this version of the app the version you see at the bottom left corner is no longer relevant and will be phased out. The reason for that is we've introduced a new mechanism that matches the version of the PBX to user portal to allow for a better compatibly. Meaning there's no need to worry about having any compatibility issues between PBX and the app, and by simply updating PBX the user portal (web & app) will be updated as well.
  18. We are working on the new version. It's in the test stage right now.
  19. Please uninstall and install the app again. It should be back to stable 3.5.5 version
  20. This has been already added and will be available with the coming 68 release. In a meantime, if you are interested, we can provide you with the custom code template to have that option available to all the user before the official release.
  21. This has already been fixed and will be added to the 68 release.
  22. Hi Enzo, The Windows app update got already rolled back to 3.5.5. Reinstalling the app solves the issue.
  23. What's your PBX version? There are 2 .css files that can be used to stylistically change user interface depending for users those changes are intended: For regular users only: css/agent-portal.css For all users including ACD managers and Admins: css/user_portal_custom.css There's also a matter if you are running a multi-domain system, to affect all the domain those modifications can be carried on the admin level, or for each domain independently within each domain settings. And of course those changes will be applied to both webrtc and Windows app users. Add those lines to either .css files mentioned above and you should be all set, and don't forget there could potentially be caching issue: #live-calls-block{ display: none; } /*My calls window*/ #my-calls-block{ height: 100% !important; }
  24. If you go to the user portal from your browser, in incognito mode, does it have the same issue? Because I'm thinking it could be a simple caching issue.
×
×
  • Create New...