What Are You Doing Right Now
-
Upgrading my FreePBX system to 14....
-
Fixing GIT problems for @QuixoticJeremy
-
FreePBX upgrade went fairly smooth. Asterisk defaulted to Chan_SIP driver instead of PJSIP that took me a little bit to figure out, but other than that no other issues I have found yet.
-
About to work on my band arrangement contract task.
-
Hurricane closing in on Houston. My nieces and nephew just had school canceled.
-
@scottalanmiller said in What Are You Doing Right Now:
Hurricane closing in on Houston. My nieces and nephew just had school canceled.
Stay safe.
-
We are good up here, might seen rain tonight. @StorageNinja is in the path, though.
-
Doing some late night and long overdue Ubuntu updates.
-
Catching up on the news. Bed time about now.
-
Oddly, Spiceworks had two questions in the middle of the night, that were nearly identical, just minutes apart from each other. Both by first posters or second time posters, and the one answered oddly by another first time poster. Very strange.
-
Also strange, after years of the high school MTA cert not being mentioned by anyone, suddenly it comes up every few weeks as if it was some new thing that no one had ever heard of and it came up TWICE in five minutes tonight!
-
I'm trying to troubleshoot why a voip phone that registered and was functional yesterday, fails to register today. . .
-
@dustinb3403 said in What Are You Doing Right Now:
I'm trying to troubleshoot why a voip phone that registered and was functional yesterday, fails to register today. . .
Maybe today is its day off.
-
@nerdydad said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
I'm trying to troubleshoot why a voip phone that registered and was functional yesterday, fails to register today. . .
Maybe today is its day off.
Better not be. . .
-
What's weird is none of the accounts that I have tried register on the desk phone. The original account fails to register on a softphone as well.
Is there a setting in FreePBX somewhere to block a device for a duration of time that may be set?
-
I know there is a fail2ban-esque firewall setup by default on FreePBX. I'm pretty sure @JaredBusch has a thread on it somewhere.
-
@dustinb3403 said in What Are You Doing Right Now:
What's weird is none of the accounts that I have tried register on the desk phone. The original account fails to register on a softphone as well.
Is there a setting in FreePBX somewhere to block a device for a duration of time that may be set?
Can happen if there are lots of failed attempts from that IP range.
-
@scottalanmiller said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
What's weird is none of the accounts that I have tried register on the desk phone. The original account fails to register on a softphone as well.
Is there a setting in FreePBX somewhere to block a device for a duration of time that may be set?
Can happen if there are lots of failed attempts from that IP range.
How would I know / can check?
-
@dustinb3403 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
What's weird is none of the accounts that I have tried register on the desk phone. The original account fails to register on a softphone as well.
Is there a setting in FreePBX somewhere to block a device for a duration of time that may be set?
Can happen if there are lots of failed attempts from that IP range.
How would I know / can check?
The Responsive Firewall
-
@jaredbusch said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
What's weird is none of the accounts that I have tried register on the desk phone. The original account fails to register on a softphone as well.
Is there a setting in FreePBX somewhere to block a device for a duration of time that may be set?
Can happen if there are lots of failed attempts from that IP range.
How would I know / can check?
The Responsive Firewall
We've already determined that a new block was added to block the SIP port (5060) and DNS entries were added to "block" the PBX.
