Vodia Telephone System

Actually that action now happens in usr_index.js file. You can copy it from the chrome sources and drop in the html folder of the PBX working folder with the same exact name. Then any changes you make to it should show. Search for accinfo for your specific area that you want removed and much more. Thanks

It means: More button types are supported for Grandstream now, like Line, BLF, Speed Dial, Intercom, Voice Mail, LDAP Search etc. Different types of button sections in different models can now be programmed. The detail for the different button mapping and more is given in the updated buttons documentation: https://vodia.com/doc/buttons Thanks.

Yes that's the idea. The URL you give in the CDR setting, is what the PBX will access and the information. Thanks.

We added it recently and therefore have not yet added it in the documentation. It is basically only for Yealink phones. When Yealink does a call pickup on a BLF, it needs a star code to use, which goes in this field. Also in the button type drop down you will see a prefix as well. That is for Yealink too but for a different purpose. In that case the value you give it in parameter is what Yealink shows on the screen pressed and any other button or dialing after that is added to that prefix as a short cut.

Actually we integrated WAC in the page itself so when you say you can see the status of each phone (by the way that includes controlling the supported phones for pickup, hold, transfer etc.) that entity is WAC. Now when you login from a desktop, you see that and also are able to change settings of the extension. But when you login from a mobile you can only see the WAC functionality (or presence etc.), and also the WebRTP phone but you can't make extension changes right now. But we will change that soon (it's under testing), where we have changed the user portal completely and you will able to do the same on the mobile phone as you can on desktop right now. I hope it cleared it up for you a bit.

You mean the WAC on the mobile phone? Actually we will be changing the user portal completely which will allow users not only to use WAC but also access all other main settings as well. It is in the testing phase and once done will be released.

In the mean time what you can do is override some functionality of our JS files by putting a copy of the file by the same name in the the html folder. The pbx will then use the javascript file instead where you can make changes. Changes like posting the results of active calls to any server (since POST allows cross origins). This should help you for now. Thanks.

Yes, but that could create security problems. We will consider preparing a whole solution, maybe user based access with some authentication method but not just full access without question. Thanks.

I think this issue has been fixed on later versions. You could give the latest one a try which is version 5.4.0 but even 5.3.2a should have it. Thanks.

You could do it from the server itself and present it to the browser. So anything the browser wants to do with the PBX, it goes through your server (where it's the server that's talking to the PBX) and then return the value if any to the browser. Thanks.

Are you loading the javascript file from one server and the pbx is on another server? If so, that won't work because of different origins. These queries can only be sent to the server which provided the javascipt file. Thanks.

That is because it is not https. For app there is no way around it but a valid certificate. For the chrome browser however, it gives you the option to use https but skip the certificate part. One you have logged in with https, you can make calls.

Hmmm the app should not be doing that. I just tested and it works here. The URL is resolvable I assume. Don't use https, only http will work until the certificate problem is resolved. From the chrome you can use the https and using the advanced feature accept going to the page without a certificate. Once you are able to login, everything should work? What is it that doesn't work once you are able to login as https (without cert)? Thanks.

You are talking about the vodia app? Can you be more specific which part of it is not working? Or does it simply not come up? For the WebRTC calls https is needed now by chrome or webview but unfortunately if you don't have the certificate for the PBX the webview does not give you the option to enter anyway without certificate like the desktop chrome does. Long story short, we are trying to find a way how to provide people with the required certificate so they can use https and therefore WebRTC. Thanks.

Is it a public system so that you can maybe make a temporary account for me with a temporary password for testing here? Also, your chrome browser is the latest I assume?

Well it works here. I just tested it again. Are you sure its not the problem of connection and not WebRTC. What number are you calling, trunk or a local extension? Are you able to connect your normal phone with that number where it works?

You must also be on the latest PBX.

You have to use https. Chrome has stopped WebRTC support for http only pages. Even if it complains of the certificate, accept the connection anyway but use https so that WebRTC can work. Thanks.

Please use only chrome for these testing so we can be on the same page. What version of the PBX are you using? We have done some changes because the browsers had changed something and it is important that those changes are in. I would recommend the latest. Also make sure to use https and not http as chrome has stopped WebRTC for http only. I hope it helps.

Hi, The problem is that grandstream does not give the field numbers in sequence when the model changes and more keys are added. Having numbers as fields is strange anyway but that's how they have done it. So after the key 396, the next probably will not be starting with 397. I have tried to find out where the next sequence for the next 6 buttons should start but they don't make it easy. Maybe we will have to extract config from a phone. Once the next starting number is found then they would probably be in sequence for the 6 keys, e.g. if it starts with say 412, then it would be 412, 413, 414, 415, 416, 417. If you have model and can find that out, that would be your number in case you are in a hurry. We will of course be trying to find it and include it after testing. I hope it helps. Thanks.

Well as you may seen in the CDR documentation found here: https://vodia.com/documentation/cdr You can write to a file the cdr folder on your server. Now giving access to that file and folder through http (on another port than the pbx http) or ftp from that server is up to you. Unfortunately not at this point. That part has to be managed by the receiving server as to what is new. But if you going to store the CDRs on a separate server, it would be a good idea to have them deleted automatically the PBX after a certain time to keep them short like for 7 days or so or even daily. Well you will have to know the login and password of the admin as that is necessary to login and get the sessionid before you are able to use the sessionid in the method I mentioned above for cdr retrieval. I am not sure what you are asking for here but in general it is up to you how to want to store the CDR's. Whether as files, as a database, as files in database. As you can see in the link above, we provide all kinds of CDR delivery depending on what kind of server the user wants to use, including mongoDB. You can also use webcdr (or json, jsons) to deliver the cdr that can be put in an SQL database. A very simple PHP example of which has been provided on the link given above, which is a very simple one and just to show how it can be done. You can implement it any way you want. I hope that helps. Thanks.

There are two commands there: Get CDR count: {"action":"count-cdr-summary","start":0,"length":1000,"domain":true} And Get CDR records: {"action":"load-cdr-summary","start":0,"length":50,"domain":true,"user":"false","missed":"false"} The first one helps you determine how many there are. With the second one you can ask for any range. You can ask for all of them with length equal to the full count you got. I hope it helps.

Call cancel can't be done with a simple url. You will have to use websockets, in which case you must also receive the id of the call which you want to clear. OR You could use our CSTA API: https://vodia.com/documentation/csta_api.php Thanks.

Hmmm without the automatic selection it works here for me. We will try to test further with the version you mentioned for the phone in case that has a difference.

We will look into it. In the mean time, can you please manually select a button profile for that extension, instead of choosing automatic. Just choose the phone's button profile from the drop down and save it. Thanks.