Defective Obihai?
johnny.medellin:
I’m not using the COT method because eventually someone else will be using the OBI unit I have in the US. That’s why I want to keep them independent. I currently have both because I’m in “Testing” mode. I currently have only GV #s, no SIP SPs, and yes, I do have separate GVs on each box (I’m no expert, but I’ve been dealing with SIP/Asterisk for a few years so I kinda know my way around). I’ll check my codecs, although I haven’t touched them since I got the units. Remember also that I copied the configuration on the “suspect” OBI (the one in Colombia) and loaded it onto my US unit, and it works perfectly in my known good unit. Also remember that my calls are random, sometimes they’ll go through, and sometimes not.. both incoming and outgoing.
I used VNC, but I’ll try to connect to the Obi directly tonight, I guess with all the problems I didn’t think of that. Thanks for the advice. BTW, for whatever reason, the Expert configuration portal through OBI is giving me problems too. I access it just fine and can make whatever changes, but for whatever reason those changes do not get reflected in my actual unit; that’s one oif the reasons why I just started VNCing to it. That and also because I like to monitor my phone calls while troubleshooting and because I want to be able to save configuration files while testing (I didn’t see a way to do those two things through the Obi website)
Regarding the “cannot connect” blank page I get, I get this error message on the Obi page only, meaning while trying to access 192.168.1.xxx on the PC I connect to. My actual VNC connection to the PC is always active and alive! By the way, You might be thinking, “well, maybe he gets that message after just rebooting the unit” to which I say, nope, it happens all the time, and at random, sometime I would be able to see one OBI page (i.e. SIP1) but when I try to go to SIP2, I would get the “cannot connect” message. To continue answering your questions, Yes, I’ve been able to have 2-way calls. But everytime except once, they stop hearing me. I can always hear them. Only once was I able to talk for more than an hour without interruptions. Oddly enough that happened after several other “cutoff” incidents and without me making any changes. Later that day the cutoff incidents came back… That’s why I keep saying Random, and that’s why I think I got a defective unit, which is just screwing with my head Sorry about the long message, I just wanted to answer your questions and post as much info as possible to help in troubleshooting
QBZappy:
johnny.medellin,
Hi, I've seen a few posts here with people having the OBi randomly rebooting. Can you ask someone in Colombia to confirm if the unit is indeed rebooting by itself? You can also see the up time on the unit. That will give you an indication and a code specifying a reboot reason. If that is the case you might want to review some posts with OBi randomly rebooting. I think RonR has has responded to a few questions related to that issue. He might want to chime in on that.
BTW, testing copies of the config on your local OBi would not absolve codec being an issue between the units, since I presume you were testing local unit with local calls.
For the Expert configuration portal changes to stick you need to enable auto provisioning:
System Management>Auto Provisioning>Method = Periodically/system start
The Expert configuration portal is not as complete as the OBi web page. It allows for configuration but lacks in the ability to verify the call history, as you observed, in order to troubleshoot an issue. This has been brought up before. If you set up the autoprovisioning you will need to configure only from the Expert configuration portal . That setting forces you to choose one configuration strategy over the other. You can not use both methods at the same time. At the moment the OBi web page method via port forwarding offers more troubleshooting options.
A while back there was some mention about some browsers not working properly with the OBi web page. I have not seen any recent mention about this. Anyways if you want to connect to the OBi web page, a direct connection via port forwarding will answer that question quickly enough. I have never had any problems with Firefox connecting to the OBi web page.
Have another go at it. You can send OBi support an email with a link to your thread. I've seen some good comments about their efforts in resolving client issues. In the end it might just be that you have a defective unit.
Good luck. Keep us posted.
Navigation
[0] Message Index
[*] Previous page