hawkflorida
Technical User
On a BCM400 3.6s/w.
When additional i2004 sets are installed the new sets are rebooting. The set information on them, such as DN number, name and line assignments etc... comes up. They stay up for about 2 seconds and then the set reboots. Other IP sets are functioning fine. But none of the functioning sets are this version i2004 which is NTDU92 BA70 06. Any ideas would be helpful.
Note: They are using POE which is working fine with the other sets. Identical programming of set parameters being used for old and new.
BCM 3.6 Build 3.1a
IP client keycodes are adequate for the number of units
Applied patches
BCM_360.130_Cummulative.99.2
BCM_360.179_SETFW.56.89
BCM_360.180_WIN.00.893066
BCM_360.198_WANDVR.17.250
BCM_360.160_VM.22.0070
BCM_360.186_CORE.08.0612
BCM_360.156_RCC.61.047
i2004, NTDU92 BA70 06
Other i2004 sets are functioning fine but none of them are the NTDU92 BA70 06 type.
Consulting -
"If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem."
When additional i2004 sets are installed the new sets are rebooting. The set information on them, such as DN number, name and line assignments etc... comes up. They stay up for about 2 seconds and then the set reboots. Other IP sets are functioning fine. But none of the functioning sets are this version i2004 which is NTDU92 BA70 06. Any ideas would be helpful.
Note: They are using POE which is working fine with the other sets. Identical programming of set parameters being used for old and new.
BCM 3.6 Build 3.1a
IP client keycodes are adequate for the number of units
Applied patches
BCM_360.130_Cummulative.99.2
BCM_360.179_SETFW.56.89
BCM_360.180_WIN.00.893066
BCM_360.198_WANDVR.17.250
BCM_360.160_VM.22.0070
BCM_360.186_CORE.08.0612
BCM_360.156_RCC.61.047
i2004, NTDU92 BA70 06
Other i2004 sets are functioning fine but none of them are the NTDU92 BA70 06 type.
Consulting -
"If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem."