Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: ralph on October 06, 2017, 09:52:29 AM
-
I'm just now digging into this so I thought I 'd bounce it off the group.
We seem to be observing at least two issues since upgrading to 8.0SP2.
1) After the upgrade the headset button doesn't work right away. We may have to turn it on and off several times before it begins working again.
2) Phones seem to lose their MAC address and return to "Enter Pin" screen.
Has anyone else observed these?
Ralph
-
Did the firmware update in the phones properly? Key issues and "lost" MAC address are common symptoms of a firmware mismatch.
Also, we have seen many cases after an upgrade where some phones go back to the Please Enter Pin screen, but only once, after being re-pinned they are fine.
-
Did the firmware update in the phones properly? Key issues and "lost" MAC address are common symptoms of a firmware mismatch.
Good question. I don't know.
I'll issue a load IPdevice command to see what happens.
Ralph
-
Did the firmware update in the phones properly? Key issues and "lost" MAC address are common symptoms of a firmware mismatch.
Good question. I don't know.
I'll issue a load IPdevice command to see what happens.
Ralph
Why not just look in IP Telephone Inventory and see what the versions are first?
-
Doh! You're right.
These are 5560 phones.
It's starting to look like it's a problem when the phones are remote and either it TW mode (without a TW Server) or hard coded.
As I write this, I wonder if it's possible that they didn't get their firm ware because it's using TFTP and the server may not have them as local networks. I'll have to check that out.
What about the headset's though? Have you seen that?
Ralph
-
Doh! You're right.
These are 5560 phones.
It's starting to look like it's a problem when the phones are remote and either it TW mode (without a TW Server) or hard coded.
As I write this, I wonder if it's possible that they didn't get their firm ware because it's using TFTP and the server may not have them as local networks. I'll have to check that out.
What about the headset's though? Have you seen that?
Ralph
I haven't that specific issue, but is that the only button that is "slow" to react? We are seeing some older CX controllers that are near capacity seem to dislike 8.0 as they lag a bit... especially with 5212/5224/5312/5324 sets.
-
Well, it's not a firmware issue. They're all the same.
Still working through it.
Ralph