For the past few days I’ve been getting an error message “An outdated version of the Asterisk DPMA module was detected. Please upgrade to a supported version to ensure uninterrupted usage of DPMA supported phones”. I’ve searched the WIKI and the community pages but everything says that this should go away when I do regular system updates. But it doesn’t.
I’m running a Sangoma appliance version of FreePBX with 22.214.171.124 installed. Module updates and system updates have been performed as well as running yum update to make sure nothing slipped past me there. Asterisk is version 13.32.0
We are using the commercial Endpoint Manager and the instructions there seemed promising. However, I cannot complete the instructions because we don’t use Digium phones. I got as far as completing steps 1 - 3. Step 4 made no sense, since I have no Digium phones.
Looking elsewhere I found more resources
Ultimately I ran the ‘rpm’ command and got the following result
rpm -qa|grep res_digium
That sounds a lot like my own journey. We both ended up in the same spot. We have a “critical error” that doesn’t effect us as we don’t have Digium phones. But it would be nice to get rid of this error message. Frankly, I’m a bit surprised my post has been up this long with no replies until now. I was starting to think I was the only one with the problem and resigning myself to the fact that I’d probably always have the error in the Dashboard.
The WIKI says it will go away with the normal update process but obviously it does not.
That worked…sorta. It looks like I actually had an extra space in my command line after “fwconsole” instead of being transposed.
It deleted the notification but it didn’t solve the problem on the Dashboard. In fact there’s now a new problem that wasn’t there before the deletion.
In addition to the DPMA SSL Certification error it now has a second error “Intrusion detection handling method” -Intrusion detection handling method is been updated recently. Please clear your browser cache and try if you are having issue with Intrusion Detection Start/Restart/Stop button.
Clearing the cache does not correct the new second issue.Nor does stopping and restarting the Intrusion detection.
I don’t know enough about this stuff to start just deleting things. Sounds like I could hurt myself pretty badly that way. I don’t have an Digium phones but it sounds like this is a part of Asterisk? I’m not smart enough to know what else might be effected, or how to delete the module safely.
The message in the dashboard about the DPMA certificate is actually a feature not a bug. Many Digium phone users would be surprised, when in May their phones suddenly stop working. I have no idea, why the warning message does not disappear once you updated the DPMA-module.
Could you please check what version of DPMA you are using?
Go to Connectivity>Digium phones>general settings and tell me what it says in the dpma version field.
In either case…once you checked the DPMA-Asterisk version…you will find out that you have an old one <3.6.2
Then…go to admin, module admin and update your system (not the modules…you want the system-updates-tab! But only do it, if you have a standard distro with an unpatched Asterisk…
I hadn’t tried just dismissing the notice. I didn’t think that would make the problem go away but would be more like putting my hands over my eyes and pretending it doesn’t exist. Generally pretending a problem doesn’t exist is a bad idea and gets you in trouble sooner or later.
But you are right, I dismissed the error just now and reloaded the page and the error is gone. Hands are firmly against the eyes. I see no evil here.
The warning may come back, the next time you update your freePBX modules. You can, of course, dismiss it again. The version must be 3.6.2 or higher. The Asterisk DPMA module is not a freePBX module, therefore you can only update it, when you do a module-admin_system-updates update as shown above. Yet, you dont have to, when you dont use the Digium phones.