Search results

Yikes. And these people vote. :yikes:

I got rid of AT&T more than a decade ago, and I got my breach offer from them yesterday. :mad5:

"The telecom giant said that 7.6 million current customers and 65.4 million former customers were affected by the breech," https://www.usatoday.com/story/tech/news/2024/04/16/att-security-features-data-leak/73347652007/

The PUBLIC design really wasn't engineered for a Raspberry Pi. Server exposure on the public internet with a static IP address is the target audience for this deployment. The design was intended for use on KVM (non-OpenVZ) cloud platforms, i.e. those that support ipset and do not employ a...

Colon used to be a separator in the old days. Digium "improved" things, and I was late to the party. Thanks. Fixed.

We've actually had this running with ChatGPT for the past six months. We use a dedicated DID locked down to a CallerID Number in Inbound Routes that points to the 2428 code in extensions_custom.conf: exten => 2428,1,Answer() exten => 2428,n,Wait(1) exten => 2428,n,System(rm -f /tmp/*.sln) ;exten...

Absolutely.

Correct. Proxmox 7 ISO is available in the Incredible PBX Repository. When all else fails, RTFM.

https://nerdvittles.com/groundwire-for-android-ios-the-best-10-youll-ever-spend/

That's what the add-fqdn option is for. In conjunction with the ipchecker app already activated in /etc/crontab, it keeps your whitelist up to date as long as you use a dynamic DNS service to automatically update the IP address associated with the FQDN for each of your extensions and your server..

Might be time to actually look in the logs and see whst the problems are. :idea:

Yep. Tesla's FSD is still beta, too... since 2016. :shit:

@ostridge: Fixed. Thank you.

So you're saying "Authentication failure for admin" doesn't really mean that?? An access refusal would trigger the same error?

@Samot: So where is the intrusion coming from with the manager.conf shown above which only permits admin attempts from 127.0.0.1??

Throwing the baby out with the bath water is rarely a good thing. :flowers:

If you mean Incredible PBX uses chan_sip on UDP 5060 and PJsip on UDP 5061, you are correct. Both are available to any user. Some default configs are provided for chan_sip only because it was more reliable in earlier releases and some users wanted to port their setups to the 2027 platform.

@Samot: This particular server is about 7 years old. It has had a working manager.conf file (as with all Incredible PBX builds) since Day One: [general] enabled = yes port = 5038 ;bindaddr = 0.0.0.0 bindaddr = 127.0.0.1 displayconnects=no ;only effects 1.6+ [admin] secret =...

The errors are showing up in the Asterisk error log. What's your theory if it's not an Asterisk attack.

bindaddr as well UDP 5060 and TCP 80 locked down so the vulnerability is elsewhere.