asterisk users - Jul 2010 - asterisk & distributed device state => res_jabber Versus res_ais

Hello,
     as I'm looking for a solution (with asterisk 1.6.2) , my 
investigations leaded to :
- res_ais => libais & corosync. (each node need to run corosync / aiexec)
- res_jabber => libjabber & iksemel. (each node need to be connected on 
an XMPP server)

I've been able to make some successful tests with res_ais on 2 servers 
but got some CPU issues with corosync after some hours of activity.

What's the best solution regarding flexibility and stability and 
real-time exploitation ?

I've got the feeling a good (and old) XMPP server will be more reliable 
than res_ais which seems to be pretty young.

Thank you for your help.

Mathieu

On 10-07-26 10:45 AM, Mathieu wrote:
> Hello,
>       as I'm looking for a solution (with asterisk 1.6.2) , my
> investigations leaded to :
> - res_ais =>  libais&  corosync. (each node need to run corosync /
aiexec)
> - res_jabber =>  libjabber&  iksemel. (each node need to be
connected on
> an XMPP server)
>
> I've been able to make some successful tests with res_ais on 2 servers
> but got some CPU issues with corosync after some hours of activity.
>
> What's the best solution regarding flexibility and stability and
> real-time exploitation ?
>
> I've got the feeling a good (and old) XMPP server will be more reliable
> than res_ais which seems to be pretty young.
On Asterisk 1.6.2, your only option for distributing device state is with 
res_ais. I've used it in a labbing system and it works well -- the caveat is
that your machines need to be on a low latency network (i.e. LAN).

With Asterisk 1.8 (currently 1.8.0-beta1) you can use XMPP to distribute your 
device states over the WAN. I've made it work with the Tigase XMPP server.
More
information about it can be found in the doc/distributed_devstate-XMPP.txt file.

Leif Madsen.