Yealink Forums

Full Version: T28 & T26 with 3rd EXP39 - button 14 & 15 act weird
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
My customer recently had their phone system upgraded - from an Asterisk/FreePBX system to a newer Asterisk/FreePBX system. The old system was using the M1 configuration platform with TFTP. The new system is using the newer format with HTTP.

After the upgrade to the new configuration format, buttons 14 & 15 of the 3rd EXP39 don't act normal. They are configured as a "Transfer" button, but whenever button 14 is pressed, it mutes the phone. When button 15 is pressed, the caller is placed on hold and a new call is started on line 2. If we press "Transfer" then push the EXP button, it works as expected. This behavior also is seen when it's configured as a BLF key.

OLD CONFIG SNIPPET:

[ Key13 ]
Path = /config/vpPhone/Ext38_00000000000003.cfg
DKtype = 3
Line = 0
Value = 6549
type = blf
PickupValue = *8
Label = Human Resources

[ Key14 ]
Path = /config/vpPhone/Ext38_00000000000003.cfg
DKtype = 3
Line = 0
Value = 6407
type = blf
PickupValue = *8
Label = Marketing

NEW CONFIG SNIPPET:

expansion_module.3.key.13.label = Laundry
expansion_module.3.key.13.type = 3
expansion_module.3.key.13.value = 6404
expansion_module.3.key.14.label = Human Resources
expansion_module.3.key.14.type = 3
expansion_module.3.key.14.value = 6549
expansion_module.3.key.15.label = Marketing
expansion_module.3.key.15.type = 3
expansion_module.3.key.15.value = 6407
expansion_module.3.key.16.label = Nsg Staff
expansion_module.3.key.16.type = 3
expansion_module.3.key.16.value = 6439

The M1 format starts at Key0, where the new one starts at 1, so that's why it's 1 off. Buttons 13 & 16 are configured the same way and function as expected. I included them for reference only.

The original firmware of the phone was 2.60.0.120. I then upgraded it to 2.73.0.50 and all seemed fine until I received a report about those 2 buttons.

Since then I tried the following firmware on the phone: 2.73.0.50, 2.73.0.40, 2.72.0.80, 2.71.0.165, 2.70.0.150.

I then saw that the EXP39 had firmware, and I attempted to upgrade each of the 4 modules, one at a time. Each one was plugged in directly to the phone, and was the only expansion module installed during the upgrade process. I used firmware 2.60.0.101 on the T28P in order to upgrade the firmware on the expansion modules, according to the instructions at: http://support.yealink.com/documentFront...cumentId=6

Still, when I compared the firmware version of the modules to the 4 modules on the T26 that's also having the same issue, the firmware was identical:

EXP39 1 Hardware Version 32.0.0.0
EXP39 1 Firmware Version 5.16.0.0
EXP39 2 Hardware Version 32.0.0.0
EXP39 2 Firmware Version 5.16.0.0
EXP39 3 Hardware Version 32.0.0.0
EXP39 3 Firmware Version 5.16.0.0
EXP39 4 Hardware Version 32.0.0.0
EXP39 4 Firmware Version 5.16.0.0

This is the T28P:
Firmware Version 2.73.0.50
Hardware Version 1.0.0.39

This is the T26P:
Firmware Version 6.73.0.50
Hardware Version 4.0.0.38

I also opened the web interface to the T28 and saved the config manually, just to be sure nothing was missing from the pushed configuration. This didn't change it.

The T26 is doing the same thing. The only process I went through with that one was to manually change it from Transfer to BLF. Pressing the button while on a call still does the same thing.

I don't know what other troubleshooting steps should be done to isolate and fix the issue. Please advise. Thank you!
(04-30-2016 03:22 AM)sbsllc Wrote: [ -> ]My customer recently had their phone system upgraded - from an Asterisk/FreePBX system to a newer Asterisk/FreePBX system. The old system was using the M1 configuration platform with TFTP. The new system is using the newer format with HTTP.

After the upgrade to the new configuration format, buttons 14 & 15 of the 3rd EXP39 don't act normal. They are configured as a "Transfer" button, but whenever button 14 is pressed, it mutes the phone. When button 15 is pressed, the caller is placed on hold and a new call is started on line 2. If we press "Transfer" then push the EXP button, it works as expected. This behavior also is seen when it's configured as a BLF key.

OLD CONFIG SNIPPET:

[ Key13 ]
Path = /config/vpPhone/Ext38_00000000000003.cfg
DKtype = 3
Line = 0
Value = 6549
type = blf
PickupValue = *8
Label = Human Resources

[ Key14 ]
Path = /config/vpPhone/Ext38_00000000000003.cfg
DKtype = 3
Line = 0
Value = 6407
type = blf
PickupValue = *8
Label = Marketing

NEW CONFIG SNIPPET:

expansion_module.3.key.13.label = Laundry
expansion_module.3.key.13.type = 3
expansion_module.3.key.13.value = 6404
expansion_module.3.key.14.label = Human Resources
expansion_module.3.key.14.type = 3
expansion_module.3.key.14.value = 6549
expansion_module.3.key.15.label = Marketing
expansion_module.3.key.15.type = 3
expansion_module.3.key.15.value = 6407
expansion_module.3.key.16.label = Nsg Staff
expansion_module.3.key.16.type = 3
expansion_module.3.key.16.value = 6439

The M1 format starts at Key0, where the new one starts at 1, so that's why it's 1 off. Buttons 13 & 16 are configured the same way and function as expected. I included them for reference only.

The original firmware of the phone was 2.60.0.120. I then upgraded it to 2.73.0.50 and all seemed fine until I received a report about those 2 buttons.

Since then I tried the following firmware on the phone: 2.73.0.50, 2.73.0.40, 2.72.0.80, 2.71.0.165, 2.70.0.150.

I then saw that the EXP39 had firmware, and I attempted to upgrade each of the 4 modules, one at a time. Each one was plugged in directly to the phone, and was the only expansion module installed during the upgrade process. I used firmware 2.60.0.101 on the T28P in order to upgrade the firmware on the expansion modules, according to the instructions at: http://support.yealink.com/documentFront...cumentId=6

Still, when I compared the firmware version of the modules to the 4 modules on the T26 that's also having the same issue, the firmware was identical:

EXP39 1 Hardware Version 32.0.0.0
EXP39 1 Firmware Version 5.16.0.0
EXP39 2 Hardware Version 32.0.0.0
EXP39 2 Firmware Version 5.16.0.0
EXP39 3 Hardware Version 32.0.0.0
EXP39 3 Firmware Version 5.16.0.0
EXP39 4 Hardware Version 32.0.0.0
EXP39 4 Firmware Version 5.16.0.0

This is the T28P:
Firmware Version 2.73.0.50
Hardware Version 1.0.0.39

This is the T26P:
Firmware Version 6.73.0.50
Hardware Version 4.0.0.38

I also opened the web interface to the T28 and saved the config manually, just to be sure nothing was missing from the pushed configuration. This didn't change it.

The T26 is doing the same thing. The only process I went through with that one was to manually change it from Transfer to BLF. Pressing the button while on a call still does the same thing.

I don't know what other troubleshooting steps should be done to isolate and fix the issue. Please advise. Tragus!

Nice info!
Reference URL's