Yes, this prompt will shows up on SIP 2.2.2 as well.<br>I never had any issues with this though, it will clear up after next registration of phone.<br>I just downloaded SIP 3.0 and have not got a chance to check and see if it happens with this firmware as well.
<br><br><br><div class="gmail_quote">On Jan 22, 2008 2:53 PM, Steve Johnson <<a href="mailto:stevej456@gmail.com">stevej456@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have just retested and agree that this error eventually does clear<br>itself. However, in this test it took about 35 minutes and each<br>Polycom phone produced between 1000 and 1300 error message lines at 1<br>to 0 second intervals (which I captured to the debug log). Once one
<br>phone starts flagging an error, all Polycom phones that are<br>buddy-watching join right in.<br><br>I triggered the problem by simply restarting asterisk:<br>/usr/sbin/asterisk -rx "restart when convenient". Sometimes (but not
<br>all the time) it will also start if you reload.<br><br>All suggestions appreciated.<br><font color="#888888"><br>S.<br></font><div><div></div><div class="Wj3C7c"><br>On Jan 22, 2008 9:23 AM, Steve Johnson <<a href="mailto:stevej456@gmail.com">
stevej456@gmail.com</a>> wrote:<br>> I am using Polycom's SIP 2.2.0047 (the current release) and am seeing<br>> this. It seems to occur less often with "extensions reload" rather<br>> than just "reload", but it would be nice to fix this.
<br>><br>> Tx.<br>><br>><br>><br>> On Jan 22, 2008 8:30 AM, Steve Davies <<a href="mailto:davies147@gmail.com">davies147@gmail.com</a>> wrote:<br>> > On 1/22/08, Steve Johnson <<a href="mailto:stevej456@gmail.com">
stevej456@gmail.com</a>> wrote:<br>> > > Hi list,<br>> > ><br>> > > There are many Polycom experts on this list -- hopefully someone has a solution.<br>> > ><br>> > > With *several* versions of Asterisk
1.4.x, doing a reload of Asterisk<br>> > > causes the Polycom 601 phones to start dumping these messages to the<br>> > > CLI.<br>> > ><br>> > > -- Incoming call: Got SIP response 500 "Internal Server Error"
<br>> > > back from 192.168.2.x<br>> ><br>> > [snip]<br>> ><br>> > I have not seen this problem here since upgrading to 2.1.2 firmware.<br>> > Or perhaps it was 2.2.0, one or the other. The phones now seem to
<br>> > recover on thier own when Asterisk returns.<br>> ><br>> > Cheers,<br>> > Steve<br>> ><br>> > _______________________________________________<br>> > -- Bandwidth and Colocation Provided by
<a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>> ><br>> > asterisk-users mailing list<br>> > To UNSUBSCRIBE or update options visit:<br>> > <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">
http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>> ><br>><br><br>_______________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">
http://www.api-digital.com</a> --<br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users
</a><br></div></div></blockquote></div><br>