Quantcast
Channel: FreePBX Community Forums - Latest posts
Viewing all 227945 articles
Browse latest View live

Inbound calls not working

$
0
0

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.


Res_srtp.c: SRTCP unprotect failed because of authentication failure

$
0
0

I am running a plain vanilla version of Asterisk 16.7 and FreePBX 14

I just started getting the following error – during all calls in the logs –

Does not seem to affect anything – calls connect fine both in and out and audio works as well – any ideas what this is about or how to get rid of this message?

res_srtp.c: SRTCP unprotect failed on SSRC 905329652 because of authentication failure
[2020-01-12 18:05:48] VERBOSE[22770][C-00000006] res_srtp.c: SRTCP unprotect failed on SSRC 905329652 because of authentication failure
[2020-01-12 18:05:53] VERBOSE[22770][C-00000006] res_srtp.c: SRTCP unprotect failed on SSRC 905329652 because of authentication failure
[2020-01-12 18:05:58] VERBOSE[22770][C-00000006] res_srtp.c: SRTCP unprotect failed on SSRC 905329652 because of authentication failure

thanks,

14 to 15 Upgrade Tool Error

$
0
0

I am also experiencing an error with the upgrade tool

Running a plain version of FreePBX 14.0.13.23 and Asterisk 16.7 – not the distro

I have already installed the latest upgrade tool version 14.0.10 but also still get the error noted above and below

Mitel crackling audio on system recordings

14 to 15 Upgrade Tool Error

$
0
0

fwconsole ma downloadinstall versionupgrade --force

(only works when the repos are working :wink: )

System Recordings not working

System Recordings not working

$
0
0

This looks to be a FreePBX 13+ machine, use fwconsole instead of amportal

You gotta make sure the folder is owned by and the Asterisk user can write.

Multiple Accounts on Zulu Mobile

$
0
0

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.


Config.php hacked - need to replace

$
0
0

At this point you should assume that your PBX is completely conpromised, more than just a hacked php file. I don’t want to sound paranoid but if I were you I would start from scratch and re-install from the ISO.

Config.php hacked - need to replace

$
0
0

Also have Sangoma post mortem how you were hacked before you ‘start from scratch’

Config.php hacked - need to replace

$
0
0

Unfortunately a full rebuild right now is not an option, as the PBX is routing calls for 24/7 technical support for customers. Also, I installed the PBX appliance while working there full-time - now I am in a new job, and just helping the out on an as-needed basis after hours.

About the best I could do would be to provision an unused Dell 1U server in the same rack as a new FreePBX box, and install FreePBX from scratch over there, then cut things over from the Sangoma appliance, but I would need to prove the need for it before I could justify the time and money the effort would cost.

Config.php hacked - need to replace

$
0
0

I have confirmed that no unusual call activity appears in the CDR call logs. The last time I had a FreePBX/asterisk server get hacked, it was for the purpose of someone making international calls via SIP traffic from the internet and through the server. This server is behind a router that does not forward SIP traffic, so that can’t happen.

So at the moment, I’m going to keep an eye on things, I’ve ensured that the admin page is only accessible to LOCAL addresses plus my fixed IP, and SIP traffic is blocked from the internet. I appreciate the help and advice.

Config.php hacked - need to replace

$
0
0

Well there were serious XSS vulnerabilities found and fixes released back in December for them. Your config.php was hack/modified. So I guess the question becomes before you updated the Framework module did you actually look at the config.php to see when it was last modified, what was changed, get a copy of it so someone else could review it if you’re not sure?

Has anything else been done to verify that this system hasn’t been compromised? Because if not and due to the fact it sat open with these known XSS exploits (which people did get hit by) I would say you can’t give them a 100% answer that this box hasn’t been touched by outside hands.

14 to 15 Upgrade Tool Error

$
0
0

Dicko – i was already on 14.0.10 – not sure how your post helps resolve the issue?

Can you explain further?

thanks

14 to 15 Upgrade Tool Error

$
0
0

Well for a while the repos have not been working, Personally I had a similar problem, FreePBX was already >= 14 but the upgrade script still bitched (click on the red link) , . . . . forcing the upgrade made everything kosher again and the upgrade proceeded.


14 to 15 Upgrade Tool Error

$
0
0

lucky for you – no same luck here?

Do i need to reboot asterisk or the server afterwards?

fwconsole ma downloadinstall versionupgrade --force
No repos specified, using: [standard,extended,unsupported] from last GUI settings

Downloading module ‘versionupgrade’
Processing versionupgrade
Downloading…
320726/320726 [============================] 100%
Finished downloading
Extracting…Done
Download completed in 0 seconds
Generating CSS…Done
Module versionupgrade version 14.0.9 successfully installed
Updating Hooks…Done
[root@# fwconsole versionupgrade --check
±-------±-----------------------±-----------------------------------------------------------------+
| Status | Name | Description |
±-------±-----------------------±-----------------------------------------------------------------+
| O | Files ownership | Files under /var/www/html appear to be owned by the correct user |
| O | Asterisk 13 or higher | Your Asterisk version of 16.7.0 is supported |
| O | NodeJS 8.0.0 or higher | Your NodeJS Version of 8.17.0 is supported |
| O | SQL 5.5.52 or higher | Your SQL Version of 5.5.64 is supported |
| O | PHP 5.6 or higher | Your PHP Version of 5.6.40 is supported |
| X | FreePBX 14 | Currently we Dont support upgradation |
±-------±-----------------------±-----------------------------------------------------------------+
You may not proceed with the upgrade. Please see the errors above

14 to 15 Upgrade Tool Error

$
0
0

FreePBX 14 | Currently we Dont support upgradation |

Likely a Sangoma appliance and not FreePBX per se

14 to 15 Upgrade Tool Error

$
0
0

Nope – not an appliance – just a regular VM on Linode which i installed myself from scratch – Centos – Asterisk and FreePBX

14 to 15 Upgrade Tool Error

$
0
0

Sorry above my paygrade , take it to the Source :wink:

Config.php hacked - need to replace

$
0
0

Toll fraud could rise to a lot more money than the cost of fixing the PBX, the customer should know better than that…

Viewing all 227945 articles
Browse latest View live