[asterisk-bugs] [Asterisk 0015757]: [branch] Add support for distributing device state and MWI via XMPP PubSub
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jan 26 18:26:07 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15757
======================================================================
Reported By: Marquis
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15757
Category: Resources/res_jabber/NewFeature
Reproducibility: N/A
Severity: feature
Priority: normal
Status: ready for testing
Asterisk Version: SVN
JIRA: SWP-763
Regression: No
Reviewboard Link: https://reviewboard.asterisk.org/r/351/
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 213622
Request Review:
======================================================================
Date Submitted: 2009-08-21 15:42 CDT
Last Modified: 2010-01-26 18:26 CST
======================================================================
Summary: [branch] Add support for distributing device state
and MWI via XMPP PubSub
Description:
Distributing device state in this way opens up the possibility of having
geographically distributed clusters, as well as having integration with
XMPP clients and other components that are PubSub-aware.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
parent of 0015753 [patch] Custom devices do not interoper...
======================================================================
----------------------------------------------------------------------
(0117224) Marquis (reporter) - 2010-01-26 18:26
https://issues.asterisk.org/view.php?id=15757#c117224
----------------------------------------------------------------------
Basically, I mean anything that the Asterisk instances are expected to add
to the affiliations list as an owner. More often than not, that will mean
new Asterisk instances. But strictly speaking that's not necessary. For
example, you could have an outside process that needs publish access to the
PubSub nodes. And whatever JID that process is using would need to be in
the affiliations list.
The way to add a new JID to the affiliations is:
1) Bring down all but one of the Asterisk instances
2) Use the built-in commands to delete the nodes
3) Stop the last instance
4) Make the addition(s) to the buddy list in jabber.conf
5) Restart all Asterisk instances
You could also bring them all down and run an external app/script to
delete the nodes (or change them on the fly, for that matter).
The same would go for removing a JID from the affiliations list.
Is that clear enough?
Issue History
Date Modified Username Field Change
======================================================================
2010-01-26 18:26 Marquis Note Added: 0117224
======================================================================
More information about the asterisk-bugs
mailing list