Re: [asterisk-users] asterisk distributed device state = res_jabber Versus res_ais
11 aug 2010 kl. 15.49 skrev Leif Madsen: On 10-08-10 04:11 AM, Olle E. Johansson wrote: 26 jul 2010 kl. 18.13 skrev Leif Madsen: 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. This fall, we're going to implement it using SIP for 1.4 and 1.8/trunk. Look for project pinana. Development will start later this month. Sounds very cool! I look forward to playing around with it. Also thanks for picking a branch name that is not related to fruit or frogs. Thanks for the feedback. I guess the name was a mistake and I'll take it under reconsideration :-) /O -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] asterisk distributed device state = res_jabber Versus res_ais
On 10-08-10 04:11 AM, Olle E. Johansson wrote: 26 jul 2010 kl. 18.13 skrev Leif Madsen: 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. This fall, we're going to implement it using SIP for 1.4 and 1.8/trunk. Look for project pinana. Development will start later this month. Sounds very cool! I look forward to playing around with it. Also thanks for picking a branch name that is not related to fruit or frogs. Leif. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] asterisk distributed device state = res_jabber Versus res_ais
26 jul 2010 kl. 18.13 skrev Leif Madsen: 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. This fall, we're going to implement it using SIP for 1.4 and 1.8/trunk. Look for project pinana. Development will start later this month. /O -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] 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 -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] asterisk distributed device state = res_jabber Versus res_ais
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. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
