What Are You Doing Right Now
-
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.
-
@scottalanmiller said in What Are You Doing Right Now:
@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.
In the PBX? That seems unlikely.
Please carefully read what was replied to before replying about a different issue.
-
@jaredbusch said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@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.
In the PBX? That seems unlikely.
Please carefully read what was replied to before replying about a different issue.
No, not in the PBX. On the LAN.
-
@scottalanmiller said in What Are You Doing Right Now:
@jaredbusch said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@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.
In the PBX? That seems unlikely.
Please carefully read what was replied to before replying about a different issue.
No, not in the PBX. On the LAN.
Then again, read more carefully about a thing before you quote and reply.
I sepcifically replied and quoted the chain asking about where to look for something in the PBX itself.
I was not replying to anything about the LAN or router or external firewall.
This makes your quote of my post lead to completely incorrect inferences of where these blocks took place.
-
Downloading and setting a Win10 usb to take home.
If I get time I might try and re-setup the old Media box into a gaming machine to play simple games like SimCity 5/Emergency2017/Command and Conquer etc.
Then set-up something like Remotr to "stream" to my tablet to play on.
-
On lunch
-
@quixoticjeremy said in What Are You Doing Right Now:
On lunch
Getting ready for hopefully some deployments tonight
