Author Topic: 5610 handsets and firmware.  (Read 3918 times)

Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
5610 handsets and firmware.
« on: September 27, 2013, 07:20:28 AM »
Will the new release 2.0 software work on MCD4.1 (release note says MCD 5.0 but...)

Alternatively can I downgrade handsets to 1.04...release notes says not.

Customer has MCD 4.1 (and out of swa and not really bothered about going back in) and a IPdect base unit and has managed to lose two phones and so we merrily order two new ones and yup the 2.0 (I assume) handsets won't work with the 1,04 base...showing incompatable firmware error... so I look to upgrade the base and come accross the release 5.0 issue...sigh.

Any one able to comment?


Offline martyn

  • Hero Member
  • *****
  • Posts: 688
  • Country: au
  • Karma: +10/-0
    • View Profile
Re: 5610 handsets and firmware.
« Reply #1 on: September 29, 2013, 06:50:41 PM »
Haven't tried it personally myself, but I can't see why it wouldn't. You may have some feature limitations or something, but the endpoints should still register and be able to make and receive calls, as at the end of the day it is all done via SIP, and that standard or way of registering hasn't changed between then and now.

Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
Re: 5610 handsets and firmware. tearing my hair out...
« Reply #2 on: September 30, 2013, 11:03:30 AM »
Anybody any idea what this means? I have tried everywhich way to upgrade this f****ing 5610 base unit but keep getting the below. tried it with phones registered, deregistered no programmming except to get the upgrade etc. etc....have tried to go from 1.0 to 1.04 as per the release 2 notes but still no joy...firmware downloaded from MOL. The second failure is from the absolute attempt to load the new firmware, the first being from a reboot...

FWU: UPANDRUNNING
0101010000 [N](01):FWU: AutoUpdCheck Start Abs time
0101010000 [N](01):Error Log Fp (count=0, assertline=0)
0101010000 [N](01): Fp0: err=0, task=0
0101010000 [N](01): Fp1: err=0, task=0
0101010000 [N](01): Fp2: err=0, task=0
0101010000 [N](01):Error Log Bf (a=0, r=0, keepalive=0)
0101010000 [N](01): Bf0: t=0, l=0, f=, d=0,0,0,0,0,0
0101010000 [N](01): Bf1: t=0, l=0, f=, d=0,0,0,0,0,0
0101010000 [N](01): Bf2: t=0, l=0, f=, d=0,0,0,0,0,0
0101010000 [N](01):GMT offset = 0 seconds
0930155550 [N](01): Time Synchronized with time server
0930155603 [N](01):FWU: DEVICE_NOTIFY_IND Device#0 State#0 PRESENT
0930155700 [N](01):FWU: DTSRV_ALARM_IND
0930155700 [N](01):FWU: DirList requested
0930155700 [N](02):FWU: loading DirList file: /sysro/tftp/DirList.txt from 192.168.1.5
0930155700 [N](02):FWU_STATUS_UNKNOWN
0930155700 [N](02):FWU: DirList load failure
0930155700 [N](01):FWU: DIR_LIST_CFM
0930155700 [N](01):FWU: Failed
0930155700 [N](01):FWU: FwuAppCleanUp
0930155700 [N](01):FWU: CLEANUP_CFM

Offline jrg0852

  • Sr. Member
  • ****
  • Posts: 309
  • Country: us
  • Karma: +3/-0
  • Look out for the next tech. because it may be you!
    • View Profile
Re: 5610 handsets and firmware.
« Reply #3 on: September 30, 2013, 11:32:50 AM »
It looks like the error comes after Dir. Could this be Telephone Directory related?

Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
Re: 5610 handsets and firmware.
« Reply #4 on: September 30, 2013, 12:25:27 PM »
Doubt it as this is a straight TFTP operation....

Offline x-man

  • Hero Member
  • *****
  • Posts: 1129
  • Country: gb
  • Karma: +25/-0
    • View Profile
Re: 5610 handsets and firmware.
« Reply #5 on: October 03, 2013, 08:35:22 AM »
OK, we managed to get the customer working but we had to get a new base unit as well in the end (which was supplied from Mitel with older software than the handsets...1.04 on the base 2.0 on the handsets) which still left us with the quandary that it wouldn't poll the tftp server. However a colleague noticed that in the settings it was doing http rather than a TFTP and that needed changing in the settings above the update settings (no mention of this in the Mitel instructions). Did that and set it to poll and it upgraded from the tftp server fine to version 2.0.

The original base station however will not poll for an upgrade. Whether this is because it has nothing connected to it I am not sure. It starts fine but will not poll for an upgrade. Life is too short to worry about it too much since we have the other one working.

Don't know if all the options work on 4.1 but calling out and in and transfer works and that's all the customer needs.


 

Sitemap 1 2 3 4 5 6 7 8 9 10