Hi Matthew,<div><br></div><div>Good idea.</div><div><br></div><div>The reason I didnt implement pairing support when I wrote chan_mobile was the d-bus dependancy stuff required to talk to the SDP daemon. I didnt want to introduce another asterisk dependancy. Its certainly do-able though.</div>
<div><br></div><div>cheers</div><div><br></div><div>dave<br><br><div class="gmail_quote">On Fri, Jan 23, 2009 at 5:16 AM, Matthew Nicholson <span dir="ltr"><<a href="mailto:mnicholson@digium.com">mnicholson@digium.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<br>
<br>
Recently it occurred to me that bluetooth paring support, might be a<br>
useful feature to have in chan_mobile. Currently you are required to<br>
manage device pairing outside of chan_mobile, which usually means<br>
configuring and managing an external program. Most of the pairing<br>
agents that I have seen are also interactive (for the initial pairing<br>
exchange), which is not suited for a server environment. A pairing<br>
agent could be built into chan_mobile and a 'pin=' option added to<br>
mobile.conf to simplify pairing chan_mobile devices.<br>
<br>
I would like to know if adding this functionality to chan_mobile is a<br>
good idea or not.<br>
--<br>
Matthew Nicholson<br>
Digium, Inc. | Software Developer<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>
</blockquote></div><br></div>