NEC DT730 NEC-SIP to SIP - Download Signature Failed 1

[np247]

Good morning,

I have an NEC DT730 (which I recently converted using files acquired by the usual means (thanks again)).

Despite everything showing successful -- upon reboot, it waits on LLDP, initializes DHCP, I can access the "Menu" -- login as admin, etc. -- but after a couple of minutes I'm prompted with "Download Signature Failed. Reboot Pending..." (photo attached).

I've tried re-flashing using IPPhoneManager, I've tried resetting everything back to factory defaults -- but the same thing keeps happening. It's basically in a bootloop as a result.

The phone was on NEC 05.00.07.00 and is now on SIP 02.03.109.04.

Additional backstory:
- While on NEC - IPPhoneManager would not allow me to flash -- I was stuck on the "Download" screen; it would error out and say "You have to select at least one available IPPhone" regardless of what I did/tried
- I ended up trying to use the phone to perform the upgrade -- I changed the filename from "itlisipv.tgz" to "itlissipv.tgz"/TFTP/TFTP address and hit Download
- Flashing went successful -- but I wonder if this process is what "broke" it?

If anyone can offer any assistance, I'd be greatly appreciative. Thank-you!

 

[np247]

I fired up my old T42 running Windows XP, installed IPPhoneManager+Pumpkin and retried the upgrade process using IPPhoneManager with the original phone - same issue. Signature Error.

Alright, so I wanted to rule out my manual TFTP upgrade escapades (and Windows 10) as an issue here.

I grabbed a second DT730 and tried it 100% using IPPhoneManager, and despite it (and Pumpkin) showing everything as successful -- I am stuck in the aforementioned "Signature Error" again.

The file I'm using is called: DT700_v2.3.109.4_DT730G_v3.1.61.9_DT820_v4.4.11.2_DT900_5.3.4.0_STD-SIP_FW.zip and IPPhoneManager is grabbing the itlissipv.tgz file -- which makes me think everything should be OK.

(I did hit the checkbox converting from NEC to SIP)

Again, any help would be greatly appreciated. This is more annoying than anything, just because I feel this *should* work.

If anyone has access to older files, or NEC firmware files, I'd absolutely love trying those as well -- otherwise I'm running out of ideas.

 

[np247]

Going down the rabbit hole here, I have a new working theory -- the phones are fine.

If I unplug the phone from the network, I realized I no longer get a "Signature Error". I suspect the phones were both trying to reach out to a non-existant server (or an existant server with an invalid configuration) and complaining as such.

I've factory reset the phones, unplugged them from the network -- disabled LLDP/DHCP and hard coded an IP address. I can ping it locally.

I have a VoIP.ms account, so I tried registering the phone with using the Polycom documentation as a template -- but regardless of what I have configured (or not configured) -- I still get the same "DHCP Complete" status message on the screen. I've taken PCAP's on the firewall (and done a port mirror) and it doesn't even try and reach out externally.

What am I missing here? My only option is "Exit" -- which just reboots the phone, which brings me right back to this same screen.

 

[np247]

Good monring,

Thank-you belevedere and gjstroom. Without your help, I would still be pounding my head against the wall.

I was able to successfully convert my DT730 to SIP F/W to "NEC Std SIP 2.3.109.4" and use it to make both inbound and outbound calls using VoIP.ms. Tested -- works well. I still need to finesse the configuration (and documentation is sparse, so trial and error FTW) -- but it does work.

The biggest gotchas I encountered are:
1. Once flashed, the phone is exceedingly dumb. No web interface or simple configuration -- config, ringtones, updates, etc. --- everything needed is pushed out through a TFTP server on boot. You _need_ them all -- without it, the phone will sit and do nothing, as I learned the hard way

2. Unless you specify the DHCP option for the aforementioned TFTP server you will end up in a boot loop. I suspect my issue was the NEC phone was seeing my actual production phones TFTP server option and trying to use that -- which was causing my failures -- which leads perfectly into #3

3. There is a section under "ADMIN" you can go into and specify the source of the configuration. By default, it is set to DHCP. To work around my issue, I needed to change this to "Static" and manually tell it the IP address of the appropriate server

I hope this helps someone in the future.

Cheers