No subject


Thu Jul 12 09:23:04 CDT 2007


600
I'm subscribed to a "buddy" on my Polycom phone. Periodically I'd get this
error: 'Incoming call: Got SIP response 500 "Internal Server Error" back
from 10.1.1.200'.

Additional Description

We have six(6) Polycom 601 attenendant consoles monitoring roughly
forty(40) Polycom 430 phones each for a total of one hundred (100) or so
watchers/hints.

To reproduce the behaviour you need only interrupt chan_sip via reload, or
an Asterisk restart.  Once this has been done, presence notifications sent
to the phones will no longer take place properly.  It is unclear as to
whether this problem is due to the Asterisk system not sending the right
messages, or the Polycom not responding properly to a properly formatted
message.  But, after a while, the phones will start sending messages back
in response to messages from Asterisk that say "Internal Server Error". 
One thing is for certain.  After the channel is interrupted, by reload or
restart, presence no longer works.
====================================================================== 

---------------------------------------------------------------------- 
 callguy - 09-18-07 13:43  
---------------------------------------------------------------------- 
We are seeing similar behavior, though we are not experiencing any reboot
issues and we do not see it on reload of chan_sip, but whenever restarting
asterisk the 601's will start sending out the same "Internal Server Error"
messages. 

Rebooting them resolves the issue. Also, it does appear that over time if
the status of the watched phones changes, it will slowly sort itself out -
but either way the situation isn't ideal.

If someone could let us know what debug data would be needed to help
troubleshoot we are happy to test. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-18-07 13:43  callguy        Note Added: 0070747                          
======================================================================




More information about the asterisk-bugs mailing list