Jump to content

Support

Administrators
  • Posts

    1,000
  • Joined

  • Last visited

Everything posted by Support

  1. You just need to have a provisioning phone for that extension account and set it to "desktop" mode on user portal and start making calls.
  2. Please check the logs on the admin level of the PBX. If the logs have "anonymous" or "unknown" , "hidden" etc. kind of caller-ID in it that means that PBX tried to hide the outgoing ID. But according to the laws that the trunk carrier follows, it may not be be allowing it from its your end.
  3. If you can set the ring time for his ext to be lesser than the time before his cell's VM gets hit, the call should move along ahead. Or you can add him as the last agent to be called if no one else picks up? Serves kind of managerial role as well?
  4. It's the time the agent was idle for.
  5. Unfortunately, nothing as of now. Only a few changes can be monitored from under the "/dom_ext3.htm" registration tab of the extensions.
  6. Can you please add an image of the issue here? Can you make sure you don't have any webpage customizations that are affecting this?
  7. Those icons are for "available for chatting" We do have red circle on the name if they're on a call. Blank if available via anything, user portal / app/ desktop phone etc. Actual status can be seen from under the registration tab as to what they're registered via. If the user is registered via an app and not via the desktop phone and adding a gray color for that can be confusing. We've kept it uniform, the colors are only for chat availability. For calls, if they're not on DND (DND symbol) or already in a call (red circle), they can be called.
  8. 401 are usually authentication requirements that is always seen in the logs. Could you paste the admin level logs for "trunk" set to level 9 and call messages on here? Do you have a dial plan set in the PBX and the Teams for it to go through? Teams dial plans takes hours to get working is what we've experienced numerous times on Teams side.
  9. This seems like a feature request at this time. We will update this thread if things change in the future.
  10. Can you make an outbound call using the wired headsets? Can you check if the web app / user portal has enough permission give to the wired headset? Do you face the same problem on a different laptop logging into the same user portal?
  11. If that is the case, please reset the certificates and also try to generate new LE certs for the domains that have expired certs on them. And recreate the cert by turning off and on of the ACME Let's encrypt (LE) setting.
  12. Support

    Code not found

    Is this the setting you're looking for?
  13. curl -u admin:pass -D - http://pbx/rest/domain/domain_name/user_settings/conf_id -X POST -d "{'pin':'2222', 'upin':'3333'}" Pin for moderator and upin for participant access code
  14. You always have to edit the URL manually in order to get to the links. http://portal.vodia.com/downloads/pbx/version-68.0.4.xml
  15. The default is always a value that the system "should do" generally speaking. For e.g in this case, it will be 1 because playing a message one time is enough generally for users.
  16. Support

    Code not found

    What are you looking to change exactly?
  17. That functionality has not been added yet for all the headphones / earphones out there in the market. Currently it's available for a particular Yealink headset. This is a feature request as of the moment.
  18. Have any of the above been tested with 68.0.4 version on the latest apps out there? There seems to be a significant improvement IMO.
  19. Is this the setting that you're referring to? Then you can see this on 68.0.4 version
  20. Can you send us these details and the admin login to your PBX via our ticketing system vodia.zammad.com and we can login and take a look?
  21. Have you tried adding the area code in the area code section on under domain settings and the rest stays the same?
  22. Can you try to login with a different account like outlook.live.com or similar ? Because we had the same error one of the accounts and we used a different account which just went through. This has to be tried because the logs on the PBX about this are limited given we don't handle the O365 account.
×
×
  • Create New...