Most understand what SIP (Session Initiation Procotol) is and what part it plays in telephony. We often describe it as the "newer way of terminating" that is cost effective and about every Ineternet Service Provider provides a flavor of it. If you arent familiar with the basics please look at some background here on SIP.
In Unified Communications there is a fairly newer protocol that has been gaining some attention called XMPP. In short, XMPP is a protocol (like SIP). XMPP was majorly used for presence and Instant Messaging. But it is being expanded to other areas like call signal controlling. Here are some basic facts about XMPP
- XMPP was built from ground to support presence and IM
- XMPP is "eXtensible"
- XMPP is being (or has been) adopted by many big vendors like Cisco, Microsoft, Google, etc.
Within the leading products we deploy on a regular basis (Cisco and Microsoft) there are multiple products that support XMPP, like Webex Connect, Microsoft's Office Communication Server as well as Cisco CUPS. Microsoft product has to have an additional configuration setup and server in order to support XMPP and it not a native server role with the edge service. As for Cisco CUPS, with the release of CUPS 8.0 that introduces the jabber platform, it is based on XMPP.
A little history about XMPP, it was introduced in 1998 and later refined by the Jabber open source community that Cisco aquired a couple of years back.
Since XMPP is a protocol, it has many streams of communications or eXtensions that are used for different "features" you see within your chat window you use on a daily basis. Technical developers have different names for the standards they come to develop, then what we end user come to know them as.
For example a couple eXtensions within the protocol are "chat state notifications" which is indicating whether a chat partner is actively engaged in the chat, composing a message, temporarily paused, inactive, or gone. We also call that a presence status.
Another example is a "jingle" which is managing peer-to-peer media sessions in a way that is interoperable with existing standards. We end users know this as a voice chat, video chat or file transfer.
If you are interested in learning more about the XMPP protocol and the extension standards, they can be found here.
I hope this provided you with some interesting tidbits about XMPP and all protocols for that matter. Every feature within an application we use (Browser, Outlook,etc.) has some sort of communication protocol that is driving the ability for you to do basic tasks.
When we all come to adopt the standard that it becomes a GREAT technology that we highly depend on. Most of the time using it as a business tool just like E-Mail. From a philisophical level, this protocol "adoption" approach is Metcalfe's law.
-D