Yealink T46S Line / Appearance Keys

[MammerJammer]

Going through the Yealink GUI I have no trouble setting up any kind of key I want, however, when trying to configure the keys through Devices >> Keys provisioning I can't get any change. I was just interested in having a few appearance keys to allow the user to handle a second incoming call, but no matter what combination I try I can't get the additional appearance to pop.

Does anyone have a screenshot of their config or have any idea why the changes are taking effect?

 

[markjcrane]

I'm teaching how to do this November 12th (tomorrow) online in the Admin training. More details can be found here if you are interested. https://www.fusionpbx.com/training.php

Otherwise there are many models of the Yealink phones you should start by being specific to the version you are trying to configure. Next a screen shot to show what you are doing. Both of these would greatly help anyone that tries to respond to you.

 

[MammerJammer]

Mark, thanks for your reply. Is there a cost associated with the online training? When I visited the link above I only found information about a 3 day in-person Admin classroom training in Houston for $995.

As far as the model, the thread topic does say T46S. The actual model on the tag says SIP-T46S - is there something more specific you are referring to? In the two T46 attachments you can see the GUI config and the resulting output to the display on the phone. It works perfectly and does exactly what I want it to. The exception is I want to be able to achieve the same result using FusionPBX for centralized configuration management, not configuration at the endpoint level.

When I default the Dsskey config in the T46S GUI and attempt to push the same button config using FusionPBX the display never changes. I should mention that I'm using the T46S device template in the dropdown. You can see the instructions I was attempting to follow from the FusionPBX wiki after finding the key config a little lacking here: https://docs.fusionpbx.com/en/latest/accounts/devices.html

 

[MammerJammer]

I'm teaching how to do this November 12th (tomorrow) online in the Admin training. More details can be found here if you are interested. https://www.fusionpbx.com/training.php

Otherwise there are many models of the Yealink phones you should start by being specific to the version you are trying to configure. Next a screen shot to show what you are doing. Both of these would greatly help anyone that tries to respond to you.

Mark, I am sure you're tied up with your class, but maybe you can circle back around when you have a minute. I had an "Ah-Ha!" moment that made me ask a simple question - is this functionality strictly a component of auto-provisioning? How else could it work? It's not as if I've told FusionPBX the login credentials for the T46S, so it must be written to a provisioning/config file where the settings are waiting to be picked up by a correctly configured auto-provisioning device.

Or I'm wrong. lol.

 

[markjcrane]

Mark, I am sure you're tied up with your class, but maybe you can circle back around when you have a minute. I had an "Ah-Ha!" moment that made me ask a simple question - is this functionality strictly a component of auto-provisioning? How else could it work? It's not as if I've told FusionPBX the login credentials for the T46S, so it must be written to a provisioning/config file where the settings are waiting to be picked up by a correctly configured auto-provisioning device.

Sounds like you had a very good Ah-Ha moment. If you are not provisioning the phones then information in devices will sit there waiting for you to setup the phone to use provisioning. You can use DHCP option 66, other DHCP option, Yealink's RPS, manual configure it to use provisioning. More information on docs.fusionpbx.com search for Yealink or Provision or Devices.

 

[MammerJammer]

Sounds like you had a very good Ah-Ha moment. If you are not provisioning the phones then information in devices will sit there waiting for you to setup the phone to use provisioning. You can use DHCP option 66, other DHCP option, Yealink's RPS, manual configure it to use provisioning. More information on docs.fusionpbx.com search for Yealink or Provision or Devices.

I reached out to Yealink and got an RPS account set up. Do you have any documentation on configuring the endpoint >> RPS server >> FusionPBX relationship? I feel like I have been given a box with a fully disassembled clock inside it that I didnt take apart but now I need to put the parts back together. Sure, you know they work, but damn, where do you start? Yealink has config templates but no overview.

 

[bittygroom]

I reached out to Yealink and got an RPS account set up. Do you have any documentation on configuring the endpoint >> RPS server >> FusionPBX relationship? I feel like I have been given a box with a fully disassembled clock inside it that I didnt take apart but now I need to put the parts back together. Sure, you know they work, but damn, where do you start? Yealink has config templates but no overview.

Im new here and using yealink as well. did you ever get this working.

 

[MammerJammer]

Yes sir. Honestly, if you follow the Provisioning guide in the Wiki, its spot on.

Where are you stuck?

 

[bittygroom]

I will try the wiki. I cant get auto provisioning to work. I have tried everything in the docs to no avail

 

[MammerJammer]

Pay attention to this section. Line 1 was all that kept mine from working before asking for help. By default auto-provisioning is DISABLED.

Advanced > Default Settings
In the Provisioning section, there are a few key options that have to be set in order to turn auto provisioning on.

• enabled Must be enabled and set to value trueand enabled True. It is disabled by default.
• http_auth_username Must be enabled and set to value true and enabled True. It is disabled by default. Be sure to use a strong username.
• http_auth_password Must be enabled and set to value true and enabled True. It is disabled by default. Be sure to use a strong password.
• cidr Optional security option to allow configuration request limited to specific IP version 4 ranges. Type array allows multiple ranges of IP addresses.