Support
-
Posts
1,000 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Support
-
-
Hi,
Alright, your requests are justified and as you know this might take a while to go over and give it a re-finishing touch. Thanks a lot for your feedback though. We really appreciate it.
-
Hi,
Thank you taking time for writing this feedback.
1 hour ago, ahennis@voicespring.net said:A very simple example we can look at all servers and all domains to pull lists for automated service flags that have holidays set and verify with the customers what holiday settings are needed for the up coming year. Since there is no mechanism in a service flag to handle floating holidays like Thanks Giving and Labor day, they need to be changed each year. Now we can produce a list of domains and service flags quickly to review with the customers. This will prevent the problem of service flags being set for the incorrect holiday each year.
Do you mean the PBX should detect the bank holidays by itself and auto assign them to for e.g. service flags every year right?
1 hour ago, ahennis@voicespring.net said:It would be useful to have descriptions of the data returned or being set. For example in the Service Flag REST calls returns data like mon: "00:00-8:AM 20:30-9:AM" which is clearly the hours for the service flag on Monday. There are also things like param1 and param2. What do these things do?
Also, yes description is also being noted down. Makes sense.
1 hour ago, ahennis@voicespring.net said:It would also be useful to query the config templates for each domain and each phone in the domain if that phone has its' own config template.
You would like to do that from domain and extension level respectively right?
-
Hello Contributors and Followers,
We are thankful for all the contributions and suggestion received from you over all our product versions and branches of it. We would like to gain a quick feedback from anyone and everyone who are using our APIs for their automation requirements with Vodia PBX 58.0 and above.
Here is our API documentation page https://vodia.com/pbxapi . Although there is a lot of CSS and beautification needed (which we agree), we would like to have a feedback from you about:-
1) If any document which you regularly use, is missing.
2) If anything is incorrect.
3) If you would like us to add extra documents which you think might be cool (if you have seen it on some other website, which you regularly use etc.). Just let us know which APIs are the ones you use on a daily basis and would like to give it a try from Vodia's end point as well.
4) Criticism is welcomed too.
-
Thanks !
-
Hi,
That is a work in progress. For now, minimize your screen and then you can see the whole page. API page for service flags is here:- https://vodia.com/pbxapi/service_flags_api
-
The documentation will be available soon. This thread will be updated once done.
-
Hi,
We will notify this thread once the new version is out.
-
Hi,
May be this will help https://vodia.com/pbxapi/certificates_api
Make sure you are on the version 58.0 and above for using this API.
-
Hi,
Won't the dial plans be the best option for this scenario for you? Please check this link out https://vodia.com/doc/domain_dialplans#Parts_of_a_Dial_Plan
-
We are in the middle of changing the whole functionalities on the PBX end, so it's too soon for us (support) to comment how it will turn out in the upcoming builds.
-
Hi,
We have made the PBX smarter starting with this version and now the PBX auto-detects the phone that has been provisioned to it and then you can go to the button profile of that extension and make the button changes from there.
-
Hi,
Please put the ANI you want to be displayed on the Domain settings and give it a try. And please upgrade to 59.1 as it has various bug fixes compared to the previous versions.
-
Hi,
You can always remove the page that we have and set it to a blank screen, which will essentially give you the same look. Customizing it to look like the old logon page will involve unnecessary overhead for your web development team.
-
Hi,
The latest build doesn't address this, Admin meant in the upcoming build after 59.1, hence 59.1+. Which version did you try?
-
Hi,
We have had the snom D745 template added since 5.5 version https://vodia.com/documentation/releasenotes550. Which version are you on?
-
Hi,
There have been a lot of changes lately on the latest 59.1 version on the PBX and the user portals end as well. Please give the upgraded version a try.
-
Hi,
Are you referring to a variable "cw_enable" on dom_ext.htm page? Did you add this variable as this doesn't exist in the default template file.
-
Hi,
These are the default settings that the extensions are born with. If you find it tedious to turn it off on all the extensions you are making then you can always use APIs (https://vodia.com/pbxapi/extensions_api ctrl + F for the variable "cw" )and automate them to turn them off on every new extensions you create. But this is more of a work than manually turning it off once the extension is created.
-
Hi,
We are aware about the FAX issues on the latest version. And we have fixed it on the latest build (still in build phase for windows). Once it is out, it will be announced ASAP.
-
Hi,
I believe that this is what you are looking for:- https://technet.microsoft.com/en-us/library/mt605227.aspx
So, as of now we don't support it. All we support is Trunking with different vendors.
But, if you are a promising customer of Vodia PBX, then we here at Vodia can build up a new version for you.
Let us know more about your plans of business with Vodia PBX.
-
18 minutes ago, cwernstedt said:
@Support The logs seem to be gone quite quickly and not much helpful info in them right after the problem happened either. I had SIP events logging set to a high number and these events quickly filled the 100 entry limit that was also set. I did receive some notification emails from the system about RTP timeout and "unconnected call" with regard to some WebRTC tests that I did, but currently this is all I have (unless more logs are stored somewhere in the pbx folder).
So I think I'll have to wait until next time this happens (if it happens).
However, I wonder if you could clarify what optimal log settings would be in order to capture these problems the next time. I need to increase logging detail and the number of entries saves, but I don't know what is reasonable, and I don't want to run into memory issues due to excessive logging.
Hi,
You wont run into any memory issues due to logs as they get overwritten once the limit is crossed. And these are logs you need to get us from the Admin level (as seen in the image as well).
Also do get us the "lsof" commands output here. Please follow the link attached previously to learn more about lsof and how to fire the command from the terminal.
-
Hi,
Which firmware are you using on the phone? It's highly possible that firmware of the phone has a huge role to play in this more than the PBX. If you can reproduce this and send us an Admin level logs for this one, that will help (see image - these logs we need). Which PBX version are you on?
-
Hi,
Could you get us the logs of those failed calls from the admin level for us to quickly see what is going on. Did anything else change on your trunk or system except upgrading to the version 59.0?
Also, if you can test it out real quick, then can you try to upgrade to 59.1 and see if the issues are fixed.
P.S.: Please take a full backup of your /usr/local/pbx folder before upgrading. And test this when you have the lowest or no business running.
-
Hi,
Also give http://Pbx_IP/rawlogin.htm a try before doing the above procedure. Hopefully it should work.
Newly developed REST API on Vodia PBX 58.0 and above.
in Customer Research
Posted
Absolutely. Thanks again.