userdoc:tt_distribute_events_xmpp_pubsub

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
userdoc:tt_distribute_events_xmpp_pubsub [2013/08/30 08:05]
abelbeck [Configure Remote Server2] 		userdoc:tt_distribute_events_xmpp_pubsub [2013/09/01 05:07]
droemel [Configure Remote Server2]
Line 87: Line 87:
 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''. 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. //(Request for working example.)//+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 
 + 
  • userdoc/tt_distribute_events_xmpp_pubsub.txt
  • Last modified: 2013/09/01 05:30
  • by droemel