rossiv
Guru
- Joined
- Oct 26, 2008
- Messages
- 2,624
- Reaction score
- 139
I was installing a new switch in my network closet at home (POE!) and I conveniently failed to notice that my Aastra 9133i was in the stages of rebooting after a firmware update when I unplugged the old switch. I was able to get it into Web Recovery mode, but when it tried to t*f*t*p the firmware file, it always errored out with unspecified error or some such. I just moved it to an isolated POE switch and it just sits at "Aastra 9133i" even if I hold down the 1 and # keys to force a web recovery. Ideas anyone? I know it isn't the t*f*t*p server because I have tried the one in PIAF, TFTPD32, and PumpKIN as well all with different firmware files and none of them worked.
Code:
PBX in a Flash PURPLE Status
─────────────────────────────────────────────────────────────────────────────────────────────────────────────
┌────────────────────────System Information───────────────────────────┐
│ Asterisk = ONLINE | Dahdi = ONLINE | MySQL = ONLINE │
│ SSH = ONLINE | Apache = ONLINE | Iptables = ONLINE │
│ Fail2ban = ONLINE | Internet = ONLINE | Ip6Tables = ONLINE │
│ BlueTooth = ONLINE | Hidd = ONLINE | NTPD = OFFLINE │
│ SendMail = ONLINE | Samba = OFFLINE | Webmin = ONLINE │
│ Ethernet0 = ONLINE | Ethernet1 = OFFLINE | Wlan0 = N/A │
│ │
│ PBX in a Flash Version = 1.7.5.6 Running on *HARDWARE* │
│ FreePBX Version = 2.8.1.4 │
│ Running Asterisk Version = 1.8.6.0 │
│ Asterisk Source Version = 1.8.6.0 │
│ Dahdi Source Version = 2.5.0.2+2.5.0.2 │
│ Libpri Source Version = 1.4.12 │
│ IP Address = 192.168.4.2 on eth0 │
│ Operating System = CentOS release 5.6 (Final) │
│ Kernel Version = 2.6.18-238.9.1.el5 - 32 Bit │
│ │
└─────────────────────────────────────────────────────────────────────┘