Jump to content
Vodia PBX forum

All Activity

This stream auto-updates     

  1. Today
  2. We are planning to release 64.0 today or at least in the next few days if anything goes wrong. So it might be worth waiting a little bit.
  3. oh okay.. I just followed the directions for the upgrade.. So, i will stay with the current version running until??? new notice, or until appears in the upgrade list of versions then? Like a 64.0 ?? Version Release Notes Date 63.0 https://doc.vodia.com/releasenotes630 7/12/2019 62.0 https://doc.vodia.com/releasenotes620 11/9/2018 61.0 https://doc.vodia.com/releasenotes610 7/13/2018 Thank You
  4. Obviously the opus.dll is missing. After all, this is not a release just a daily build. The opus.dll is not public available yet.
  5. Last week
  6. Hi The upgrade didnt worked, VodiaPBX could not start the service. I needed to rollback a copy of the full folder made before upgraded with the above file. In windows this is what the evern handler shows under application: Faulting application name: pbxctrl.exe, version: 0.0.0.0, time stamp: 0x5dcad419 Faulting module name: opus.dll, version: 6.3.9600.19478, time stamp: 0x5d6aa558 Exception code: 0xc0000135 Fault offset: 0x00000000000ecf30 Faulting process id: 0x4a8 Faulting application start time: 0x01d59962780d2ed1 Faulting application path: C:\Program Files\Vodia Networks\Vodia PBX\pbxctrl.exe Faulting module path: opus.dll Report Id: b5c344c3-0555-11ea-80d3-e919d057acdd Faulting package full name: Faulting package-relative application ID: And under system: Faulting application name: pbxctrl.exe, version: 0.0.0.0, time stamp: 0x5dcad419 Faulting module name: opus.dll, version: 6.3.9600.19478, time stamp: 0x5d6aa558 Exception code: 0xc0000135 Fault offset: 0x00000000000ecf30 Faulting process id: 0x4a8 Faulting application start time: 0x01d59962780d2ed1 Faulting application path: C:\Program Files\Vodia Networks\Vodia PBX\pbxctrl.exe Faulting module path: opus.dll Report Id: b5c344c3-0555-11ea-80d3-e919d057acdd Faulting package full name: Faulting package-relative application ID: I wont be able to give you the logs, since the current running system, is back as the previous one running OKAY Hope this helps.
  7. This needs to be placed there: http://portal.vodia.com/downloads/pbx/version-63.1.xml
  8. Hi again, Do i need to place the .DAT in here?: The .EXE gives me a 404 error. Software Update Please enter the URL for a software update XML file in the URL below. During the update and after that update you can continue using the system. Note that after the software update that updated the PBX software itself, you have to restart the PBX or schedule a reboot. Loading voice prompts do not require a restart of the PBX. URL: Save
  9. http://portal.vodia.com/downloads/pbx/dat/pbxctrl-63.1.5.dat http://portal.vodia.com/downloads/pbx/win64/pbxctrl-v63.1.5-64.exe
  10. Hi ! It wasnt the line given to me with the url. But the click on the 630.xml i press that sent the vodia to a prev. downgrade that seemed never allowed to recover from there ( as i said, i ended up corrupting it ) But its now working as the prev. day before that. I will try to apply the upgrade late tonite again. And keep you posted. But, if i want to manually download the .exe, wont find the page etc.. (or is it supposed to behave this way for security perhaps? not allowing external direct access?) Example: http://portal.vodia.com/downloads/pbx/win32/pbxctrl-v63.1-32.exe http://portal.vodia.com/downloads/pbx/win64/pbxctrl-v63.1-64.exe
  11. Not sure how the update ink would corrupt your system. It will either go through or it won't. Please let us know from the webclient Admin level 9 logs what error is it giving you when upgrading fails.
  12. Thank You, for the info. And how about the upgrade to 63.1 ? i havent been unable to achieve this either in fact, i ended up corrupting it, needing to restore the whole system to get it back to the prev. day. Any help, greatly appreciated.
  13. We simply don't have DNS-based whitelisting yet. Also not in the daily builds.
  14. I had to do a restore of the server, since the vodia process got corrupted someway.. Will wait for your directions after. Thank You
  15. Neither of this two files seems to be found either: <file name="pbxctrl.exe" type="executable" build="Apr 18 2019" os="Win32" hash="" link="http://portal.vodia.com/downloads/pbx/win32/pbxctrl-v63.1-32.exe" rename="pbxctrl-old"/> <file name="pbxctrl.exe" type="executable" build="Apr 18 2019" os="Win64" hash="" link="http://portal.vodia.com/downloads/pbx/win64/pbxctrl-v63.1-64.exe" rename="pbxctrl-old"/>
  16. Hi Im applying this to the maintenance, but only gives me: Software update failed. In a moment gave me 2 of 4 and then back to Software update failed. and keeps there. Im using this url instead of any from the list withing vodia: http://portal.vodia.com/downloads/pbx/version-63.1.xml I also tried: https://doc.vodia.com/releasenotes631 following pattern bellow. Version Release Notes Date 63.0 https://doc.vodia.com/releasenotes630 7/12/2019 62.0 https://doc.vodia.com/releasenotes620 11/9/2018 61.0 https://doc.vodia.com/releasenotes610 7/13/2018 Perhaps im doing something wrong? Should i manually download / rename files inside the folders? Thank You
  17. Download link: http://portal.vodia.com/downloads/pbx/version-63.1.xml
  18. If i go to vodia maintenance+software update, the most recent at the top of the list, is this one: 63.0 https://doc.vodia.com/releasenotes630 7/12/2019 Hope this helps
  19. Where can i find the latest version releases? I been looking in: https://doc.vodia.com/releasenotes630
  20. Hi I have: Software version 63.0.5 (Win64) Build date Aug 23 2019 20:16:51
  21. Which version of the PBX are you on? Because on the latest version (63.1) we've made the PBX lot smarter about this.
  22. Hi every single month when my customer IP changes, i need to manually add it to the firewall to be able to manage the registration of the device. Does this make sense for you? (I know the PBX of the clients (Grandstream) is behind a NAT) 166.172.190.139/32 Blocked (SIP/UDP) REGISTER 4300@sss.server.net 146 sec 166.172.190.139:46704 Enabled (SIP/UDP) REGISTER 4300@sss.server.net 18 sec I have set the maximun counts/numbers in settings under access in vodia, but nothing changes, vodia keeps blocking the registration, until i add the whitelist. I also suspect a bad password, but, is mostly unliked it. But i will check, soon i have access to customers PBX Meanwhile i posted it. Thank You
  23. Earlier
  24. Does the bot speak SIP? In that case it might just be a matter of using the SIP protocol to redirect the call to the right destination.
  25. Hello colleges, We develop bot for customer calling. This bot will be call to clients, react all answering machine messages and redirect to internal number when client will pick up the phone. 1. Can we integrate working of this bot to you software? Where can we find detailed information about that?
  26. Awesome ! will it require a PBX update or is it all ZoHo side with being published.
  27. When you import certificates make sure they are base64-encoded https://doc.vodia.com/admin_certs also note that the PBX can generate certificates using letsencrypt.
  1. Load more activity


  • Who's Online (See full list)

    There are no registered users currently online

×
×
  • Create New...