AndyRothgen
IS-IT--Management
I've got a bit of a strange one here, it's happened on a few sets now and I'm not aware of any changes made that might relate to this.
The phones stop working and come up with InvalidTN. When I dig into it the S1 & S2 keeps resetting to our other phone system's server, I reset this correctly but the phone doesn't seem remember it properly. Due to the differences in the two systems this also means a firmware upgrade every time it swaps between systems.
I've done a factory reset using the '# up down up down up # 9 Hangup' from here This hasn't helped.
I believe the sequence the phone is following is as follows -
Set to correct S1/S2
Boots
Picks up firmware upgrade to 'nortel' this is correct for all phones on that system
Reboots on new firmware
Forgets S1/S2 and picks up firmware upgrade to 'avaya' for our other system
Reboots & comes up invalid TN as it's looking at the wrong server
The reason we've got two systems is we were historically two organisations who've merged and bought their own systems with them. However it's all functioned fine like this for around 10 years, this is a new issue.
The phones stop working and come up with InvalidTN. When I dig into it the S1 & S2 keeps resetting to our other phone system's server, I reset this correctly but the phone doesn't seem remember it properly. Due to the differences in the two systems this also means a firmware upgrade every time it swaps between systems.
I've done a factory reset using the '# up down up down up # 9 Hangup' from here This hasn't helped.
I believe the sequence the phone is following is as follows -
Set to correct S1/S2
Boots
Picks up firmware upgrade to 'nortel' this is correct for all phones on that system
Reboots on new firmware
Forgets S1/S2 and picks up firmware upgrade to 'avaya' for our other system
Reboots & comes up invalid TN as it's looking at the wrong server
The reason we've got two systems is we were historically two organisations who've merged and bought their own systems with them. However it's all functioned fine like this for around 10 years, this is a new issue.