January 04, 2022, 08:15:26 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Better Logging For OBI202  (Read 4597 times)
parimal24
Newbie
*
Posts: 3


« on: July 23, 2013, 08:27:54 am »

Hello Folks,

Reading all great reviews, I paid more $$ and choose Obi202 instead of Cisco and must say I have had nothing but problems. I am hoping to get support here as I have given up on Obi Support. Long story short, my device sporadically presents various issues: SP1 goes into unregistered, incoming calls lost, and today Register Failed: 486 Too many requests etc.

Each time I do a support ticket, someone emails me "it is fixed, we changed the  X_UserAgent port". Each time, no explanation given, just ports changed stating your router blocks it. I have requested several times for root cause analysis but nothing! I tried syslog but it does not log port changes to device - it is no use at all. Is there any other kind of logging I can do which will actually log something useful? Can some expert here point me in the right direction? I am technically savvy and can do any troubleshooting if pointed out. I would like to take this up from scratch and find out what is causing these issues. My router is not blocking anything as I have done a battery of telnet tests.

P24.
Logged
Shale
Hero Member
*****
Posts: 1061


« Reply #1 on: July 23, 2013, 09:03:54 am »

Is there any other kind of logging I can do which will actually log something useful? Can some expert here point me in the right direction? I am technically savvy and can do any troubleshooting if pointed out. I would like to take this up from scratch and find out what is causing these issues. My router is not blocking anything as I have done a battery of telnet tests.

You can put your OBi on the same hub (such as DS104) and use Wireshark to monitor the traffic. Wireshark has filtering to let you look for the packets you want to watch. It is not simple. http://wiki.wireshark.org/HubReference has a list of hubs known to work.

So it is at a lower level than syslog.
« Last Edit: July 23, 2013, 09:08:35 am by Shale » Logged
carl
Sr. Member
****
Posts: 453


« Reply #2 on: July 23, 2013, 08:48:39 pm »

I would try to keep it simple. Put your Obi into DMZ a try factory reset and start from scratch. Normally, configuring Google Voice should be a piece of cake even for a non techie. If there is a problem, you may want to return it and get a new one. Obi 202 is a great product. If GV works, you move on to SIP providers.
Logged
parimal24
Newbie
*
Posts: 3


« Reply #3 on: August 01, 2013, 02:43:54 pm »

So I called Obi Support "engineer" who after listening to my grievance, advised that he needs to escalate this issue to internal escalations team. I asked for a ticket/case # but he said they do not have any such system in place. I asked him to email me that Obi acknowledges they have received my request, he said someone WILL call you. I was loosing it but somehow kept my composure and asked I be copied on email to escalation team and the agent said OK and hung up. Needless to say...no email received!

As much as I would like to smash this unit to the ground, I cannot forget the OT I put in to buy this unit. What do u suggest I do now? Huh

I hope this is not their general support and that i got unlucky with a bad agent. Will try again  Undecided
Logged
Shale
Hero Member
*****
Posts: 1061


« Reply #4 on: August 01, 2013, 03:03:11 pm »


As much as I would like to smash this unit to the ground, I cannot forget the OT I put in to buy this unit. What do u suggest I do now? Huh

How did the WireShark work out?

Not going to take Carl's suggestion?

Does high drama work well for you in other situations?
« Last Edit: August 01, 2013, 03:05:11 pm by Shale » Logged
parimal24
Newbie
*
Posts: 3


« Reply #5 on: August 01, 2013, 05:17:56 pm »

Quote
How did the WireShark work out?

WireShark suggestion requires added expense (to buy a hub or another NIC for PC) and a bit of learning curve (first capture and then filter) - which I am willing to do as a 3rd or 4th measure - though a sure-shot method, troubleshooting should't start with it right?

Quote
Not going to take Carl's suggestion?

Usually a factory reset is done when nothing else works. When your PC/MAC hangs, do you format it to begin with? Plz. don't get me wrong, I thank you for suggestions and I will do those but I certainly cannot begin there and rid any changes of pin-pointing the issue for future avoidance. GV is my SP3 and does not have issues, it is SP1 (FPL) I have issues mostly with incoming call.

Quote
Does high drama work well for you in other situations?

My life does not allow me to spend time troubleshooting stuff - it's not worth it. I bought this device and expect it to work out of the box or with minimal config./time input. I'd expect the manufacture to support what they sell so proudly, not hang-up on customers, and if cannot help, at least prove it is not their product that is at fault!

I was looking for answers from experienced users saying "if it's these symptoms, check a, b and c, if its error code 486, then do this....etc". But I guess I am gonna have to dedicate a weekend to this now. Thanks for your pointers. I will let you know howd it go.
Logged
Shale
Hero Member
*****
Posts: 1061


« Reply #6 on: August 01, 2013, 06:05:23 pm »

Quote
How did the WireShark work out?

WireShark suggestion requires added expense (to buy a hub or another NIC for PC) and a bit of learning curve (first capture and then filter) - which I am willing to do as a 3rd or 4th measure - though a sure-shot method, troubleshooting should't start with it right?

I am not sure it would have helped.  I bought my DS104 via ebay at a good price, but that unit often commands a premium.

 
Quote
Quote
Not going to take Carl's suggestion?

Usually a factory reset is done when nothing else works. When your PC/MAC hangs, do you format it to begin with? Plz. don't get me wrong, I thank you for suggestions and I will do those but I certainly cannot begin there and rid any changes of pin-pointing the issue for future avoidance. GV is my SP3 and does not have issues, it is SP1 (FPL) I have issues mostly with incoming call.
Carl said "Put your Obi into DMZ a try factory reset and start from scratch." It is the DMZ that the important part. If you are convinced that your router is not blocking port access that the OBi202 is needed, then trying DMZ would not make sense. If you are convinced without testing, I think you should try to return the OBi202. On the other hand, if you are open to the possibility, then try DMZ. Even better, if your modem and router are separate, connect your OBi202 directly to the modem for testing. Reboot the modem so that the OBi can draw its IP. I really suggest trying at least one of those things.

Restoring to factory settings is probably not needed. However that process is not really like formatting a hard drive on a computer. Using OBiTalk, programming things to operational from factory reset is not a lot of work.

Quote
Quote
Does high drama work well for you in other situations?

My life does not allow me to spend time troubleshooting stuff - it's not worth it. I bought this device and expect it to work out of the box or with minimal config./time input. I'd expect the manufacture to support what they sell so proudly, not hang-up on customers, and if cannot help, at least prove it is not their product that is at fault!

I was looking for answers from experienced users saying "if it's these symptoms, check a, b and c, if its error code 486, then do this....etc". But I guess I am gonna have to dedicate a weekend to this now. Thanks for your pointers. I will let you know howd it go.

I did not recognize your symptoms. It was unclear to me where you were getting those error messages-- were those on the FPL website, or what? I searched for FPL and found it was also called Freephoneline. I wonder if the the problem is some kind of credentials thing. If you would like to search prior posts on this forum, I suggest using a Google search adding  site:obitalk.com to your search terms. That search is more effective than the forum's search function.

 http://www.obihai.com/FAQ.php does list various symptoms and actions.

GV is working for you. FPL is not. The problem sounds like more of an FPL or credentials thing, but it still seems worthwhile trying the DMZ or direct-to-modem thing.

 Getting lot of individual customer support technical support on a $100 item is not something I would expect.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Advertisement
Advertisement