2 ; Sample configuration file for res_ais
3 ; * SAForum AIS (Application Interface Specification)
5 ; More information on the AIS specification is available from the SAForum.
6 ; * http://www.saforum.org/
8 ; A nice open source implementation of AIS is available called openais. Visit
9 ; the openais website for downloads and more information.
10 ; * http://www.openais.org/
15 ; The general section is reserved but not currently used.
19 ; Event channels are named distributed groups that share events. Each node
20 ; that is the member of the event channel should have an entry in their
21 ; ais.conf file that indicates that they are a member of the event channel.
22 ; Each node's entry for the event channel also indicates which event types
23 ; will be published to other nodes, as well as which event types this node
24 ; will subscribe to from other nodes in the event channel.
26 ; The name of the event channel is the name in brackets that begin a section
27 ; in the configuration file.
30 ; To define an event channel, this entry must be in the configuration section:
33 ; Indicate that a node is capable of publishing events of a certain type by
34 ; using the publish_event directive.
37 ; Indicate that a node is interested in receiving events of a certain type
38 ; from other nodes in the event channel by using the subscribe_event directive.
41 ; Supported event types include: mwi, device_state
45 ; This example is for a node that can provide MWI state information, but should
46 ; also be listening for MWI state changes from other nodes. Examples of when
47 ; this would be used are when this is both a voicemail server and also has
48 ; phones directly registered to it.
57 ; This example would be used for a node that can provide MWI state to other
58 ; nodes, but does not need to know about MWI state changes that happen on
59 ; any other node. This would most likely be a voicemail server where no
60 ; phones are directly registered.
68 ; This example would be used for a node that has phones directly registered
69 ; to it, but does not have direct access to voicemail. So, this node wants
70 ; to be informed about MWI state changes on other voicemail server nodes, but
71 ; is not capable of publishing any state changes.