Jump to content
Vodia PBX forum

All Activity

This stream auto-updates     

  1. Last week
  2. Support

    Transfer Button on User Portal not Working

    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.
  3. Hi, I am using Vodia 60 version. I am logged in on the pbx web portal via user interface as ext 200. There is a Yealink phone registered as extension 200, I see on user portal three buttons appear while call is connected, DISCONNECT, HOLD and TRANSFER. Disconnect and Hold are working but transfer does not. Please advise.
  4. A_nd_y

    Delayed ringing

    Thank you! With this file it works again
  5. Support

    Delayed ringing

    Hi, Use the attached ringtones.xml instead of the one on 60.0.3 and see if that makes a difference. ringtones.xml
  6. A_nd_y

    Delayed ringing

    Hi! In the meantime we have updated to 60.0.3. However, the delay is still present. And yes, we use Snom (870) phones. What else can we do to reduce the delay?
  7. Vodia PBX

    Large DECT Installations

    How about snom M-Series? They had fairly large installations with DECT.
  8. McFone

    Large DECT Installations

    Hi, the only solution we found is from Spectralink with the IP-DECT Server 6500, we will test it.
  9. Earlier
  10. Support

    Restore Backup

    Hi, Can you send that backup zip file to us in a private message and we will try to reproduce that issue here.
  11. Support

    Large DECT Installations

    Hi, We do support a Yealink W52P DECT phone. And also we can also manually register Snom M700, but the Yealink should be recommended.
  12. McFone

    Large DECT Installations

    Hello Community who has experience in large DECT installations together with the Vodia. The project will contain 240 DECT base stations with 300 DECT handsets. The positions of the DECT access points are already measured, which hardware on DECT is recommended for this which can provide something like this. Any idea thanks
  13. Vodia PBX

    BLF - NW BUTTONS V60.00

    Exactly. You can control it on per-group basis.
  14. Cld007

    BLF - NW BUTTONS V60.00

    Does that mean this change in 60.1 will allow a single BLF key that can pickup calls of a ringing extension regardless of if it is a direct call or a call to a hunt or agent group?
  15. Rameshkumar

    Restore Backup

    Hi, I am using Vodia 60.0.3 (Win64). I've a domain backup having around 12MB data and 300 accounts/users. When I restore that backup on 60.0.3 server it only shows me 200 accounts/users uploaded. When I restore the same backup on version 5.3.2 it works good. Please advise.
  16. Vodia PBX

    Doorphone internal dialplan only

    The pattern does not make any sense to me... If you want to get the last 3 digits after the prefix try !555198([0-9]{3}$)!\1!t!0 Dial plans answer the question on which trunk an outbound call should end up and what number to dial. There is no way to do additional things like enabling trunks.
  17. Hello, a customer has a door phone system on his old telephone system which is operated on an analog port. We want to use a Cisco SPA 122 as gateway and make the phone number DID available only for internal use. So that the extension number cannot be reached externally, we want to set the following in the routing of the SIPTRUNK, the "198" is the door intercom system. For inbound routing we wanted to use the following pattern !(5555555198$)!0!t!([0-9]{3}$)!\2!t!0 Routing: If incoming number 5555555198 then routing to 0 and for DID with 3 digits strip the last digits ANI if not found route all to 0 For the dial plan we want to set the following https://drive.google.com/file/d/14zRPJF4E7VmpD1get6k0JfE8NPBorFyo/view?usp=drivesdk It is not possible to deactivate the SIPTRUNK Ecotel in the dialplan or delete it after saving the entry is back again, how to delete or deactivate the trunk from the dialplan For a internal dial plan it is correctly entered with the pattern * and target 198 (ANI intern) The door opens when you enter the code #61 during a call, the Vodia sends it this way or we have to set something. We can also place DTMF codes on a button to open the door at the push of a button thanks
  18. Vodia PBX

    Adressbook

    Everything goes through the API, you can always take a look what the browser sends to the PBX after you press the import button and then do the same from your script. It is all REST.
  19. voltier

    Adressbook

    Hi there - we are wanting to provide an interface on our own portal which will allow the end customer to add/delete/manage the Address Book. Will there be any plans to have Address Book via your API?
  20. Vodia PBX

    Addressbook-speed dial

    Well 60.1 is a pretty good version, however not a "released" version (daily builds). dom_adrbook.htm should be still there... You can use the CSV import button to import in bulk.
  21. djanjic

    Addressbook-speed dial

    We upgraded to 60.1 hosted few days ago. I just noticed that address book under domain set up is gone. We have new client who wants to set up a large address book and put them on speed dial with *XXXX. I am wondering how to do this since address book is gone and there is not enough buttons on the phones?
  22. Vodia PBX

    can't set conference password v.58

    No we do release notes only for the "full" releases. We try to make them more stable than the in-between builds.
  23. beanyb

    can't set conference password v.58

    So while searching the forums for a fix I realized the software updates have decimal numbers which do not appear in the versioning of the releases. https://vodia.com/doc/releasenotes I updated to 58.4 and now the GUI works well. Is there any page that shows these decimal builds with their own release notes ?
  24. Vodia PBX

    CDR URL stops posting

    This is obviously not good... There were some situations where the PBX would not recover from HTTP client problems but in 60.0 they should be solved?
  25. jannies

    CDR URL stops posting

    We have been using the CDR URL to post json for quite some time and every now and then the posting stops working. This includes the action URL end points for "When a new call comes in" and "When a call connects to an agent" The log file shows that that requests are pending up and till it reaches 500 where it then starts to drop the webclient requests. [5] 2018/05/03 15:23:58: Action URL request http://xxxapi.xxx.co.za/api/CreateNewCall{ "id":"1326", "from":"\"xxxx\" <sip:8062@pbx.xxx.co.za>", "to":"\"xxx\" <sip:8028@pbx.xxx.co.za>", "callid":"5aeb0d7c222b-n3vc93jb8p6v", "domain":"pbx.xxx.co.za", "lang":"", "clip":"false", "extension":"8062", "trunk": "", "source": "[source}", "target": "8028" } [6] 2018/05/03 15:23:58: 500 more requests pending to xxxapi.xxx.co.za:80 [2] 2018/05/03 15:23:58: Too many webclient requests, dropping http://xxxapi.xxx.co.za:80/
  26. beanyb

    can't set conference password v.58

    Unfortunatley we cannot upgrade to v.60 until we iron out the changes that appeared after upgrading to v.58. We lost our ringing customization for Yealink phones that were not provisioned with Vodia but we opened a separate ticket for that and we'll try to work it through. I looked in the conference directory XML file and the new conference I created in v.58 has encrypted pins while the v.56 conferenced had clear text. Any way I can turn off PIN encryption in the xml files ? Thanks
  27. Support

    can't set conference password v.58

    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.
  1. Load more activity
×