Vodia Telephone System

I agree. We have a bunch of other things on our plate right now but it will be entered in the todo list. Thanks.

Right now it can recognize a number starting with + and any number in the format (xxx) xxx-xxxx. Later we would like more but what should be the formula to avoid other non-telephone numbers becoming links.

Is this problem solved for you?

Fixed. Should be there in the next version.

Thanks for your feedback. Yes we are working on some of these issues. Others are low priority, because we have to allocate resources and if some issues don't even register with most of our customers then they will get done last. For bulk extensions CSV is still the way to go. We had added a table where multiple extensions could be created but had to remove it because customers didn't like it. Call stuck has alluded us for a while. We are trying to recreate it consistently so that it can be fixed. Unfortunately it is very erratic and inconsistent and actually hardly ever happens in our test scenarios. We may have to build a bigger test scenario. Hmmm, you can't create trunks in Firefox. That's new to me, we will test and fix. No audio on calling from web interface is for WebRTC calls or the calls initiated by the phone through the web? Because both work perfectly here, I just tested it. Which version are you testing? Any logs? There is a migration path but we do suggest to back up everything (in case you need to go back), and there may be minor corrections needed after migration because a lot has changed since version 3. Other than that, it should not be a big problem. And our support will help you through the migration, once you decide to do so and call our support. Thanks.

The pbx is already ready. Just enter the MAC address of the phone into the extension which you want provisioned on the phone. Make the extension settings as you would like, e.g. name, buttons etc. Open MAC based provisioning for that extension. Just plug your phone and point it's provisioning server to the pbx (either manually in the phone's webpage or through DHCP option 66) and it will provision to that extension. The details are given here: http://vodia.com/documentation/pnp_grandstream Thanks.

With 2160, yes. We haven't tested it for 2124 but since it's the same series, I don't see any reason why it wouldn't work there as well.

We will look into it but it won't be quick. MS keeps changing the protocol as well, so its usually messy. For now, can you restart the pbx and see if the contacts disappear at least then.

- Contacts will not be deleted immediately but after the sync time (which you can set), does it still not refresh and delete the contacts? - There is no limit from our side, but of course resources like memory, etc. may limit it. - No, it is only user based at the moment. Thanks.

We will try to get one, add its provisioning and test it.

It shouldn't be but it is possible. Or maybe somehow it can't deal with a contact that is somehow incompatible with pbx, again it shouldn't be. Could you try it on another google test account with fewer test contacts?

I sent you an email regarding your test account. I tested it on the test account you provided and as you can see in the contacts list, the test contacts were successfully downloaded. I don't see why it would work on my test account and not yours, especially when it is done on your pbx with the test account which you set up.

Hmmm, is this pbx by any chance in public domain where we can access a test account (that you can create for us) for testing?

I just tried it and it works for me. I am sure you tried it the way it is mentioned but just to be sure. You gave your email address in the Email Address field, pressed "Get Auth Code", a new window opened where you logged in with the same email address you provided and its password, which takes you to the authentication page, then you pressed "Accept" button. The Auth Code appeared in that window which you copy and paste in the "Paste Auth Code Here" field and pressed "Login". Give it some time and the contacts will appear on the "Synced Contacts" page. Make sure there are some contacts set in your account. If it doesn't, try to repeat the process again with log set at max. so we can determine why it would work here and not there. Sometimes, the server is busy, it has to be repeated 2 times. Of course once it is done, then you don't have to do it again, it will keep sync every 15 minutes or so, unless you remove it or restart the pbx.

That happens when a language translation is not present. We will change it so it shows English in that case, but that still would not solve your problem of translated text unless you add your German translations. For that, the documentation is here: http://vodia.com/documentation/admin_translation Login in the German language. After you turn on the translation as shown in the document above, you have to go to a domain and then to an extension by clicking: "Click here to switch into user-mode" under the extension. Now since this is a dialog, the translations are on the language page. Click on "Language" in the user mode (remember translation is still on). Right click on any "undefined" you see. It will give you a hint as what it should translate. For example, sortby should be German translation of Sort by and so one. Provide the translation and click save. When you are finished, log out and the translations should be there. We will also get a copy for future use. Thanks.

Use only the drag and drop. Unfortunately the other option was only kept temporarily for now for backward compatibility and for people to be able to delete their previous images if they want. So just concentrate on the drag and drop. Do you save the image after to drag it to the box? It has to be saved once dragged in. This picture is the one that shows up in the chat with another person and also in presence etc.

It has been fixed and will be available in the next version 5.2.6, which should be very soon. Thanks.

The customized file will not have any hard-coded URL. The customized file is the one that provides the WebRTC functionality and dialer. This file is the one you can customize according to your needs for the dialer etc. The part that goes in customer webpage should be generated with the "GENERAL" link when you create a new trunk for that customer. That generated code will go in the customer webpage to access your customized usr_callbutton.htm to make calls to the pbx on that trunk. One trunk per customer, therefore one generated code per customer so that call comes into that trunk. And all of them are served your customized file for dial in. I hope it's clear.

Yes usr_callbutton.htm is that file but you can't access it directly. What you can try though is, create a file by that exact name in the html folder of the pbx working directory. And copy all the contents of that file from the browser into it. Once you are sure it works, from there on you can change it according to your needs. I hope that helps.

The phone admin and password are set from the provisioning settings on the domain. If empty, they will be generated by the pbx and you won't know them. So set it up as you want and provision the phone again so that it is fed to the phone. But note that it will be for all phones provisioned on that domain. The settings are at the bottom of the domain "General Settings" under "Provisioning Parameters".

Well you can use the expressions and headers in the incoming trunk routing to give a list of numbers allowed and redirecting others to say an IVR that gives a message and hangs up. Here are some related documents: http://vodia.com/documentation/trunk_inbound_routing http://vodia.com/documentation/trunk_custom_headers

Yes it is for Version 5.

Inter-Office Trunk Trunk may terminate calls for remote systems: YesNo Dial plan for outbound calls: Domain Default2ndExampleDial Out Please set the setting to Yes and select the dial plan to use for the outgoing call. That way, incoming calls will go out the selected trunk (through the dial plan), when the number isn't found in the PBX itself. However, make sure to take steps for security of calls, so that not anybody is allowed.

Regarding the button delete, I think Yealink does not delete an already provisioned button (not a helpful behavior from the phone but that's how it was in some versions). Could you instead try to change the button to empty or something else. But you could right, maybe the provisioning does not even reach the phone. The phone's log could help there, since the PBX is making the correct file to send but is the phone getting it and is it applying it correctly is the question here. Did you do a clean factory reset and provisioning to see if that reaches the phone?

Where as we haven't tested it on T48 but I think it should behave the same as T46G which we have tested and works great. Unfortunately if something is set in Yealink it won't change it with provisioning which needs a clean slate, so if these things are already set, can you please do a factory reset and provision again. Of course, I am sure you already know that you have to give the MAC address of the phone to a particular extension and open that extension for MAC based provisioning. Then restart the factory reset phone and it should provision. To double check, what went in, you can go to the "generated" folder in your working directory for that domain and extension and check the file (with the MAC of the phone) to see all the settings that were provisioned. I hope it helps solve or narrow the problem. You can send us that generated file if the problem isn't solved.