On 12/13/2016 11:02 PM, Roger Oberholtzer wrote:
On Tue, Dec 13, 2016 at 6:27 PM, Per Jessen <per@computer.org> wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2016-12-13 11:49, Per Jessen wrote:
Carlos E. R. wrote:
That was my thought too - you could run asterisk internally, but it's a bit of big gun for this.
And it is a target for attacks :-(
Everything is a target, but it's not a big deal - you get a lot of people trying to gain access to a SIP account, but it is so easily blocked. I've been running asterisk as our telephone system for at least 8 years. For Roger's purpose though, it's far too much effort to set up, I would say.
This is for communication with a computer and person in our measurement systems. They are usually on the road, and thus not on line. We will be using this when they are in for service in our garage that is 600 km from my office (hence all this nifty remote access). All machines are behind the corporate firewall. Which is another reason I would like not to involve a server. Unless my own openSUSE machine could server SIP information somehow.
We do have plans for getting these systems on line when on the road. But that will be limited to when we need access. And at that time we would need to be more careful of unauthorized access. But that is a plan for the future.
Many years ago, when we had an office in Alaska and another in Australia we ran a teamspeak server on our gateway Linux box. It worked well for both individual two person calls as well as conference calls. Teamspeak never did have the best security (it was designed for gamers) and anyone who could find such a server could coordinate calls on it. There were all sorts of love-birds using it late at night from what my server guy told me. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org