Differences

This shows you the differences between two versions of the page.

--- userdoc:tt_distribute_events_xmpp_pubsub [2013/08/30 07:58]
abelbeck
+++ userdoc:tt_distribute_events_xmpp_pubsub [2013/09/01 05:30] (current)
droemel [Configure Remote Server2]
@@ Line 1: / Line 1: @@
 ====== Distribute Asterisk Events using XMPP PubSub ======
-On occasion it is desirable to distribute device state and message waiting indication (MWI) events between Asterisk servers.  This can be accomplished by utilizing XMPP PubSub events and a common XMPP server.  The Asterisk XMPP clients are configured via either ''jabber.conf'' or ''xmpp.conf'' .
+On occasion it is desirable to distribute device state (e.g. BLF) and message waiting indication (MWI) events between Asterisk servers. This can be accomplished by utilizing XMPP PubSub events and a common XMPP server. The Asterisk XMPP clients are configured via either ''jabber.conf'' or ''xmpp.conf'' .
 !!Note: AstLinux 1.1.3 or later is required!!
@@ Line 83: / Line 83: @@
   exten => 1024,hint,SIP/24
-__The important past is:__ only the **device state** (INUSE, NOT_INUSE, RINGING) of **"SIP/24"** is distributed, not the hintname (e.g. "1024") or the context (e.g. "blf_server1"). You can name the hint and context as you want on Server2.
+!!Note ->!! Only the **device state** (INUSE, NOT_INUSE, RINGING) of **"SIP/24"** is distributed, not the hintname (e.g. "1024") or the context (e.g. "blf_server1"). You can name the hint and context as you want on Server2.
+Now you can simply create a BLF key on a phone on Server2 for "1024" to monitor the device state of "SIP/24" of Server1. For getting local BLF keys to work, several other parameters in ''sip.conf'' and ''extensions.conf'' may be needed. The same applies to distributed device states. Here you'll find only the differences.
+The Message Waiting Indication (MWI) events are also distributed across servers. For the above example you just need to add this to a phone in your ''sip.conf'':
+  mailbox=24
+as if it were a local mailbox. You will either need different mailbox numbers on each side or different voicemail contexts, if you want to use the MWI feature. You can check the MWI status in the Asterisk CLI with:
+  event dump cache MWI
-Now you simply can create a BLF key on a phone on Server2 for "1024" to monitor the device state of "SIP/24" of Server1. The context (e.g. "blf_server1") must be "reachable" for the phone though. It can be included into your "default" context (or whatever your main context for your local phones is), or you can set a "subscribecontext" in ''sip.conf''.
-I couldn't figure out yet, how to subscribe to MWI states on the remote server, the events are distributed.