What follows is an incomplete list of leading vendors who are using the main protocols described in one of the previous blog articles: SIP and XMPP. This list is based on my personal knowledge. I apologize in advance for any exclusions.
The goal is to provide material for further analysis by the reader.
Cisco was one of the first to embrace the potential of Unified Communication systems and open standards.
Cisco historically selected MGCP and H.323 as VoIP protocols. SIP was later introduced, first on endpoints and then on servers.
Jabber, Inc., is a provider of presence and messaging software. It’s important to note that Cisco has acquired this company not the open standard Jabber (jabber.org). Jabber, by that point, had already been renamed to XMPP.
Continue reading “Overview of Platforms with SIP / XMPP Support”
Security is a serious topic and, unfortunately, it is either overlooked, exposing organizations to risks, or incorrectly addressed through cumbersome solutions. In the series of blog articles I will try to shed light on what you should pay attention to, in terms of security, when choosing a UC solution.
Notwithstanding all the advantages of a UC solution, there is one important prejudice against its adoption: security concerns.
There is a widespread belief that VoIP solutions based on SIP are not secure, and that their usage must be blocked, or at least limited to local networks (eventually extended by VPNs).
Nothing could be further from reality. Well-developed and deployed VoIP solutions that are based on SIP and XMPP are actually more secure than traditional communications.
How did the prejudice start and spread?
Continue reading “Introducing Unified Communications Security”