Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <1319633296.2238.4.camel@black> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <64599> Message-ID: <[email protected]>
I have run into this issue using Polycom phones (firmware 3.2.6/4.3.1) on one of my sipXecs 4.4.0 update #14 servers. I can confirm that this behavior still occurs even when using TCP for transport. The size of the SIP messages which cause the Polycom phone to respond with "500 Internal Server Error" are about 9K or larger. I have seen one that was over 11K acknowledged with "200 OK", so not all over this size are failing, just the ones that appear to be mangled (truncated) coming from sipXrls. This system has 18 Polycom 650s, most of which have sidecars, and most users have about a dozen speed dials with presence set up. A couple of users have 17 speed dials with presence. Domenico Chierico wrote on Wed, 26 October 2011 08:48 > I was trying to replicate this: > > http://track.sipfoundry.org/browse/XX-9857 > > and I didn't have any luck, can someone report some more > details about it: > > 1) what if you insert more than 12 extensions? > 2) can you attach log in debug mode from the sipXrls > > thanks > Domenico Chierico -- _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
