On Sat, May 17, 2008 at 12:23 PM, Andy Powell <<a href="mailto:openmoko@automated.it">openmoko@automated.it</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Saturday 17 May 2008 18:07, Brandon Kruse wrote:<br>
<br>
> ><br>
> > That's not always a good thing.<br>
><br>
> I agree.<br>
> Compliance has been extremely difficult.<br>
><br>
<br>
</div>Amen!</blockquote><div> </div><div>Another "ugh" for compliance across browsers :(<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
<br>
> >> Trixbox uses PHP/mysql/apache2, whereas the AsteriskGUI uses the<br>
> >> builtin<br>
> >> Asterisk HTTP Server, and javascript files (because we believe that<br>
> >> there<br>
> >> should never be unneeded load on the box that your phone calls are<br>
> >> running<br>
> >> through. )<br>
> ><br>
> > You're still running an http server on your asterisk box. You could<br>
> > offload<br>
> > even more by using something like my mysqlswitch and a 2nd box for<br>
> > mysql +<br>
> > Apache. In reality most people are either running asterisk at home<br>
> > where it<br>
> > doesn't matter or running it 'big time' where the gui is no use /<br>
> > too slow.<br>
> ><br>
> > I<br>
> > still believe that an internal http server is just so wrong in the<br>
> > first<br>
> > place - but you're entitled to your opinion ;)<br>
><br>
> Haha, you should have seen the community response when mark merged<br>
> that into feature frozen 1.4 ;)<br>
><br>
> We have community members with 2,000 end points and gateways managed<br>
> through the GUI,</div></blockquote><div> </div><div>Heh, not sure exactly. Javascript select boxes + 2,000 entries + sorting = script delay, for sure.<br>And....the GUI only works in Firefox 2 and 1.5.<br><br>But, we may have something up our sleeve that could be released soon, never know :)<br>
<br>I am a vi + /etc/asterisk man myself, since that how I was raised. (Way before GUIs)<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
</div>Windows users ;P<br>
<div class="Ih2E3d"><br>
> and editing the files themselves. I say try both!<br>
> I am just biased.<br>
<br>
</div>:D<br>
<div class="Ih2E3d"><br>
> > Good work with the iax2 integration. Some integration with the<br>
> > contacts would<br>
> > be really useful, perhaps a voip number. I have here a Pirelli DP-<br>
> > L10 sip+gsm<br>
> > phone which has a really nice feature, the ability to set a<br>
> > preferred network<br>
> > to dial from,<br>
> ><br>
> > ie<br>
> > GSM Only<br>
> > VOIP Only<br>
> > GSM Preferred<br>
> > VOIP Preferred<br>
><br>
> This is EXACTLY what I want to do, well put. One semi-concern I have<br>
> is where to configure this? Your opinion, scaredy, would be great!<br>
> (for the best place to do this).<br>
<br>
</div>I think that it's a dialer function - however it would be nice if other<br>
applications could tell the dialer how to dial. Since dbus seems to be the<br>
interface that's going to be used it might be nice to have the option there<br>
too. In essence you can configure this option from the dialer or any other<br>
application that sends a message via dbus - this seems the most flexible and<br>
would allow an application to tell the dialer 'Please dial this number, via<br>
VOIP'<br>
<div class="Ih2E3d"></div></blockquote><div><br>I am a little confused about where we would want the options (eg Preferred voip, preferred GSM, etc)<br><br>I remember mickey discussing the strong API for using dbus. I am loving this, as I use<br>
dbus in a lot of other applications, specifically with glib. It's as simple as signal_connect('sig-name, aka new-phone-call', callback_func);<br><br>I will look into the Dialer for this. Obviously this is going to take a lot more work that just getting the underlying iax2 working, it<br>
will almost be enough for 2 separate projects. (Exposing events of the dialer over dbus, if it is not already, etc).<br><br>Um, you can use the ipkg for installation, instructions on <a href="http://bkruse.com">http://bkruse.com</a><br>
<br>I had a pretty crazy build environment for iaxclient, as it was not supposed to natively compile for ARM (That was a crazy night.)<br><br>Ok, just checked out the source again. iaxclient_moko (in trunk) is the one you want. I am not sure if you can<br>
get it to build, I need to add those kinds of things to the configuration script, hence the reason I released the ipkg<br>so soon :P <br><br>The other directories are third party libs that iaxclient depends on, that are also setup to cross-compile.<br>
<br>You should be able to make an iax call with the test client.<br><br>After that works great, and the source works/builds ok, then I will start implementing into the dialer.<br><br>Once I can make a call through iax, using the dialer, I will work on another program (using dbus) for auto-detecting<br>
AP's. (Eg keep scanning, there is probably already a mechanism to do this.)<br><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
<br>
> > obviously well aware, cures this.<br>
><br>
> One port, nat work arounds, best protocol ever. Maybe not best :P<br>
<br>
</div>IAX2 is excellent for point to point, It's a life saver (if not a marriage<br>
saver) that means I can easily talk to my wife when I'm away. It links my<br>
home asterisk box in .nl to the office one in the UK so I can work from<br>
either place. Sure I could do the same with SIP/H323 etc but with IAX2 it's a<br>
10 second job - fire and forget. Awesome, I love it.<br>
<div class="Ih2E3d"></div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
<br>
><br>
> > Is this limited to the freerunner just because of wifi or is there<br>
> > some other<br>
> > reason? I'm thinking BT or teathered (sp) would still be useful on<br>
> > the gta01.<br>
><br>
> Absolutely. I have my iax client working through ethernet over usb.<br>
> But right, USB wifi, or usb bt.<br>
<br>
</div>Excellent, I'm happy to test it out on my 01 - Hey, I'm happy to put it on my<br>
images by default once you're happy for it to go.<br>
<div class="Ih2E3d"><br>
</div></blockquote><div>Install the ipkg, and do a testcall --help (it's in /usr/bin or /bin, cannot remember) <br><br>Btw, are you currently building freerunner images?<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
> > Looking forward to getting my grubby paws on it :D<br>
><br>
> I value your opinion :)<br>
<br>
</div>I value your code :)<br>
<br>
I presume I should be looking at iaxclient_moko and ignoring the iaxclient<br>
dir ?<br>
<div><div></div><div class="Wj3C7c"></div></div></blockquote><div>Answered above^^ <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="Wj3C7c"><br>
--<br>
<br>
Andy / ScaredyCat<br>
<br>
_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div></div></blockquote></div><br>