PSTN interface issues

I have a fancy box that implements a "voice attendant" for our home phone. Colleagues have duplicated it for use on their home and office phones (whether land line or VoIP).

Recently, a colleague tried to implement it on a cell phone line using a box like this:

as a bridge/gateway between the cellular network (with his cell phone acting as intermediary). He's had all sorts of problems. :<

Given the successes others have had, I suspect the problem lies in the bridge device.

As I've not yet designed my own telco interface (using a COTS FXS), my interest lies in determining whether there is some "enhanced" set of POTS specifications that *my* FXS should embrace... or, if this is just a "suboptimal implementation" -- in which case, my colleague is SoL.

The device referenced should be simple enough to implement. I'd imagine the online comments I've seen about it (low volume, weak ringer, garbled sound, etc.) are likely consequences of designing "on the cheap" and/or relying on stealing charge current from the cell phone's charger/power source.

Anything I should have him look at, specifically? Or, pointers to another COTS solution (or, an open-hardware implementation!) of something similar that he could pursue? Or, just let him wait until I come up with a fresh implementation (LOW on my priority list as targeted users have tethered lines)

Reply to
Don Y
Loading thread data ...

Glad you listed all the problems the guy ran into. It really helps troubleshoot the issue he's facing.

Reply to
Cydrome Leader

Had you CAREFULLY read what I'd written -- along with the reviews of the item at the URL posted (I'll assume you're too lazy to actually chase down the manufacturer's web site for even more info) -- you'd infer the sorts of problems he's had.

And, the sorts of problems OTHERS HAVE NOT HAD, despite using a variety of different PSTN "hooks" to connect to the COTS hardware that I've used.

Hint: the problem lies in the "device" mentioned in the URL.

But, I don't expect your imagination to extend beyond what's placed under your nose...

Reply to
Don Y

Yes, I'm too lazy to do research for a guy who is too lazy to tell us what the problems are. If you care to share, I might be interested enough to read the link to an Amazon listing (as if they often have much useful info.)

--

Rick C. 

---- Get 1,000 miles of free Supercharging 
---- Tesla referral code - https://ts.la/richard11209
Reply to
Rick C

No thanks.

So your trash and the junk off amazon aren't compatible. I'm truly shocked.

Well have fun with your project.

Reply to
Cydrome Leader

So, any "help" you could have offered would have been largely speculation; not rooted in prior experience. He (and, eventually, *I*) will be the wiser for exploring the issue, while your laziness will keep you ignorant.

My "trash" is actually some other COTS device that has a proven track record (thousands of Asterisk installations motivated my initial selection of that hardware). And, the fact that it (as a system) has worked without any problems with the PSTN (in various communities around the country; not tried abroad, yet) as well as other FXS implementations (e.g., VoIP gateways) validates the design, to some extent (at the hardware level).

So, the Amazon device is the culprit -- as suggested by the reviews on that device (and the implementation details available on the manufacturer's site). As I said below...

Not my project -- his! I can't warrant a noncompliant device will work with a system designed against *real* specifications! Wanna bet the device can't drive a "real" phone load?

He's a big boy; he's got at least the same types of diagnostic kit that I have so I'm sure he'll sort it out. Whether he actually delves *into* the "adapter" to determine where the design is "lacking" will be up to him and his level of curiosity. If he *doesn't*, I'll likely buy one just to tear apart and learn what *not* to do!

But, it *does* suggest another design opportunity... :>

Reply to
Don Y

Does "fancy box" translate to a computer running software, e.g. Asterisk, or something more proprietary? (Radio Shack made some interesting proprietary things in the '80s and '90s.)

Without knowing more about the problems that he had, I can't speak to them.

I'm assuming that the device connects to the phone via Bluetooth.

I am quite certain that Asterisk supports connecting to things (cell phones) directly via Bluetooth. As in you can put a (supported) USB Bluetooth dongle in the computer, load the proper drivers, and configure Asterisk to use it as a channel. (I think "channel" is the word that I want.) There's no need for such an external Bluetooth to B1 gateway.

My problem with the B1 is the lack of /good/ signaling across it. You basically have current and voltage.

The fact that Caller ID comes between the 2nd and 3rd ring basically means that you can't do anything based on or with Caller ID until after the 3rd ring on the B1. What's worse is that by the time the 3rd ring happens on the inbound B1, there's a very good chance that the caller has heard four or five rings on their end. So ... timing becomes a problem.

I'd suggest bypassing the external box and putting Bluetooth directly under Asterisk's control.

--
Grant. . . . 
unix || die
Reply to
Grant Taylor

Glad you have a sidekick and ameritec line test and simulator test set laying around like I do. No doubt, you'll be able to say PSTN another 25 times and just research your way out of this one.

Reply to
Cydrome Leader

You still don't get it -- it's not *my* problem! I can demonstrate that I can drive (and be driven by) a PSTN signal. Other folks (e.g., the Asterisk crowd) can similarly vouch for the hardware that I'm currently using.

By contrast, other folks have COMPLAINED about the amazon device's compatibility with their COTS phone devices.

The problem is, thus, that of the amazon device. I have no obligation to figure out (FOR THEM) why their product is deficient. My colleague will sort out why it's not working FOR HIM. And, if he can find a workaround, he'll adapt. If not, he'll likely just discard the device as yet another "product with shortcomings" and look for an alternative -- even if it is more costly.

He has the benefit of KNOWING that others have had no problems with my box -- or the hardware upon which it is based (/cf./ Asterisk). And, the "evidence" of problems reported by other users of that amazon device.

Reply to
Don Y

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.