Help! 150 SE lost extension numbers after reboot! 2

[liquidshokk]

Have rolled out 150 handsets on a Server Edition in a data centre and just rebooted it after it being up for a few weeks and all the phones have lost their base/extension numbers!!

9.1.6 SE

Anyone seen this?? Can't have that every time we need to reboot the server!!

 

[liquidshokk]

75 handsets have come up when using MV_IPTEL.. really doesnt make any sense. All handsets are configured the same (using option 242) and are configured identically in manager so not sure why only 75 would come up

 

[liquidshokk]

I have upgraded the switches at each site and the number of phones registering is going up, but I can't get past 116 of 152 with all switches upgraded...

The switches are cisco SF200's and were installed with default configuration. Is there anything that should be disabled/enabled on these switches when installed that could help?

 

[IPGuru]

instead of repeatedly trying to reboot all hones simultaneously what happens if the customer manually reboots the handsets that don't come up?

it is less than Ideal but may get them working.


Do things on the cheap & it will cost you dear

 

[liquidshokk]

OK, I THINK i have got to the bottom of the issue. The IT co confirmed they had entered the DHCP option 242 incorrect, with spaces where there shouldnt be spaces and missing the VLAN test 0 at the end, presumably due to trying to copy and paste it to the DHCP server at each site.. Once this was correctly the phones started coming up normally, with some requiring a hard reboot or their base number re-entering as it had been wiped out. A reboot of the phone system resulted in all phones coming straight back up..

My question is whether an incomplete DHCP string would cause this to happen, and why not all phones were affected by this? I also upgraded the software on each of the POE switches too and upgraded the system to 9.1.8, so not sure if doing any of this also affected the outcome once the DHCP option was corrected.

Hope this helps someone else,

 

[IPGuru]

* for confirming the cause of the issue
I suspect that this will indeed help someone else in the future


Do things on the cheap & it will cost you dear

 

[liquidshokk]

Spoke too soon...

Rebooted the primary server tonight without secondary configured, handsets all came back up.

Added secondary server to primary config, rebooted primary and no 96xx handsets came up and I have been unable to get any up despite rebooting system, switches etc

Handsets sat saying authentication failure, followed by requesting extension and security pin.

I despair.

 

[sstevancevic]

Try to put

SET BRAUTH 0

at 46xxsettings.txt

 

[liquidshokk]

What does that do please?

Does that have anything to do with the secondary server specifically as the issue doesnt appear to be present with only one server connected... Do I need to edit the file on the secondary too?

Thanks

 

[derfloh]

That tells the phone to not have to authenticate against http server for phone config backup and restore but I don't see any relation to the issue described.

The auth failure described must be for H323 login against IPO service.

 

[liquidshokk]

What part does the phone password on the H323 extension play? I usually leave this blank, however when assigning an extension on the handsets I enter 1234 as the password. Could this be relevant? I have tried getting the handsets to re-register by putting 1234 into the extension config but wonder if its too late by that point.

Do others put a password on the extension in the config and the handsets themselves?

I'm guessing either way the handsets shouldnt lose their extensions just because a secondary server has been added? A single primary server can be rebooted time and time again and the handsets come straight back up..

 

[gknight1]

if you leave the password field blank in Manager you can enter anything on the phone and it will come up, even if you just push #. If you put something in Manager you will have to enter in the phone.