<div class="gmail_quote">On Thu, Oct 28, 2010 at 1:42 AM, Jonas Kellens <span dir="ltr"><<a href="mailto:jonas.kellens@telenet.be">jonas.kellens@telenet.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 10/28/2010 12:52 PM, Gordon Henderson wrote:<br>
> On Thu, 28 Oct 2010, Jonas Kellens wrote<br>
>> On 10/28/2010 10:44 AM, Kevin Keane wrote:<br>
>><br>
>>> I assume that you checked and the remote IP is a legitimate IP phone? If<br>
>>> not, it could be an attempt to break into your system.<br>
>>><br>
>>> If it is a legitimate IP phone, make sure that the SIP configuration is<br>
>>> correct -- if the SIP authentication fails, you can see this happening.<br>
>>><br>
>>><br>
>> 1. This is a legitimate phone, yes.<br>
>> 2. Registration goes as follow : REGISTER> SIP/2.0 401 Unauthorized><br>
>> Re-Register with Digest> 200 OK<br>
>><br>
> Is it s Snom phone?<br>
><br>
> I've seen Snoms do this...<br>
><br>
> Gordon<br>
><br>
<br>
</div>I have this with Snom 320, Snom 370, Grandstream GXW4008 and YeaLink T28...<br>
<font color="#888888"><br></font></blockquote><div><br>Yes, I have seen this with Snom 370s... It's maddening. I'm going to start testing out the version 8.x firmware.<br><br>- Julian<br><br></div></div><br>