obi202 needs to be rebooted at least weekly for ip phones to call out
evergreen:
Thanks, RFC3261 for the help. I think your response gave me something to bounce off of since I wasn't sure what level of detail would be appropriate for troubleshooting this matter the next time my phones acted up. So now, my phone is having this issue again and I jotted this information down before rebooting:
Obitalk dashboard
SP1-SP4 as registered with no issues
Obi202:
System Status:
Obitalk service status:
Status: Acquiring Service (0);ex-addr=76.234.229.234:10075(10075)
CallState: 0 Active Calls
Call History:
Fork to:
PH1
OP1(101);(Failed: No Service)
OP1(100);(Failed: No Service)
OBiPLUS status:
(ip address of IP phone 1) -> Ext 1 Status -> Registration state: Failed - No Response
(ip address of IP phone 2) -> Ext 1 Status -> Registration state: Failed - No Response
One thing that I've noticed that while internal communication between IP Phones is down, I can still dial out and receive calls using phones connected to PH1 and PH2.
Hopefully, this contributes a bit to the conversation and isn't a mere longhand repeat of what you had just stated, since I didn't fully understand your diagnosis and possible solution regarding setting up a span port. I'm wondering if your solution is fairly easy to implement and if you've tried it out with some success. Thank you everyone!
azrobert:
You can try pointing your IP Phone directly to your OBi without OBiplus. The phone doesn't register to the OBi, so turn off registration. If the phone doesn't have a no registration option it will fail to register, but still might work.
See: http://www.obitalk.com/forum/index.php?topic=6865.0
RFC3261:
Quote from: evergreen on July 18, 2014, 12:29:04 pm
... So now, my phone is having this issue again
While I do not know the exact time, my IP phones also failed about mid-day, losing SIP registration. I am starting to suspect that the OBihai servers (running on AWS, last I checked) experienced a "glitch", resulting in some set of individuals to experience the loss of ability for IP phones to continue registration.
I wonder if paid OBIPlus customers are seeing the same issue? Perhaps I am getting what I paid for? I am sort of hoping OBihai will release fixed firmware, but if not, I guess I will have to consider installing FreeSwitch or Asterisk on my BBB to stop these annoying outages. One more job to add to my infinite to-do list....
evergreen:
IQuote from: RFC3261 on July 18, 2014, 02:43:29 pm
Quote from: evergreen on July 18, 2014, 12:29:04 pm
... So now, my phone is having this issue again
I am sort of hoping OBihai will release fixed firmware, but if not, I guess I will have to consider installing FreeSwitch or Asterisk on my BBB to stop these annoying outages. One more job to add to my infinite to-do list....
yeah, I thought it might be firmware related, either on my obi202 v1.4(3.0.1 (Build: 4350)) or my Cisco SPA504g, but they seem to be up to date. I had two more mini outages today and it's happening less regularly and more sporadically now. I'm not sure if I should report an outage here just to compare notes or what. Would installing Freeswitch or Asterisk be another free solution meant to supplement obiplus or are those complete replacement solutions?
RFC3261:
Quote from: evergreen on July 21, 2014, 06:05:28 pm
yeah, I thought it might be firmware related, either on my obi202 v1.4(3.0.1 (Build: 4350)) or my Cisco SPA504g, but they seem to be up to date.
My guess of the OBi firmware is that there is a bug there (not that it is not the latest) with communications to the OBi host in the cloud that results in the OBi device not continuing to serve the IP phones. My test POTS phone continues to work fine during the period. The observation is that the IP phones registration packets are being ignored. Whether it is a license issue, or something else, is just conjecture. Since OBi does not provide support via the forums, I do not expect any real updates or acknowledgement of issues. I have sort of waited for a new firmware image in the random hope that the issue might get fixed. But my patience is starting to come to a middle.
Quote
I had two more mini outages today and it's happening less regularly and more sporadically now. I'm not sure if I should report an outage here just to compare notes or what. Would installing Freeswitch or Asterisk be another free solution meant to supplement obiplus or are those complete replacement solutions?
I also had a few outages today.
Asterisk/Freeswitch are complete replacements (for the OBi). I would have to build a Linux image for my ARM based system, and build and run Asterisk and/or Freeswitch, and do the configuration there (which is somewhat harder than the OBiPLUS solution, although there are GUI tools to do it). I believe the OBi is an ARM based system too, but it is a "black box" (which is also a bit grey :-). Since I only use IP phones (I just keep a POTS phone for testing), I do not really need the OBi202 Ph/Li ports, making a move to a (new) dedicated system easier for me (if one has real POTS needs, you would need to keep the OBi as part of the solution for its FXO/FXS capabilities). I prefer to use the OBi and OBiPLUS, but if it continues to be unreliable (as it appears to be), I am going to have to consider doing the work to change to another solution, and retire my OBi202. That will be a sadness, but times change.
Navigation
[0] Message Index
[#] Next page
[*] Previous page