<p>Yeah, that's what I'm doing and just finished tonight. Still a bit to go but gist is:</p>
<p>1. Follow @SureVoIPLabs<br>
2. Bot auto follows you back if not already following <br>
3. Sends you a DM with a thank you and instructions. <br>
4. You then send a DM like so:</p>
<p>d @SureVoIPLabs my_mobile_number/number_I_wish_to_call</p>
<p>5. Do some tariff checks and fire off a bgapi with 2 or 10min limit <br>
6. Send you a DM back </p>
<p>All free but limited to UK for now. Will be live next week or so. Full version with international and App auth coming with credit topups via DM too :)</p>
<p>Gav. </p>
<p><a href="http://www.surevoip.co.uk">http://www.surevoip.co.uk</a></p>
<div class="gmail_quote">> On Mon, Jul 25, 2011 at 11:59 AM, Gavin Henry <<a href="mailto:gavin.henry@gmail.com">gavin.henry@gmail.com</a>> wrote:<br>> <br>>> Why not bgapi and listen for the CHANNEL_ANSWER event?<br>
>><br>> Dealer's choice. You can totally do that if you so desire. It all depends on<br>> what the ultimate goal is. If you just need to have a few calls hit the dp,<br>> attempt bridge, then play messages based on failure types then the dialplan<br>
> itself can handle it with just continue_on_fail and transfer apps. You can<br>> throw in a dp script if you have some specific logic you wish to apply.<br>> Keeps it clean and simple. However, if you are wanting to do some async<br>
> stuff like real-time status updates, etc. then event socket w/ bgapi<br>> originates is definitely the way to go.<br>> <br>> -MC<br></div>