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
userdoc:tt_distribute_events_xmpp_pubsub [2013/09/01 10:29] – [Configure Remote Server2] droemeluserdoc:tt_distribute_events_xmpp_pubsub [2013/09/01 10:30] (current) – [Configure Remote Server2] droemel
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. !!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 are listed only the differences.+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'': 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'':
  • userdoc/tt_distribute_events_xmpp_pubsub.1378031374.txt.gz
  • Last modified: 2013/09/01 10:29
  • by droemel