toggle quoted messageShow quoted text
Ok, thanks for the detailed explanation. I know understand the traffic related issues that may arise.
Looking at my specific situation I would like to be able to share my AmbeServer with another Ham. Which seems to work fine so far. However I have been aware of his use and when. The problem lies in that when do we know when the server is currently busy? I guess we don't.
Ok thanks again and this provides yet another optional use for my ThumbDV!
Sent by pressing a send button.
On Nov 14, 2017, at 3:00 PM, John D Hays - K7VE <john@...
The AMBEserver has nothing to do with connecting to various protocols, reflectors, etc. That is all handled by the client software, eg BlueDV. ThumbDV/AMBEserver only has one function: take in PCM encoded audio and return AMBE or take in AMBE and return PCM encoded audio (to the client).
Again, it is a simple system, it gets a PCM packet from a client and returns an AMBE packet to that client, receives an AMBE packet from a client and returns a PCM packet to that client. A single AMBE-3000 chip handles a single stream, and having multiple clients would divide that stream up between the clients in an unpredictable way. The AMBEserver doesn't have multiplexing capability. If you are asking if you can use the same AMBEserver by different clients at different times, that works just fine -- simultaneous use is going to have problems.
Ambed, by the folks who are doing the XLX reflectors, handles multiplexing multiple streams to multiple AMBE devices on a timeshared basis, that is currently only supported by the XLXd service.
We are contemplating kick-starting a multi-ambe device for such applications as Ambed.