"Andrew Gabriel" <andrew@cucumber.demon.co.uk> wrote in message
news:42dba60a$0$38044$5a6aecb4@news.aaisp.net.uk...
> In article <42db928c$0$13702$ed9e5944@reading.news.pipex.net>,
> "Paul D.Smith" <paul_d_smith@x-hotmail.com> writes: 
>
> Much to my surprise, upgrading (and then downgrading again)
> my sipura spa-3000 didn't lose any settings.
>

Out of interest - why did you downgrade?

[ Post a follow-up to this message ]

In article <3k43teFs1m45U1@individual.net>,
"Lee" <me@privacy.net> writes:
>
> "Andrew Gabriel" <andrew@cucumber.demon.co.uk> wrote in message
> news:42dba60a$0$38044$5a6aecb4@news.aaisp.net.uk... 
>
> Out of interest - why did you downgrade?

The version 3 firmware introduced and fault whereby all the
syslog messages are missing the PRI header so they aren't
usable. In the version 2 firmware, most of the syslog messages
are more correctly formed (a few only are missing the PRI header
and unusable).

Also, the version 3 firmware didn't fix the TCP window handling
problem which was the main reason for trying the upgrade. This
prevents the browser interface working properly when the browser
system advertises a large TCP window (i.e. probably something
over 32k, but not window scaling), and it is running across a WAN
or sufficient routers such that more than 32k of data gets
buffered across the network. It looks to me like the spa-3000 is
perhaps tripping on some associated 16bit arithmetic which needs
to be 32 bit arithmetic, screwing up its TCP sequence calculations,
and gets stuck in a TCP restransmit loop. If you have control of
the TCP window advertised from the browser system, knocking it
down to 20k is a workaround.

--
Andrew Gabriel

[ Post a follow-up to this message ]

"Andrew Gabriel" <andrew@cucumber.demon.co.uk> wrote in message
news:42dced6e$0$38046$5a6aecb4@news.aaisp.net.uk...
> In article <3k43teFs1m45U1@individual.net>,
> "Lee" <me@privacy.net> writes: 
>
> The version 3 firmware introduced and fault whereby all the
> syslog messages are missing the PRI header so they aren't
> usable. In the version 2 firmware, most of the syslog messages
> are more correctly formed (a few only are missing the PRI header
> and unusable).
>
> Also, the version 3 firmware didn't fix the TCP window handling
> problem which was the main reason for trying the upgrade. This
> prevents the browser interface working properly when the browser
> system advertises a large TCP window (i.e. probably something
> over 32k, but not window scaling), and it is running across a WAN
> or sufficient routers such that more than 32k of data gets
> buffered across the network. It looks to me like the spa-3000 is
> perhaps tripping on some associated 16bit arithmetic which needs
> to be 32 bit arithmetic, screwing up its TCP sequence calculations,
> and gets stuck in a TCP restransmit loop. If you have control of
> the TCP window advertised from the browser system, knocking it
> down to 20k is a workaround.
>

Not sure what all that means, but thanks! ;-)

I have an spa-3000 that appears to be working fine but thought I would
check.

Lee

[ Post a follow-up to this message ]