Review Board 1.7.16

Deprecate chan_gtalk, chan_jingle, and res_jabber in preference of chan_motif and res_xmpp

Review Request #2082 - Created Aug. 23, 2012 and submitted

Leif Madsen
file, russell
Modify markup for chan_gtalk, chan_jingle, and res_jabber in order to deprecate them. Add replacement markup pointer to chan_motif and res_xmpp.
Executed make validate-docs to verify markup was valid. Ran make menuselect to verify modules live under the deprecated header, and show the correct replaced by.
Review request changed
Updated (Aug. 23, 2012, 2:30 a.m.)
Posted (Aug. 23, 2012, 11:45 a.m.)
I'm acknowledging the underlying issue, but I'd prefer to see some discussion of this patch before we commit it.  I'd hate to have this go into Asterisk 11.0.0-beta2, and have people feel like this was done without enough discussion.
  1. As an ack to the actual patch, I agree with deprecating all modules listed.
  2. I think this is a step in the right direction, especially since we have drop in replacements for the same functionality.  This shouldn't really affect anyone and overall makes things better for them as well.  Better support and being up to date with the latest specs is a good thing.
    It would be very scary trying to support 5 modules when we can handle it with with just 2 supported modules.
Posted (Aug. 23, 2012, 12:07 p.m.)
Just a related note, jabber is used in many examples and noted in many other areas.  Quick example would be in

jabber list nodes=xmpp list nodes
jabber purge nodes=xmpp purge nodes
jabber delete node=xmpp delete node
jabber create collection=xmpp create collection
jabber create leaf=xmpp create leaf
jabber set debug=xmpp set debug
jabber show connections=xmpp show connections
jabber show buddies=xmpp show buddies

Maybe expand your changes...
Posted (Sept. 10, 2012, 11:16 a.m.)
Given the feedback received and the fact that maintaining two sets of modules for the same functionality could become a headache very quickly, we decided to go ahead and put this into 11 (since it's still beta) and trunk. runs on a server provided by Digium, Inc. and uses bandwidth donated to the open source Asterisk community by API Digital Communications in Huntsville, AL USA.
Please report problems with this site to