Mystery reboots Obi 110 build 2774
ProfTech:
Hmmm... That is mildly interesting. I have CallCentric on sp1 for 2 years with no problem until now. I have CallWithUs on sp2 but it is set to not register. And Obitalk is enabled. I am only currently testing CallWithUs so could easily disable it but don't have much faith that will change anything since it isn't even registering and I don't have DID with them. It would be nice if they told us what code 94 is actually supposed to mean.
CoalMinerRetired:
I'm getting beyond mildly annoyed by this, .... the reboots and the suggestion to try the divide and conquer approach).
I was away all of last week, and detected one reboot, and one unknown instance of I can't determine what happened because the status via ObiTalk portal was mixed up. Then after five days of uninterrupted uptime (and notable with zero calls placed and answered), and then one short call received this AM, I got a reboot an hour or two after the received call. So I guess I start the selectively disable two of four SPs and see what happens.
CoalMinerRetired:
A 12-day update.
Using the divide and conquer approach, I have two (of four) SPs configurations disabled. Both are for Callcentric (with the CNAM with GV arrangement), and two GV SPs enabled.
Uptime has been 12 days so far, that exceeds any prior uptime duration (on this firmware release), so the obvious culprits are the two CallCentric SP services.
The devices behavior has not been 100% perfect these 12 days, though. Today I had an active call change into dead air. This is about the fifth or sixth time in as many days it happened. I'll be on a call, anywhere from 60 seconds to 15 minutes into the call the other party and I stop hearing each other.
There is no clicking on the line nor is there a hangup. In fact, I cannot disconnect the call, placing the handset down on the hook has no effect, the Obi ignores this signal and maintains the call still in progress, ... I cannot disconnect via the hook, no matter how many times I press the hook. All the while I see the Phone 2 phone port light flashing, indicating the "The phone is in use," and at the same time the Obi WebPage is un responsive, therefore I cannot do a "Remove" under the Status > Call Status to end the call. As a side note and curiosity, I see that "Remove" records the call as "Call Ended" by both parties, both columns, in Call History.
I chose not to reboot, and to wait it out and see for how long the Obi took to become responsive again. In today's case it was 60 to 90 seconds until the call hung up and I could place call again. Curiously, the Call History showed the call was ended by my phone, not by the other end.
And to add to the symptoms, today when I placed a follow up call (back into the ongoing multi-party conference call), there was an enormous amount of echo on the entire call, whoever spoke had a bad echo. After a few minutes I became suspicious I was causing it, I dropped off and dialed in again and the echo was gone. Other parties did the same so we're not sure who caused it, ... but I'm suspicious it was caused by my end.
So my next step is to re-enable the Callcentric SP services, will report back again.
ProfTech:
It sounds like from yours and other posts that the 202 firmware has some issues. I can sympathize. I owned my 110 for about a year before the firmware was fairly solid and worked like it was supposed to, and mine was not one of the first units off the line. They were about 6 months into sales when I purchased. FWIW, Obi loaded 2776 into my unit. I disabled CallWithUs for the time being and my unit seems to be more stable now. Still using CallCentric on SP1. But I have made a few other minor tweaks along the way so hard to say what was actually going on. Stay tuned...
CoalMinerRetired:
I reached the 14 day uptime milestone today. So I decided to carefully re-enable both Callcentric SPs.
Did so via the ObiTalk wizard for Callcentric. After doing so, made a few minor (from my pov) expert mode changes: for both CC SPs unchecked skip call screening ('cause I'm doing the GV & CC with CNAM thing), and for one of the two SPs (SP2) had to change the ring Profile to A, and default_ring to 7. Strangely, SP2 defaulted to Codex Profile B and Ring Profile B, whereas SP 1, 3 and 4 default to profile A.
By my count I have the two suspect Callcentric SPs now setup with only four small tweaks that vary from the ObiTalk portal wizard.
I hope the next update I add to this thread is to report success. If not I'm going to seriously consider giving up.
Navigation
[0] Message Index
[#] Next page
[*] Previous page