Support

What happens if it's not heard? Is it a blank no sound call or something else? Can you make sure the audio is in 8KHz, Mono, Wav, 16 bit format only? And then upload that audio again. It should worked, as it worked for us here.

It is tedious for sure, but it will work. The logic should work.

You would have to use this setting a little clever manner but it should work. Assign it on 8 extensions that those 8 extensions can call each other, but leave out the rest 2.

Hi, Maybe we spoke on the phone yesterday. Did you try to provision them with TCP/ UDP on the latest version of the firmware and the PBX (63.1)?

Maybe this works for you. You can use the hotdesk feature on the Yealink phone however there are few things you must do in order to get it to work, it's not rocket science...but needs preparations. This procedure basically prepares the phone as a burner phone where users can log in and out of the phone. Copy this into your yealink common file, I would recommend creating a new extension on the PBX however don't give it an actual extension #, just give it a name. The file should be copied under the (Customize) of the extension so you don't change the file in the admin level. ######################################################################################### Hotdesking ## #######################################################################################hotdesking.dsskey_register_name_enable =1hotdesking.dsskey_username_enable =1hotdesking.dsskey_password_enable =1hotdesking.dsskey_sip_server_enable =0hotdesking.dsskey_outbound_enable = 0In the same Yealink_common.txt file add this line under the syntax ({yealink-buttons}) and save. linekey.1.label = Loginlinekey.1.type = 34That's all we have to do on the common file. Next, on the extension create your buttons, however, on the first line key choose (Configure on the phone) then once you're done with the buttons, provision the phoneOnce provisioned your phone should look like this. When you press the login button you should see this message to clear the config press okNext page will ask you to enter the following value: register name, user name, and password The password is the SIP password of the extension Register: 412Username: 412 / MAC address (could also be mac address if the extension number doesn't work)Password:(SIP password of the account) Once the value is entered the phone will register with the assigned buttons, when the next person wants to log in, all they need to do is enter their credentials. Note: The buttons are static and will register once a new user logs in. Please check this video for more info. https://drive.google.com/open?id=1-JA3FhEoXO6IHJPZ8KiUuIztwmWNDcH3 Hope this is what you're looking for and it works for you.

Oh apologies. We thought you were on the latest version of the user portal. In the old one, this symbol is for DND. Also for the LDAP the entries should be in the right format (+1 and number format for US etc.) for the system to accept. Also sometimes caching can be issue as well on the browser, make sure addition of new entries is done on an incognito window. If the user portal takes it, then the phone should accept it too (ideally). But let us know if the user level address book issue still exists, we may have some more finishing touches to give it on that end, because we came up with whole new user portal now.

Meaning, it is only for "cancelling" that selection. It is not a third option as such. It's only an "exiting" cross from that selection, option. Was the LDAP working properly with these phones? What phone models are these? Once you set the address book for each of the levels (Domain+personal, Domain only, Personal only) it should show you only those on that physical extension. Maybe your LDAP is having issues. Make sure you have the LDAP ports set on /reg_ports.htm page on the PBX GUI and that is open on your firewall as well. Yealink and Snom (also maybe recently Polycoms) should support it fully (AFAWK).

Yes, that would only be for the user level. It's like having a personal contact on your cell phone. No, it is just to end that option from being selected. Click on the "X" and you'd see. Thanks for bringing this to our attention, but we are still working on sharpening and modifying all the details on the new user portal. They always have had the functionality to manage their own address book. What did they not have that you're referring to?

Hi, Yes we have some issues with the Emails on Zoiper currently, this thread will be updated with further instructions/ updates on it's fixes.

Thanks for bringing this to our attention. We will update this thread with more information about this ASAP.

You just told us that you are deploying this meaning you must have obviously tested this before telling us that you have this feature . We are legitimately trying to get developers involved here to make sure we can help you out with. Our team patiently talked back and forth on all the platforms you mentioned for more than 6 hours now but you don't seem to have a yealink tested for us to see how it actually works. As we mentioned before we are trying to understand this so that we can help create a new feature if we don't have it. There were 2 questions that we had asked before, if you can answer to both of them well and good, if not, fine!

1) So this is a whole Mitel system in short that you sent the video of? The phone + the PBX or whatever they call this? 2) Did you even test the Yealinks on this system? Can you hookup a Yealink phone and send us the working video of that?

Hi, Thanks for this. But it looks like a Mitel system with it's own phones. Can you send us the video with Yealinks that you said you have there too? Sorry to bother you with that, but Yealink will give us better idea.

Of-course it's something that can be done, but how it is done is what we're trying to see here. This looks like a classic case of dumbing down the phone which we don't do, hence the video and the screenshots of the process shall help.

Is there a way that you can send a very vivid video of all of this process? Including the buttons etc. so that we can wrap our heads around it? As we suppose that even the firmware on the phone has been modified for it.

Which phone, make and models are they having that uses this?

We don't have this video particularly focusing on the cloud, but maybe it'll help (if you haven't seen it already) :

For the intermediate builds (which don't end in "0") do not have release notes, as they are under testing (but are completely stable).

So the next step is that you have to make an account on vodia.com if you don't already and then get a new license from here: https://portal.vodia.com/en/cpelic

After downloading the software did you go to the license page and accept the license agreement?

Hi, 1) So this platform is for everywhere (Laptops and phones) except for iOS. 2) Hmm we understand that, but these are the only 2 readily available options that we have. Rest everything will go under feature request for now. How about you have those desktop phones in place, but you may or may not use them as much as you use these features? Win win?

OK, there's one more solution, maybe they won't destroy this one. How about they use our new and latest user portal and / or our Android app and this whole problem goes away? They can make and receive calls via a laptop or google chrome or our android app itself and you won't even have to buy desktop phones anymore, so no damage. And you can control the user portal from your end. Just create new web passwords or delete them for the new user, joining or leaving respectively. We just launched the app yesterday with the latest user portal.

You're right, but also, how often will that happen? Atleast you don't have to wait for some feature to be added and you can get this client going right now.

This will be a one time job. Unfortunately, this is the only solution we have for now.

Yes 63.0.5 should be the latest for it. If you're box is for testing, you can also try out 63.1. But it's STRICTLY for testing right now.