Extremely new to FreePBX and learning all on my own.
I have been able to create a few EXT’s and auto Provision a few Yealinks.
When I make a change to the template, and choose save, rebuild configs, and update phones, my phones reboot, but never apply the new changes. Could someone kindly point out my error? Not sure what I am doing wrong.
There are so many ways that this could be not working, it’s hard for us to know.
You’re going to have to tell us a lot more detail about how you’ve configured your phones to pull config, what protocol you are using for provisioning, what firewall settings you may or may not be using, how you have option 66 configured in your DHCP server, and probably three or four more pieces of information before you’re going to get any useful answers.
I’ll try my best to answer.
I am using HTTP Provisioning protocol
No firewall settings
Not sure about option 66 on DHCP server. I am using FiOS and do not see DHCP options for option 66, and I am testing Freepbx on a spare PC for the time being.
Edit:
Only a manual reboot applies the new changes.
If a manual reboot pulls the updates, then the file source for the files “in the phone” is correct. The config could be over-writing the good location with one that doesn’t work.
The /var/log/httpd/access.log file should be telling you if there’s an error on the download. It could be a problem in the EPM field for the firmware download, or it could be that the phone doesn’t think the files have changed and, therefore, doesn’t load them.
It’s hard to tell. Take a look at the access.log file and see if there’s something in there to clue you in.
Thanks so much for the help. Ill check the access.log to see.
one of the things that can cause this is that you have manually set some of the config parameters in the phone.
As Dave said, logs should direct you to the issue.
However, I’ve seen issues like this occur with outdated firmware, make sure you have newer firmware installed on your phones.
When I go to /var/log/httpd and do an ls, I do not see the access.log file?
I believe I am using the most updated firmware available via endpoint manager/firmware management.
It lists 1.17 as the newest firmware available. I tried different FW’s as well, and still have the same issue.
I ran the following command: nano /var/log/httpd/access_log and have some output. Here is some entries for 2.212 which is one of the yealinks I am having issues with
192.168.2.212 - - [05/Mar/2018:15:07:19 -0500] “GET /0015659a64fd.boot HTTP/1.1” 404 215 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:15:07:20 -0500] “GET /y000000000000.boot HTTP/1.1” 404 216 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:15:07:20 -0500] “GET /y000000000028.cfg HTTP/1.1” 200 931 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:15:07:20 -0500] “GET /0015659a64fd.cfg HTTP/1.1” 200 73636 “-” “Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd”
192.168.2.212 - - [05/Mar/2018:15:07:54 -0500] “GET /yealink/1/t46.rom HTTP/1.1” 200 23144608 “-” “Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd”
192.168.2.212 - - [05/Mar/2018:16:25:23 -0500] “GET /0015659a64fd.boot HTTP/1.1” 404 215 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:25:23 -0500] “GET /y000000000000.boot HTTP/1.1” 404 216 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:25:23 -0500] “GET /y000000000028.cfg HTTP/1.1” 200 931 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:25:23 -0500] “GET /0015659a64fd.cfg HTTP/1.1” 200 73762 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:25:40 -0500] “GET /yealink/1/t46.rom HTTP/1.1” 200 23144608 “-” “Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd”
192.168.2.212 - - [05/Mar/2018:16:33:16 -0500] “GET /0015659a64fd.boot HTTP/1.1” 404 215 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:33:16 -0500] “GET /y000000000000.boot HTTP/1.1” 404 216 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:33:17 -0500] “GET /y000000000028.cfg HTTP/1.1” 200 931 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:33:17 -0500] “GET /0015659a64fd.cfg HTTP/1.1” 200 73755 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:33:16 -0500] “GET /0015659a64fd.boot HTTP/1.1” 404 215 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:33:16 -0500] “GET /y000000000000.boot HTTP/1.1” 404 216 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:33:17 -0500] “GET /y000000000028.cfg HTTP/1.1” 200 931 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:33:17 -0500] “GET /0015659a64fd.cfg HTTP/1.1” 200 73755 “-” “Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd”
192.168.2.212 - - [05/Mar/2018:16:35:52 -0500] “GET /yealink/1/t46.rom HTTP/1.1” 200 23144608 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:35:52 -0500] “GET /yealink/1/t46.rom HTTP/1.1” 200 23144608 “-” “Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd”
I ran Asterisk _rvvv and found this input which seems to offer some evidence of what is happening?
[2018-03-06 15:06:00] ERROR[13369]: res_sorcery_config.c:230 sorcery_config_internal_load: Unable to load config file ‘pjproject.conf’
[2018-03-06 15:06:00] ERROR[21336]: res_pjsip_config_wizard.c:1086 object_type_loaded_observer: Unable to load config file ‘pjsip_wizard.conf’
[2018-03-06 15:06:00] ERROR[21336]: res_pjsip_config_wizard.c:1086 object_type_loaded_observer: Unable to load config file ‘pjsip_wizard.conf’
[2018-03-06 15:06:00] ERROR[21336]: res_pjsip_config_wizard.c:1086 object_type_loaded_observer: Unable to load config file ‘pjsip_wizard.conf’
[2018-03-06 15:06:00] ERROR[21336]: res_pjsip_config_wizard.c:1086 object_type_loaded_observer: Unable to load config file ‘pjsip_wizard.conf’
[2018-03-06 15:06:00] NOTICE[21336]: sorcery.c:1406 sorcery_object_load: Type ‘system’ is not reloadable, maintaining previous values
[2018-03-06 15:06:00] ERROR[21336]: res_pjsip_config_wizard.c:1086 object_type_loaded_observer: Unable to load config file ‘pjsip_wizard.conf’
[2018-03-06 15:06:00] ERROR[13369]: res_pjsip_config_wizard.c:1086 object_type_loaded_observer: Unable to load config file ‘pjsip_wizard.conf’
[2018-03-06 15:06:00] WARNING[13369]: iax2/firmware.c:237 iax_firmware_reload: Error opening firmware directory ‘/var/lib/asterisk/firmware/iax’: No such file or directory
[2018-03-06 15:06:00] NOTICE[13369]: iax2/provision.c:562 iax_provision_reload: No IAX provisioning configuration found, IAX provisioning disabled.
[2018-03-06 15:06:00] ERROR[13369]: res_pjsip_config_wizard.c:1086 object_type_loaded_observer: Unable to load config file ‘pjsip_wizard.conf’
[2018-03-06 15:06:00] NOTICE[13369]: confbridge/conf_config_parser.c:2095 verify_default_profiles: Adding default_menu menu to app_confbridge
[2018-03-06 15:06:00] WARNING[13369]: app_voicemail.c:13835 actual_load_config: maxsilence should be less than minsecs or you may get empty messages
[2018-03-06 15:06:00] WARNING[13369]: app_flite.c:76 read_config: Flite: Unable to read config file flite.conf. Using default settings
These lines tell you the phone is provisioning and successfully downloading the firmware:
192.168.2.212 - - [05/Mar/2018:16:33:17 -0500] “GET /y000000000028.cfg HTTP/1.1” 200 931 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
192.168.2.212 - - [05/Mar/2018:16:33:17 -0500] “GET /0015659a64fd.cfg HTTP/1.1” 200 73755 “-” “Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd”
192.168.2.212 - - [05/Mar/2018:16:35:52 -0500] “GET /yealink/1/t46.rom HTTP/1.1” 200 23144608 “-” "Yealink SIP-T46G 28.81.0.70 00:15:65:9a:64:fd"
if the phone is not behaving to expectations, it could be your expectations are wrong, or perhaps a firmware issue.
The files aren’t on the server.
In your phone, the file “source” setting is wrong, as in there should probably be a directory in there.
Try this. Log into the console and type the following:
find / -name ‘0015659a64fd.boot’
and see if you can find out where the boot file for your phone actually is.
Well, my expectations are that if I make changes to button layout, save, rebuild and reboot, that the phones will reboot, pull down the new Config and display the new button layout. Does it not work like that?
I tried typing find / -name ‘0015659a64fd.boot’. Once I hit return, nothing happens. Just goes back to the #
The file doesn’t exist on your system. Is FreePBX installed on 192.168.2.212?
Try the following:
find / -name ‘t46.rom’
Maybe that will help you find the errant files.
Rom found in
/tftpboot/yealink/1/t46.rom
/tftpboot/yealink/2/t46.rom
FreePBX is installed on 192.168.2.96.
192.168.2.212 is the IP of the yealink phone
Good. The files are getting updated to the TFTP directory.
In that case, one way to solve the problem is to turn on the TFTP protocol in the phone and turn on the TFTP daemon on the server. You should be good to go after that.
The only part of that that’s hard is the TFTP daemon. You have to set “disable” to “no” in the /etc/xinetd.d/tftpd config file (the filename might be different, I don’t have a machine I can access here).
Tried TFTP as well, and still not updating properly.
Check your /var/log/message file and see what is happening with the requests for TFTPd.
I found the issue. When I first started, I duplicated a T46 template to use with a T29g phone. Each time I entered the T46 template I would always see the T46 and T29 models highlighted. I thought perhaps this was causing a conflict and I deleted both the Templates and created them individually. Now my yealinks update properly with any template changes.
Thanks so much for all the help 