aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/jabber.txt13
-rw-r--r--doc/jingle.txt8
2 files changed, 21 insertions, 0 deletions
diff --git a/doc/jabber.txt b/doc/jabber.txt
new file mode 100644
index 000000000..5889a6e36
--- /dev/null
+++ b/doc/jabber.txt
@@ -0,0 +1,13 @@
+(res_jabber is very experimental!)
+Jabber(xmpp) is an xml based protocol primarily for presence and messaging.
+It is an open standard and there are several open server implementations,
+ejabberd, jabberd(2), wildfire, and many others, as well as several open source
+clients, Psi, gajim, gaim etc. Jabber differs from otherIM applications as it
+is immensly extendable. This allows us to easily integrate asterisk with
+jabber. The Asterisk Jabber Interface is provided by res_jabber. res_jabber
+allows for asterisk to connect to any jabber server via the standard client
+protocol or also as a simple client. Several simple functions are exposed to
+the dial plan, jabberstatus, jabbersend, and soon jabberrecv. res_jabber is also used
+to provide the connection interface for chan_jingle.
+The maintainer of res_jabber is Matthew O'Gorman <mogorman@digum.com> or
+mog_work on irc or prefered mogorman@astjab.org over jabber.
diff --git a/doc/jingle.txt b/doc/jingle.txt
new file mode 100644
index 000000000..b6bdd111c
--- /dev/null
+++ b/doc/jingle.txt
@@ -0,0 +1,8 @@
+(Jingle support in asterisk is experimental)
+Jingle is an xmpp based protocol for signalling the transfer of media.
+Currently asterisk supports the propitery GoogleTalk protocol that is
+very similar to jingle, and hopes to support true jingle specs
+(JEP-166,167,176,177,180,181 etc) as more clients support the true standard.
+Jingle's configuration is very similar to sip.conf only as we are not the
+jabber server in this case you must provide a connection for the peer to
+travel out on.