The point is that I *do* want the state of the DAHDI channel to be published (in the test, it is a FXS extension), but it should be somehow:<div>1) distinguished from the devices with the same name (eg. DAHDI/4) on each of the other servers</div>
<div>2) be monitored nevertheless by hints on the other servers, since this is the initial purpose of the test.</div><div><br></div><div>What I am thinking as a quick (but not optimal solution) is to have the jabber module publish only the custom device states and create a custom state for each extension that follows the stage changes of the "normal" devices.</div>
<div><br></div><div>This will definitely solve my problem, but will spoil the purpose of device state sharing between servers.</div><div><br></div><div>Maybe there should be a more sophisticated way of posting states using pubsub than just device name/device state that could accomplish both goals.</div>
<div><br></div><div>Any ideas?</div><div><br></div><div>PS. As for the comment on the documentation, I didn't mean to be rude. There is are just too many results if you google "asterisk distributed device states" but they all point to the same few paragraphs with the same example that involves a custom device state and not real devices.<br>
<div><br><div class="gmail_quote">On Sun, Jan 29, 2012 at 8:02 PM, Russell Bryant <span dir="ltr"><<a href="mailto:russell@russellbryant.net">russell@russellbryant.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Sun, Jan 29, 2012 at 6:05 AM, Dimitris Kazakos <<a href="mailto:nemphys@gmail.com">nemphys@gmail.com</a>> wrote:<br>
> Either I missed something important, or there is a design flaw in the<br>
> distributed device states functionality:<br>
><br>
> After struggling for a while, I managed to get 2 asterisk servers<br>
> (inter-connected using an IAX trunk) connected to an Openfire XMPP server<br>
> with the intention to share extension states between them (for blf usage).<br>
> I first tried the Custom device suggested to be used as a test in the<br>
> documentation (which is quite poor, btw) and all worked fine; the state was<br>
> properly shared between the servers.<br>
<br>
</div>Now that you set it up, feel free to help with the documentation.<br>
<div class="im"><br>
> The problem starts when the state sharing started for actual devices.<br>
> After a little digging in the Openfire database/XMPP message logs trying to<br>
> see what was actually published, I realized that there are 2 things<br>
> published with each state change: device name and state (along with the<br>
> server eID) - good so far.<br>
> The problem is that both servers have DAHDI fxs/fxo cards and therefore both<br>
> servers have DAHDI/X devices. For those devices, the state is normally<br>
> published using XMPP pubsub, but since the device names are the same in both<br>
> servers (though the actual devices are different), when eg. device DAHDI/5<br>
> on server 1 was in a call, the device state of DAHDI/5 on server 2 (using<br>
> show hints) would change to "in-use".<br>
> This of course is a deal breaker, as there are many devices that have the<br>
> same name (custom DND, meetme, etc, actually all except sip/iax<br>
> extensions/trunks).<br>
><br>
> Am I missing something, or this issue has not been addressed yet?<br>
<br>
</div>You're right. It's just that you're the first person that has found<br>
this to be a problem. I think most people are just using the states<br>
of SIP devices. Adding some options to limit what states get<br>
published wouldn't be very hard.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Russell Bryant<br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</font></span></blockquote></div><br></div></div>