Hi folks-
My OBi202 was acting up after almost 2 years of solid operation and I discovered the GV XMPP cutoff was approaching.
Figuring it had something to do with this, I signed up for PhonePower and replaced my GV SP1 with it via auto provisioning.
Same scenario - trunks light up regularly/randomly on the Avaya IP500 it is attached to.
Thinking the device was failing, my second one died about 8 months ago, I ordered a new OBi202 and replaced the unit and power supply.
Same scenario except it was now also rebooting regularly with reason code 6.
Powered down and removed the BT dongle as it was the only thing that did not change.
Same scenario.
Went into web admin and saw "Reboot required" and clicked on reboot.
Now I have the check mark for Config Current, but it's still pre-alerting even though I have 2+ solid days of uptime.
Any ideas on how to fix this ?
It hasn't happened while on a call, yet, but clearly something isn't right. Thanks-Jake
Additional info
HardwareVersion 1.4
SoftwareVersion 3.0.1 (Build: 4330)
Service Providers always shows
SP1 OBi PhonePower Registered
PHONE Port Status
PHONE1
State
On Hook
LoopCurrent
0 mA
VBAT
56 V (11.8 V)
TipRingVoltage
45 V
PHONE2
State
On Hook
LoopCurrent
0 mA
VBAT
56 V
TipRingVoltage
45 V
Trace of trunks on switch
4/14/14 1:27:17 PM-575ms Line = 2, Pre-Alerting
4/14/14 1:27:17 PM-576ms Line = 3, Pre-Alerting
4/14/14 1:57:17 PM-438ms Line = 2, Pre-Alerting
4/14/14 1:57:17 PM-439ms Line = 3, Pre-Alerting
4/14/14 2:27:17 PM-999ms Line = 3, Pre-Alerting
4/14/14 2:27:18 PM-000ms Line = 2, Pre-Alerting
4/14/14 2:57:17 PM-733ms Line = 2, Pre-Alerting
4/14/14 2:57:17 PM-734ms Line = 3, Pre-Alerting
4/14/14 3:27:18 PM-174ms Line = 2, Pre-Alerting
4/14/14 3:27:18 PM-175ms Line = 3, Pre-Alerting
