Differences

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

--- userdoc:tt_distribute_events_xmpp_pubsub [2013/08/30 08:00]
abelbeck [Configure Remote Server2]
+++ userdoc:tt_distribute_events_xmpp_pubsub [2013/09/01 05:07]
droemel [Configure Remote Server2]
@@ Line 85: / Line 85: @@
 !!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 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''.
+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. 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''.
+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 need different mailbox numbers on each side, if you want to use the MWI feature. You can check the MWI status in the Asterisk CLI with:
+  event dump cache MWI
-I couldn't figure out yet, how to subscribe to MWI states on the remote server, the events are distributed.