Vodia PBX
-
Posts
11,110 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Vodia PBX
-
-
I assume you are using a global trunk. You can use for the "Destination for incoming calls" a list of expressions, e.g.
!.*!\1!123456789, where 123456789 would be your default number? -
For a system that is not busy, one core is enough.
-
2 hours ago, RichardDCG said:
This seems to indicate it is already a feature? If so how do I enable it?
Well it is on the status page, not the graphs (it is not supposed to change much during 24 hours).
-
4 GB RAM should be okay unless you plan to have huge amounts of CDR. In that case it would make sense to go for 8 GB. Also in you are using Windows, I would go for 8 GB anyway as Windows itself tends to be memory hungry. As for the CPU, 2 cores are perfect. However it would be great if the cores are dedicated and not shared with other VM, so that they can be responsive when RTP hits the server and the other VM is not currently trying to mine cryptocurrencies.
-
This will have nothing to do with SNMP. Did you check if the app has the permission to notify the user?
-
Well, running out of hard drive space is a major problem. We show the available space on the general status web page for a reason. The hard drive does not make a difference between CDR and actual configuration data, e.g. if writing the pbx.xml file fails the system will be in serious trouble after a restart. I would recommend to really make sure enough space is available, plus it is relatively cheap these days anyway.
-
If it does not connect then the port seems to be closed. You can see that e.g. with
netstat. It should obviously not happen. Maybe double check if the pbxctrl has the execute permission and the process is even running? You can always stop the service (e.g./etc/init.d/pbx stopor justps auxww|grep pbxctrland thenkill pid) and then start it manually (cd /usr/local/pbx; ./pbxctrl --no-daemon --log 9). Then you should see lots of error messages that should point to the problem. -
There seems to be an issue with SIP passwords that we are already investigating. It could be that they are actually not set (that would be a security feature), but obviously we need to have some way of overriding that. We'll definitely address this in 69.0.2.
-
Well please make sure that the pbxctrl.dat is the one from http://portal.vodia.com/downloads/pbx/dat/pbxctrl-68.0.24.dat. If it is a different version this will be a problem.
-
1 hour ago, RichardDCG said:
Can I reapply 68.0.24 via CLI?
If you have made a file system backup, it is actually very easy to revert to the previous version — just revert the file system. And if you have not made a backup, its a good time to do it now.
Yes the -old files are there to revert them back if the update fails. But you still need to be careful because there is guarantee that they match. You can use
./pbxctrl --versionto find out what the executable version is.You can overwrite the pbxctrl (pbxctrl.exe for Windows) and the pbxctrl.dat. Just make sure that the pbxctrl is executable (
chmod a+rx pbxctrl). The differences between 68.0.24 and 68.0.26 and very small and there should be no issue switching between those builds. -
Maybe the pbxctrl.dat file did not make it. You can easily copy this to the disk manually, the link is in http://portal.vodia.com/downloads/pbx/version-68.0.26.xml (e.g. wget http://portal.vodia.com/downloads/pbx/dat/pbxctrl-68.0.26.dat).
-
Hmm this is just another setting, it should behave like the others during the bulk update. Maybe is there a typo or something?
-
Well so far our understanding was that we forward the error code to the calling user-agent. The phone should display an appropriate message, probably on the display or, for example, play a busy tone when the call returned a 486 code.
That being said, looking at our own apps, there might be potential for better information to the user.
-
-
There are several possibilities. You can use ActionURL, but we have a new framework https://doc.vodia.com/docs/integrations-framework where this works much better for these things.
-
You can now start the PBX with
--admin-username nameand--admin-password password. -
We'll make a 69.0.2 soon.
-
If it cannot bind to port 80 or 443, there must be another process running on that port. Did you try
netstat -anpto see what is there? -
13 minutes ago, mskenderian said:
API: https://api.vodia.com/status_api no longer works.
The API documentation needs some TLC. The focus was on getting 69 out of the door, and we'll have to spend some time on explaining everything. For example, we have a beautiful article ready on passkeys that we will release in a few days.
-
On 1/9/2023 at 11:03 PM, RichardDCG said:
you cant use the windows app as a residential ext?
Oops yes that rules that option out.
-
As you might have seen in the newsletter, version 69.0.0 is available. It is a release with many new features. This is exciting and makes sure we are keeping up with the many changes that are currently happening in the commutations technology space.
After the release is before the release. We have already found a couple of smaller glitches in the new front end like from/to mixed up in missed chat message activity logs and we are already making daily builds with the name 69.0.1. Also, it seems that insecure login over HTTP causes problems with the latest Chrome browser which we are addressing.
Another common problem is that administrators cannot log in because the system management DNS address was set to some bogus address on many servers. Well — its written in the release notes but it seems it is easily overlooked...
We expect that it will take a few days and weeks until the dust has settled. We are working on making sure that everything is running smooth as soon as possible. If you find anything that should be corrected, please let use know, ideally in the form of a trouble ticket with steps that describe what the problem is and how to reproduce it.
Underneath, we have made some great improvements that will make the PBX even more rock solid. We are excited about this new release and want to make sure that administrators and users see that we arrived in the year 2023!
-
With the groups, we could build something around there block calls permission for the other extensions. Alternatively you could make the extension a residential extension and block internal calls, however obviously then the calls must be routed outside of the PBX as PSTN numbers.
-
Good point. Both WebRTC and VoIP phone registrations are actually interesting, so we'll need essentially to keep both of them separate.
-
On 12/30/2022 at 9:15 AM, Justin L said:
... to a KB ...
What is a KB?
Version 69
in Announcements
Posted
Ok we have made a new version 69.0.2, which should also include a Windows executable. The release notes have also been updated.
The front end is brand-new, yes the landing page is a little bit empty right now. We have already some partners filling the space with their own stuff; our plan is to put essentially the ACD stats there for the own extension (we want to fill the space with meaningful information). This would be expected for the next release number, which will be 69.0.4.