For added clarity, I have a technical team available (assuming I don't
distract them from their regular tasks) as well as access to significant
computing capacity on our own cloud. Our technology stack is PCI
certified and members of our group are expert in systems security (but
Excellent! It sounds like you definitely have the technical ability to
adequately evaluate this product to meet your security needs. Also, I
suspect Jitsi will fit in very well within your infrastructure and not
cause many (if any) problems with your current security.
Before I go distracting anyone else in our group, I'd like to have a
better understanding (in layman's terms that can be clearly explained to
other non-technical business people in our sphere) of what options we
have for net-based internal and external communications. I believe that
my having a better understanding will allow me to be somewhatn more
useful in the process and allow our group to focus and implement faster
(reduce meeting cycles).
It would be best if the technology we choose could communicate with
common third party systems and devices (e.g., VoIP via SIP, etc.) but
automatically default to the highest security/privacy comms when
communicating amongst ourselves. It would also be highly desirable to
communicate securely/privately across IP-enabled mobile phones, IP
deskphones, tablets, and notebook/desktop computers.
Since you have a mixed communications scenario (both internal
communication and external, by phone, communication), I'd strongly
recommend that you look at implementing SIP. A properly implemented SIP
system will allow you to do everything you want to do (instant
messaging, file transfer, presence support, internal calling, external
calling via the telephone network, encryption of voice and video chat
(with certain limitations, of course).
SIP is also a very well understood and supported technology that is
widely deployed in businesses and is compatible with an extremely wide
range of hardware and software including ANY kind of telephone hardware
(both traditional and VOIP). For example, you could use SIP in the
office with your a combination of your favorite VOIP software (like
Jitsi) and your favorite VOIP telephone hardware to make and receive
calls both internally and over the regular phone network. AND you could
use it at home, for example, with a $10 regular phone you bought from
Walmart to do the same. It's incredibly flexible.
My argument for your case would DEFINITELY be SIP over XMPP or other
We are very aware of various rules and regulations levied on many telco
services providers (e.g., CALEA) as well as the numerous privacy and
security breaches of too many of the big name net services providers.
The internal consensus is that the best option is to run our own systems.
Absolutely. While there are MANY SIP providers out there, if you are
concerned about having the most security (as well as flexibility) you
will want to run your own system. They aren't hard to set up and run at
all. Take a look at Asterisk for example. It can be set up in an
afternoon and can be used for everything from a simple home phone system
to the backbone of a multimillion dollar communications network.
PS: On reading your generous reply, I realize that my understanding of
all the pieces used to implement Jitsi is unclear. Is there a detailed
overview of the technology stack and how it all fits together?
I'm not aware of any one stop shop for that kind of thing (Digium might
have something but I don't know). Perhaps someone here might know of a
good place for you to start. In fact, the Asterisk site might have some
of that stuff as well so check there. I'll dig around and see what I can
find and forward it to you off-list when/if I do.
Anyway, I hope this helps. If you have any questions, please feel free
to reach out.
On 02/05/2015 11:28 PM, Roland Schoettle wrote: