On 1/22/08, Steve Johnson [EMAIL PROTECTED] wrote:
Hi list,
There are many Polycom experts on this list -- hopefully someone has a
solution.
With *several* versions of Asterisk 1.4.x, doing a reload of Asterisk
causes the Polycom 601 phones to start dumping these messages to the
CLI.
I am using Polycom's SIP 2.2.0047 (the current release) and am seeing
this. It seems to occur less often with extensions reload rather
than just reload, but it would be nice to fix this.
Tx.
On Jan 22, 2008 8:30 AM, Steve Davies [EMAIL PROTECTED] wrote:
On 1/22/08, Steve Johnson [EMAIL
I have just retested and agree that this error eventually does clear
itself. However, in this test it took about 35 minutes and each
Polycom phone produced between 1000 and 1300 error message lines at 1
to 0 second intervals (which I captured to the debug log). Once one
phone starts flagging an
Yes, this prompt will shows up on SIP 2.2.2 as well.
I never had any issues with this though, it will clear up after next
registration of phone.
I just downloaded SIP 3.0 and have not got a chance to check and see if it
happens with this firmware as well.
On Jan 22, 2008 2:53 PM, Steve Johnson
Hi list,
There are many Polycom experts on this list -- hopefully someone has a solution.
With *several* versions of Asterisk 1.4.x, doing a reload of Asterisk
causes the Polycom 601 phones to start dumping these messages to the
CLI.
-- Incoming call: Got SIP response 500 Internal Server
