asterisk users - May 2005 - SIPURA SPA-2000 webserver dead after firmware upgrade

I just got a refurb Sipura SPA-2000 and was able to assign it an IP
address with DHCP and ping the device, but then I ran the firmware 
upgrade utility to bring it up to spa2k-2.0.13g which seemed to
work just fine, but after it rebooted I cannot connect to its
webserver for configuration.  I can still ping the unit.  When
I use the built in voice menu it reads back the right IP address,
webserver port, and claims the webserver is enabled, but I can't
connect to port 80 on the device and running the firmware upgrade
utility says that it cannot connect to the unit either.

Has anyone seen something like that and is there a fix?  A google
search didn't turn up any apparent hits.

Thanks
Steve

I have a SPA-3000 and Netgear switch; when I run an upgrade on SPA-3000
with Netgear switch in between my SPA-3000 stopped functioning; I send
it back and got a new unit.  However, later on I run onto a post (on
Voxilla) that warned not to use Netgear switch to upgrade Sipura unit.  
Indeed, I use my old hub to upgrade the new unit and it went smooth.

-- 
#Joseph

On Tue, 2005-05-10 at 21:50 -0400, Steve Prior wrote:
> I just got a refurb Sipura SPA-2000 and was able to assign it an IP
> address with DHCP and ping the device, but then I ran the firmware 
> upgrade utility to bring it up to spa2k-2.0.13g which seemed to
> work just fine, but after it rebooted I cannot connect to its
> webserver for configuration.  I can still ping the unit.  When
> I use the built in voice menu it reads back the right IP address,
> webserver port, and claims the webserver is enabled, but I can't
> connect to port 80 on the device and running the firmware upgrade
> utility says that it cannot connect to the unit either.
> 
> Has anyone seen something like that and is there a fix?  A google
> search didn't turn up any apparent hits.
> 
> Thanks
> Steve

Run nmap against the ip address and see what ports are active for tcp
service. Maybe you can connect via a different port (I know it should be
80), and see if the configuration is different between voice and web

dave
On Tue, 2005-05-10 at 21:50 -0400, Steve Prior wrote:
> I just got a refurb Sipura SPA-2000 and was able to assign it an IP
> address with DHCP and ping the device, but then I ran the firmware 
> upgrade utility to bring it up to spa2k-2.0.13g which seemed to
> work just fine, but after it rebooted I cannot connect to its
> webserver for configuration.  I can still ping the unit.  When
> I use the built in voice menu it reads back the right IP address,
> webserver port, and claims the webserver is enabled, but I can't
> connect to port 80 on the device and running the firmware upgrade
> utility says that it cannot connect to the unit either.
> 
> Has anyone seen something like that and is there a fix?  A google
> search didn't turn up any apparent hits.
> 
> Thanks
> Steve
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users

Steve Prior wrote:
> I just got a refurb Sipura SPA-2000 and was able to assign it an IP
> address with DHCP and ping the device, but then I ran the firmware 
> upgrade utility to bring it up to spa2k-2.0.13g which seemed to
> work just fine, but after it rebooted I cannot connect to its
> webserver for configuration.  I can still ping the unit.  When
> I use the built in voice menu it reads back the right IP address,
> webserver port, and claims the webserver is enabled, but I can't
> connect to port 80 on the device and running the firmware upgrade
> utility says that it cannot connect to the unit either.
Sounds like you got the one we just sent back to Sipura a couple weeks 
ago.  Try to update the firmware again; if that fails I'd suggesting 
contacting Sipura for an RMA.

The one we had seemed heat induced.   It would work fine for a few 
minutes and then just die (but always still responded to pings).  No 
calls and no web interface would work until it was unplugged and cooled 
down.

I saw such wired behaviours on several SPAs. I think this is caused 
defect flash.

We sent our SPAs back and got a new HW Version.

regards
klaus

Steve Prior wrote:
> I just got a refurb Sipura SPA-2000 and was able to assign it an IP
> address with DHCP and ping the device, but then I ran the firmware 
> upgrade utility to bring it up to spa2k-2.0.13g which seemed to
> work just fine, but after it rebooted I cannot connect to its
> webserver for configuration.  I can still ping the unit.  When
> I use the built in voice menu it reads back the right IP address,
> webserver port, and claims the webserver is enabled, but I can't
> connect to port 80 on the device and running the firmware upgrade
> utility says that it cannot connect to the unit either.
> 
> Has anyone seen something like that and is there a fix?  A google
> search didn't turn up any apparent hits.
> 
> Thanks
> Steve
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
> 
>