<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/19/2014 08:40 AM, Steve Murphy
wrote:<br>
</div>
<blockquote
cite="mid:CAPPCp8FRV6oe1Nokv-ecT4sYGc9qzh2KkqxAkB_g9b+0iQYPYw@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra">
<div class="gmail_quote">
<div class="gmail_default" style="font-family:courier
new,monospace;display:inline">
<div class="gmail_default" style="font-family:courier
new,monospace">Here's another idea! How about changing
your port from 5060 to something<br>
</div>
<div class="gmail_default" style="font-family:courier
new,monospace">different, maybe 7067 or some other
number that is not popularly being used?<br>
</div>
<div class="gmail_default" style="font-family:courier
new,monospace">
You'll provision your phones to use this port, and the
scanners will not<br>
</div>
<div class="gmail_default" style="font-family:courier
new,monospace">find you. Seems a much simpler
solution... but there are some drawbacks...<br>
</div>
<div class="gmail_default" style="font-family:courier
new,monospace">can anyone think of them? And will these
drawbacks matter to you? And, given<br>
</div>
<div class="gmail_default" style="font-family:courier
new,monospace">
this solution, will the odds that a scanner might find
your machine be so low,<br>
that it is not worth using something like fail2ban to
override them? Food<br>
for thought!<br>
</div>
<div class="gmail_default" style="font-family:courier
new,monospace">
<br>
</div>
<div dir="ltr">murf<br>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
We use this tactic. I never seen scanners in my logs anymore.
Haven't had any issues with it to date... we use Linksys, Polycom,
Yealink, Grandstream, and Audiocodes products. All have the ability
to specify the registration port.<br>
<br>
Cheers,<br>
<br>
j<br>
</body>
</html>