› VitalPBX Community Support › General Discussion › Endpoint Manager Yealink Expansion Module bug
- This topic has 11 replies, 3 voices, and was last updated 1 year, 11 months ago by
toxicfusion.
- Post
-
- June 13, 2018 at 3:43 pm
There is currently no way to assign the button Type on the Yealink Expansion Module, the pull down menu for the Type is not working so the following field is left out “expansion_module.1.key.1.type = XX” making it inoperative.
The other fields are working properly below
expansion_module.1.key.1.label = test
expansion_module.1.key.1.line = 1
expansion_module.1.key.1.value = 100
- Replies
-
- June 13, 2018 at 3:45 pm
- June 13, 2018 at 3:53 pm
- June 13, 2018 at 4:12 pm
Looks like its just in the V81 for Yealink T46s and T48s
As a workaroung I have been placing a file y000000000066.cfg in the /usr/share/ombutel/ww/includes/xepm/provision/ directory with the following parameters that are missing from the module for the wallpaper and addon buttons
#!version:1.0.0.1
##File header “#!version:1.0.0.1” can not be edited or deleted, and must be placed in the first line.##
wallpaper_upload.url = http://10.1.1.5/xepm-provision/wallpaper.jpg
phone_setting.backgrounds = Config:wallpaper.jpg
expansion_module.1.key.1.line = 1
expansion_module.1.key.1.type = 16
expansion_module.1.key.1.value = 101
expansion_module.1.key.1.extension = **
expansion_module.1.key.1.label = Billexpansion_module.1.key.2.line = 1
expansion_module.1.key.2.type = 16
expansion_module.1.key.2.value = 102
expansion_module.1.key.2.extension = **
expansion_module.1.key.2.label = Taylorexpansion_module.1.key.3.line = 1
expansion_module.1.key.3.type = 16
expansion_module.1.key.3.value = 103
expansion_module.1.key.3.extension = **
expansion_module.1.key.3.label = ITexpansion_module.1.key.4.line = 1
expansion_module.1.key.4.type = 16
expansion_module.1.key.4.value = 105
expansion_module.1.key.4.extension = **
expansion_module.1.key.4.label = Floral0- February 11, 2019 at 3:16 am
- February 11, 2019 at 4:57 pm
Create a file for the firmware each level of phone you are using for example y000000000066.cfg
Place this file in the /usr/share/obmbutel/www/includes/xepm/provision/ directory
The file should contain this and any other functions you want to apply to all of the phones with that firmware level, only one file is needed for all of the phones of that type
#!version:1.0.0.1
##File header “#!version:1.0.0.1” can not be edited or deleted, and must be placed in the first line.##
wallpaper_upload.url = http://your-server-ip/wallpaper.jpg
phone_setting.backgrounds = Config:wallpaper.jpg
Then copy your wallpaper.jpg file to the directory /usr/share/ombutel/wwww/
0- February 12, 2019 at 2:00 am
- February 12, 2019 at 2:30 pm
Yealink uses a config file for autoprovisioning each firmware level has a different number added to the end of the file y0000000000xx.cfg
For example the T48G would be y000000000028.cfg
The T46S version would be y000000000066.cfg
You can see the firmware level by pressing the OK button on the phone when it is idle
Example T46S phone firmware 66.82.0.20 uses the first digits 66 so y000000000066.cfg would be the file name for the T46S
Pay attention to the S or G versions they are different, there is a partial list ( below )
VitalPBX does not use these firmware files in their endpoint manager, they use the
macaddress.cfg Example 805EC0242220.cfg
When your phone boots and looks for its provisioning files it will look for the
firmware file y000000000066.cfg then the mac file 805EC0242220.cfg (example)
Any parameters that vitalpbx is missing can be added to the firmware file because the phone will read from both
T2 Series
2 – T28P
6 – T26P
7 – T22P
34 – T21P
9 – T20P
31 – T19PT3 Series
38 -T38G
32 – T32GT4 Series
35 – T48G
28 – T46G
29 – T42G
36 – T41P0- February 13, 2019 at 3:49 pm
- February 13, 2019 at 4:28 pm
Works for both on site and cloud, you can set up an option 66 in your local router for the address of your server “http://your-server-ip/xepm/provision/”
Or go into your phones and set it manually at Settings/AutoProvision/Server URL
Just make sure your firewall has a whitelist entry for your on site location so the phone can find the config files
0- February 15, 2019 at 8:28 pm
- February 16, 2019 at 12:57 am
- You must be logged in to reply to this topic.