<div dir="ltr">They are sending requests from his own public ip huh? Trade secrets....<div>Hmmmm, IPTaibles, Fail2Ban (as a preventative), there is something</div><div>I am missing.... What the f is it called again? Oh yeah Pike!!!</div>
<div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">>> alwaysauthreject = yes</span><br></div><div style><span style="font-family:arial,sans-serif;font-size:13px">I don't know about that.... However, using the mac address of the device as the `<a href="http://sipbuddies.name">sipbuddies.name</a>`, and having </span><span style="font-family:arial,sans-serif;font-size:13px">`sipbuddies.secret` other than </span><span style="font-family:arial,sans-serif;font-size:13px">`12345a` ;), I would say yes too.</span></div>
<div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">>> One of Asterisk's dirty little secrets is that it does not show the source IP when a device or hacker tries sending a call >> without registering. The rejection message in the logs do not show the IP of the attacker. Yes it sucks, yes it has </span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">>> been that way for many many years.</span><br></div><div><br></div><div style>Does not good if the address is spoofed as it seems is the case here. IPTables, class c filter rule buy yourself a burger or a slice...</div>
<div><br></div><div>Be strong my legit brotherins!!! <br><div style></div></div><div style>N.<br></div></div>