diff options
author | Russell Bryant <russell@russellbryant.com> | 2012-02-05 10:58:37 +0000 |
---|---|---|
committer | Russell Bryant <russell@russellbryant.com> | 2012-02-05 10:58:37 +0000 |
commit | 055a19e1286fbb7a3559c9928fad4e7d08af5329 (patch) | |
tree | bf9e55be47bfefe82e02466a8e2091f4f8de8bd2 /configs | |
parent | a898eb4d078750c46cefc2f3fba6b34207eec160 (diff) |
Replace res_ais with a new module, res_corosync.
This patch removes res_ais and introduces a new module, res_corosync.
The OpenAIS project is deprecated and is now just a wrapper around
Corosync. This module provides the same functionality using the same
core infrastructure, but without the use of the deprecated components.
Technically res_ais could have been used with an AIS implementation other
than OpenAIS, but that is the only one I know of that was ever used.
Review: https://reviewboard.asterisk.org/r/1700/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@354046 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'configs')
-rw-r--r-- | configs/ais.conf.sample | 85 | ||||
-rw-r--r-- | configs/res_corosync.conf.sample | 31 |
2 files changed, 31 insertions, 85 deletions
diff --git a/configs/ais.conf.sample b/configs/ais.conf.sample deleted file mode 100644 index a4428891f..000000000 --- a/configs/ais.conf.sample +++ /dev/null @@ -1,85 +0,0 @@ -; -; Sample configuration file for res_ais -; * SAForum AIS (Application Interface Specification) -; -; More information on the AIS specification is available from the SAForum. -; * http://www.saforum.org/ -; -; A nice open source implementation of AIS is available called openais. Visit -; the openais website for downloads and more information. -; * http://www.openais.org/ -; - -; -; *** NOTE *** -; This document includes some information about using the res_ais module for -; distributed events. However, it is important to note that res_ais is still -; considered experimental, as the module exposes the binary format of events -; over the network between servers. This format is still subject to change -; between 1.6.X releases. -; ************ - -; -; [general] -; The general section is reserved but not currently used. -; - -; -; Event channels are named distributed groups that share events. Each node -; that is the member of the event channel should have an entry in their -; ais.conf file that indicates that they are a member of the event channel. -; Each node's entry for the event channel also indicates which event types -; will be published to other nodes, as well as which event types this node -; will subscribe to from other nodes in the event channel. -; -; The name of the event channel is the name in brackets that begin a section -; in the configuration file. -; [mwi] -; -; To define an event channel, this entry must be in the configuration section: -; type=event_channel -; -; Indicate that a node is capable of publishing events of a certain type by -; using the publish_event directive. -; publish_event=mwi -; -; Indicate that a node is interested in receiving events of a certain type -; from other nodes in the event channel by using the subscribe_event directive. -; subscribe_event=mwi -; -; Supported event types include: mwi, device_state -; - -; -; This example is for a node that can provide MWI state information, but should -; also be listening for MWI state changes from other nodes. Examples of when -; this would be used are when this is both a voicemail server and also has -; phones directly registered to it. -; -; [mwi] -; type=event_channel -; publish_event=mwi -; subscribe_event=mwi -; - -; -; This example would be used for a node that can provide MWI state to other -; nodes, but does not need to know about MWI state changes that happen on -; any other node. This would most likely be a voicemail server where no -; phones are directly registered. -; -; [mwi] -; type=event_channel -; publish_event=mwi -; - -; -; This example would be used for a node that has phones directly registered -; to it, but does not have direct access to voicemail. So, this node wants -; to be informed about MWI state changes on other voicemail server nodes, but -; is not capable of publishing any state changes. -; -; [mwi] -; type=event_channel -; subscribe_event=mwi -; diff --git a/configs/res_corosync.conf.sample b/configs/res_corosync.conf.sample new file mode 100644 index 000000000..9a72c1ccd --- /dev/null +++ b/configs/res_corosync.conf.sample @@ -0,0 +1,31 @@ +; +; Sample configuration file for res_corosync. +; +; This module allows events to be shared amongst a local cluster of +; Asterisk servers. Specifically, the types of events that may be +; shared include: +; +; - Device State (for shared presence information) +; +; - Message Waiting Indication, or MWI (to allow Voicemail to live on +; a server that is different from where the phones are registered) +; +; For more information about Corosync, see: http://www.corosync.org/ +; + +[general] + +; +; Publish Message Waiting Indication (MWI) events from this server to the +; cluster. +;publish_event = mwi +; +; Subscribe to MWI events from the cluster. +;subscribe_event = mwi +; +; Publish Device State (presence) events from this server to the cluster. +;publish_event = device_state +; +; Subscribe to Device State (presence) events from the cluster. +;subscribe_event = device_state +; |