My cisco phones are provisioning just fine using EPM but they are not accepting the firmware in firmware slot 1. The current firmware is 7.5.5 and I’ve verified the cisco web site and the phones are able to go to the highest without doing anything special (like updating certain firmware’s in steps).
I’m wondering if anyone else has updated the firmware for these phones using the EPM? Are there any log files I can verify to see if there is any errors with the process?
NOTE:
I am still able to login to the UCP. It will just constantly give me an XMPP error.
Hi, I don’t think there is a way to modify that directory or its contents through the GUI. But typically, you shouldn’t have to. What is it you’re trying to achieve? You may be able to find what you need through the EndPoint Manager module, and maybe its Basefile Editor.
Hello,
I just want to verify this is legitimate. Our systems are flagging that we have a security update needed. However the Ticket number is #00000 and the notification is SEC-2019-000.
Can someone from Sangoma confirm before we update all systems?
Description is: Add GPG keys to begin to address longstanding keyserver issues
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
If it helps, I updated 6 servers yesterday and so far so good. It is related to the GPG key poisoning that has been commented on the forum.
Hi @Simon first you can confirm EPM generated configuration in /tftpboot is generating proper firmware location path in /tftpboot/ . If thats looks right then try to take pcap/tcpdump on the port (depends on provisioning protocol) to see interaction between cisco phone and your freepbx to know more about why phone is not downloading firmware based on phone generated request. thanks.
Hello:
Sorry to re open this I was out for the holidays and I was just a couple hours late to answer and got automatically closed.
Here is the link to the original topic:
If an @admin sees this and can reopen or merge both I would be grateful.
@mattf How do I get those logs? Happy to provide them.
Regards
It would appear to be related to this commit.
Or you could place the firmware files in the tftp folder of your freePBX server and edit the xml-config files of your phones to load the new firmware.
You need a ftp-client like FileZilla and a linux-compatible editor.
Great! I still think they should use the only working non poisonable key server and remove sks however.
I’ve been told that the key server changes will be committed soon which is awesome as that’ll solve future key server poisoning.
Also nice job @qwell!
Indeed it is. I was able to activate my installation using the “phx@” email address. Thanks!
It’s ultimately my problem for not ensuring I had entered the correct address. But many web sites these days ask new registrants to enter their email address twice to guard against this. Of course, people could just copy and paste an incorrect email address twice, but whenever I see this on a web page I make it a point to type the email into both input boxes.
As far as I know there is still an issue with the portal failing to set up new accounts when accessed using FreePBX > Admin > System Admin > Activate.
Thank you all for the confirmation. We will begin updating based on the response from @tonyclewis
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
I’m running the most current SangomaOS distro (12.7.6-1910-1.sng7) with FreePBX 15.0.16.27 and Asterisk 16.6.2. All modules are up to date.
The issue I’m experiencing is that some, but not all, inbound calls will simply hang up on the person when a call comes in. If the user calls back it will usually answer and is fine. Outbound calls have no issues at all.
Handsets are Grandstream GXP2170’s and I have one softphone extension that I’ve been using for testing as well. The issue occurs regardless of endpoint device.
Firewall is pfsense and provider is Skeytel. I’ve got this same combination (firewall and provider… PBX may be slightly older version) at other locations with no issues so I don’t believe it is anything from that end.
I have snippets from call logs for both failed and successful calls which I will post in separate reply to keep things clean. Any guidance of where to look net or what I can try would be greatly appreciated.
Check your drive space. make sure your drives arent full
Are we talking about Framework v15.0.16.38? I’m not seeing any changes in it.
…and I can’t post links cause I’m new and the log file is 3500+characters and limit is 3200… sweet. so if you are up for some arts and crafts, here are the links to the call logs.
Failed: driveDOTgoogleDOTcom/open?id=1A-JuzgjGf3i7Sx7OfPhFIz6JO9nuNo2y
Success: driveDOTgoogleDOTcom/open?id=1lz45SpubLH7DeMPJO96lujpSpKR616M5
Yep, that’s right.
There are more changes coming soon that are going to adjust which keyservers are used for downloading unknown public keys and updating existing keys when needed. Those changes should resolve the biggest issues people have been seeing.
