Jump to content

Support

Administrators
  • Posts

    1,000
  • Joined

  • Last visited

Everything posted by Support

  1. Hi, If you would like to completely customize it, you can also do that if you refer to this link https://vodia.com/doc/appearance
  2. Hi, Is there a way that you can upgrade to the 5.2.5 or better, to the latest 59.0 version. Because that could be a bug which was fixed on the later versions and upgrading would be the only solution to it.
  3. Unfortunately, as Admin mentioned, you would have to upgrade in order to achieve that.
  4. Hi, Did you give it a go by removing the "0015xxx" entry and keeping only the "805Exxx" ?
  5. Hi, Please let us know if this query is regarding our PBX? If yes, please be a little more detailed about your question.
  6. Hi, These are your domain recordings (dom_recordings.htm) entries. By deleting them, the PBX wont be able to access those files anymore even if they are occupying space on your server.
  7. If yealink bu default takes up the first button as a line key then yes developers must have made the button profiles smart enough to go around it.
  8. Hi, Is that all the logs that you could collect? No other logs were enlisted in the fresh new trail of the FAX sent? Also, WSAEWOULDBLOCK is not really an error but simply tells you that your send buffers are full. This can happen if you saturate the network or if the other side simply doesn't acknowledge the received data.
  9. Hi, Well in that case can you send us the admin level logs after giving the fax to email another try? Here are the log settings that you would have to set before doing this. Did you also edit / delete any of the certificates of the PBX?
  10. Hi, Apologies for the delayed response. We do have the FAX working on the latest 59.0 build, but please test it on your test system first before putting it on your production system. Just a precautionary measure.
  11. Looks like a feature request. We will try to check this off is the developers agree for this in the upcoming builds.
  12. Hi, Which page are you referring to? please make all the changes in the cURL command which caters to your PBX such as: Your domain / IP address (and port if any) of the PBX, your PBX login credentials, your user extension number etc. Those are simply examples for you to follow.
  13. Hi, If you are using "resolvable domain names" as your PBX and if you are keeping the same domain name on the newer server and if you are not using IP addresses anywhere for e.g in the outbound proxy of your provisioning settings (on the domain settings page) then you will have to reset all the phones and provision them again. So as long as you have used domain names everywhere you should be fine.
  14. Until it is officially released, it is hard to say. Stay tuned.
  15. Please check these links and modify your settings accordingly on the PBX. 1) https://vodia.com/doc/onewayaudio 2) https://vodia.com/doc/server_behind_nat 3) https://vodia.com/doc/admin_sip_and_audio
  16. Could you also let us know the HTM pages you are referring to? both working and non-working one?
  17. Hi, It will be glad if you could let us know on which version did you used to see this alert, as the latest (59.0) doesn't have it for now.
  18. Hi, Did you try to use these variables from the registration tab anyway? We are in middle of changing the documentation as well, maybe we will change this too.
  19. Hi, Is your chrome browser updated? Working internally should be the first thing that it should do. Please also involve your network operator in this scenario in the meanwhile.
  20. Hi, Yes we meant 59.1. But please only test that out on your test machine as there are a lot a improvements still to be done on this version. But the real power of the user portal can be seen there. Even includes graphical bar pie charts.
  21. Hi, Which version are you trying this on? There have been a lot of improvements on the 59.1 version for this.
  22. The ANI field from the specific trunk will be seen first by the PBX to be used as the outbound caller ID. If that field is not set then, there is the default ANI in the domain. Ultimately, the trunk header will grab the ANI. Try the "From-Header" field in the Hunt group after you have set the ANI. Hope this helps.
  23. Have you checked the "registration" tab under extensions? Is that you were referring to?
  24. Hi, Then that is a different issue. Your network has to be checked for that and this page https://vodia.com/doc/onewayaudio
  25. Did you try the option call pick up option from this link https://vodia.com/documentation/starcodes_transferringcalls ??
×
×
  • Create New...