Jump to content

Support

Administrators
  • Posts

    1,000
  • Joined

  • Last visited

Everything posted by Support

  1. Hi, Can you turn on the Admin level 9 logs for webserver and webclient only and do the update without the reboot and send us the logs. Please beware, that you will lose all the buttons and the MAC addresses once you upgrade from 56.0 to 60.0. So take a backup before doing this.
  2. Unfortunately, that cannot happen by keeping the cell phone attached to the first extension as there is no need for that cell phone to hear anyone else's personal greetings and possibly change them if it is not a part of that ext.
  3. Hi, Wouldn't that completely flood your inbox? or an Admin's inbox in case of an agent, in an agent group doing that?
  4. Hi, That would be a pretty cool feature to have. We might have to put it in our bucket list if possible.
  5. The folders you should keep cleaning and wiping off (if not needed after a certain point) are: 1) CDR - All CDR* folders in the directory ( cdre, cdrt, cdri and cdr). 2) PCAP folder. 3) Recordings folder. These should be mainly the most important hard drive space occupying folders.
  6. Hi, Login via that user who is the manager (assign that user a queue manager in the ACD settings) of that ACD.
  7. Hi, The version on 60.1 works fine. But it is still in the testing phase. So please hold on until the stable version is rolled out. If you want to test it out, then you can upgrade to 60.1 and test this for yourself.
  8. Hi, Use the attached ringtones.xml instead of the one on 60.0.3 and see if that makes a difference. ringtones.xml
  9. Hi, Can you send that backup zip file to us in a private message and we will try to reproduce that issue here.
  10. Hi, We do support a Yealink W52P DECT phone. And also we can also manually register Snom M700, but the Yealink should be recommended.
  11. Hi, We tested this on our latest 60.0 version and everything seemed to work fine. Please picture attached. Make sure you are not using the password codes that you have used previously anywhere (no matter if it's a new ad-hoc conference, it's just a security measure). If that still doesn't go through, then try upgrading to 60.0 and the issue might disappear. P.S: Do make sure you give us a call before upgrading to 60.0.
  12. Hi, Did you check your dial plans and trunks if they are working as they were previously?
  13. Hi, Unfortunately this would be a little out of our reach to develop an API at this point. After discussion with our team, we have concluded that going with only CSTA will be the best option for you.
  14. Hi, It will be released on 60.0.3. If you want to upgrade to this version before the official version is released then you can follow these steps: 1) Download the 'pbxctrl' from this link http://vodia.com/downloads/pbx/centos64/pbxctrl-centos64-60.0.3 2) replace the 'pbxctrl' in the /usr/local/pbx folder with the 'pbxctrl' from the downloaded file. 3) Reboot.
  15. Hi Norris, Yes for now those are the only buttons that we have on the latest build for now. As we spoke earlier, they may have to get new extensions for the phones. For buttons, we will create an updated page shortly.
  16. Hi, But please give us a call before you upgrade to 60.0.
  17. Hi, Did you check out this link https://vodia.com/documentation/csta_api_example ?
  18. Hi, So you are looking for a Blind call to be transferred? Did you try our REST API yet https://vodia.com/pbxapi/index.php? If you dont find what you are looking for, then give us a call or maybe describe here what you are looking for and we can try to add it if it's possible (scenario wise).
  19. Hi, Which phone is 41bis? Also, BLIND transfer should work fine. If it had been just one phone in picture here then you can try that the Blind transfer works fine. If you try to blind transfer from 41bis first (and if it doesn't work) and if you try again from 41 does it give you the same issue again? If yes, then the cancel is not being sent from both the phones at the same time (because they aren't in sync with each other) and hence yes double registration might be the issue.
  20. Yes. But before that, try turning the DISA feature off on that domain's settings page and give it a try. We don't know your use case but if it works then well and good.
  21. Hi, Use either of these (choice depends on how your trunk takes it) settings to NOT show the original caller ID and just show from where the call have generated.
  22. Hi, Give us a call and we can discuss this further. +1-617-446-1399
  23. Slightly, not much. But we gave you the exact one you need.
  24. Hi, The procedure we provided above is from the latest version 60.0.1. Did you follow the steps 2 and 3 exactly as it's shown? We also tried to "append" the outputs of the pbx.xml before and after restart and can clearly see the difference ( password visible) in the latter part of the file. Please test the API command above again, it has been edited to suit you better.
  25. Hi, The settings at the bottom of the page mentions that restart is required if you change any of those settings on the page reg_settings.htm There is one more build from March 12th, but we don't see how that will make a difference.
×
×
  • Create New...