Outgoing call rings but I hear white noise when answered -one phone number only

(1/6) > >>

bluemusestudio:
Obi202 works fine except in one specific situation: When I call my father, the phone rings and I hear it and he hears it. But when he answers, I hear white noise kind of like a fax machine. If my father calls me back, everything works fine. If I call him from my computer using the same Google Voice number registered to my Obi202 it works fine. If I call him from my Comcast landline or cell phone it works fine. I do not seem to have any problem calling any other numbers from my Obi202 excepts my father's Comcast digital voice phone number. Please help.

UPDATED November 3, 2018

Thank you for all your replies.

The problem still remains. It appears that it happens intermittently and changing the FaxDetectionMethod parameter did not fix it. Perhaps the most useful thing I can say is that the problem occurs only when I use my Obi202 with Google voice to call only my father's phone number. I have another phone line that uses Comcast digital voice and can call my father's number and the problem never occurs. There is an HP all-in-one printer with a fax line attached to my father's phone line and he has set the fax to pick up only after 6 rings, but when I call on my Obi line, the answer happens after the first couple of rings and I get the static sound that seems like a fax machine. I have asked him to disconnect the phone cord from his printer (and there is no answering machine attached), but I cannot confirm whether this was successfully done. He is elderly and it is difficult for him to reach and see behind the fax machine and he may not have properly disconnected the right phone cord (since there are two.)

I tried an experiment to see whether my Obi 202 would complete the call to my father if I called out on a different number. Like my phone 1, my phone 2 is also a Google Voice number. The main difference in set up is that phone 1 uses CallCentric for incoming calls so I can get callerID. To access my phone 2 number, I use the command **3 + the number I want to dial out to. When I call my father using phone 2 the call connects normally. But, one minute later, when I called using phone 1 when my father answered the call all I heard was the static white noise like a fax machine. I am not sure what this experiment proves. I wanted to see whether the Obi 202 and Google Voice services were the sources of the problem and it appears they are probably not. The only remaining variable would seem to be the unique Google Voice number associated with my phone 1. I would appreciate any insights forum member might share. Thanks!

SteveInWA:
Does he have an answering machine feature on his phone?  If so, can you try to get him to disable it and try your call again?  Same goes for a fax machine (e.g. HP OfficeJet, Brother or some other brand of multi-function device).  If he has one, unplug it and test again.

A_Friend:
Quote from: bluemusestudio on September 08, 2018, 07:24:30 pm

Obi202 works fine except in one specific situation: When I call my father, the phone rings and I hear it and he hears it. But when he answers, I hear white noise kind of like a fax machine. If my father calls me back, everything works fine. If I call him from my computer using the same Google Voice number registered to my Obi202 it works fine. If I call him from my Comcast landline or cell phone it works fine. I do not seem to have any problem calling any other numbers from my Obi202 excepts my father's Comcast digital voice phone number. Please help.


Here's something else to try:

On the Obi202, on the settings page under Physical Interfaces and whichever Phone Port you're using to place the call, in the Calling Features section, you'll find a setting called FaxDetectionMethod.  Change it to "disable" and see if that makes a difference.

SteveInWA:
The "FaxDetectionMethod" parameter only applies to inbound calls (a call coming into the phone number for the service provider configured on the OBi), not outbound calls.  The fix was/is to configure the fax machine properly:  if it is on a dedicated phone line (as would typically be the case in a business office), then set the fax machine to answer calls immediately.  If the fax machine is sharing a phone line with regular voice telephone calls, then set the fax machine to not auto-answer at all.  In the second scenario, the fax machine user would manually answer the call when it comes in.  Some fax machines can "peacefully coexist" with voice calls, by using...wait for it... fax detection on INbound calls.

So:  that setting had nothing to do with your issue.

A_Friend:
Quote from: SteveInWA on September 09, 2018, 07:43:33 pm

The "FaxDetectionMethod" parameter only applies to inbound calls (a call coming into the phone number for the service provider configured on the OBi), not outbound calls. 
...
So:  that setting had nothing to do with your issue.


Bear in mind that bluemusestudio describes the problem thusly:  He can call his father's number with any other phone other than the OBi device, even Google Voice from a browser, and he doesn't get the "static".  Only calling with the OBi does this happen. 

Presumably, whatever fax machine, service, etc. is online at his father's house is also there for the non-OBi calls.

So, what is it PARTICULAR to the OBi that is triggering this?

My guess was there was some fax handshake being passed/acknowledged by the OBi, appropriately or otherwise.  It's interesting that he reports success after disabling it. 

Some fax machines (and I've had a few) allow you to set a document to be remotely requested by another fax machine.  (Thereby turning an outgoing call into an incoming fax call.)  It's an obscure setting that I've never seen anyone use.  Maybe his father recently managed to press the wrong button, so to speak, and it's confusing the OBi.  Beats me.  But the problem was only happening with the OBi in the loop.  Which means, changing that setting may well have disabled whatever was causing the problem.  And, as long as he doesn't have a fax machine of his own, leaving it disabled won't hurt anything.

Navigation

[0] Message Index

[#] Next page