<div dir="ltr"><p dir="ltr">It would be in interesting if the events endpoint would be similar to couchdb's changes endpoint, where IIRC you can ask for all the events since a given point in time.<br>
</p>
<div class="gmail_quote">On Jan 3, 2014 12:51 AM, "Julian Lyndon-Smith" <<a href="mailto:asterisk@dotr.com" target="_blank">asterisk@dotr.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
please forgive my ignorance and lateness to the thread :<br>
<br>
one of the worries that I always have with using something like ARI to<br>
do billing etc is that there is always a possibility of the ARI<br>
application being down when such events occur. Can ARI events be<br>
logged to a database (much like the cdr and manager events can)<br>
internally within asterisk ?<br>
<br>
If there were multiple ARI listeners or db loggers (for redundancy<br>
purposes), does an ARI event contain a unique id / guid so we can tell<br>
if that event has been already processed ?<br>
<br>
Julian<br>
<br>
<br>
On 3 January 2014 02:56, Joshua Colp <<a href="mailto:jcolp@digium.com" target="_blank">jcolp@digium.com</a>> wrote:<br>
> Alistair Cunningham wrote:<br>
>><br>
>><br>
>> It's not quite the question you're asking, but I'll weigh in anyway.<br>
>> When implementing this, please bear those writing billing engines in<br>
>> mind. For example, imagine a call comes in from the PSTN to a toll-free<br>
>> number (so the inbound call must be billed). The caller listens to an<br>
>> IVR for 10 seconds, then talks to a person on a locally registered SIP<br>
>> handset for a further 20 seconds. That person then blind transfers them<br>
>> out to a cell phone (and the outbound call must be billed). They talk to<br>
>> the cell phone user for 30 seconds, who uses the # key to attended<br>
>> transfer them to a different cell phone (which is a separate billable<br>
>> outbound call), with the first cell phone user talking to the second for<br>
>> 15 seconds during the attended transfer. The original caller talks to<br>
>> the second cell phone for 2 minutes, then hangs up. The inbound call<br>
>> must be billed for 3:15, the first outbound for 0:45, and the second<br>
>> outbound for 2:15 (ignoring ring times on the outbound calls). Of<br>
>> course, you don't need to implement this logic in Asterisk, but please<br>
>> keep the model of the channels consistent enough that someone writing a<br>
>> billing engine can figure out exactly what call legs they need to bill,<br>
>> and for how long, and when transfers occur which endpoint did the<br>
>> transfer and how. AGI suffered from billable call legs appearing to hang<br>
>> up when transferred (even though they stayed up), making it very<br>
>> difficult to piece together exactly what billable calls occurred when.<br>
>> It would be good to avoid this in ARI.<br>
><br>
><br>
> From the perspective of the transfer events you'll get full details about<br>
> everything involved. Who did the transfer, what type, the bridge involved,<br>
> the channels transferred, where. The ARI application can interpret these and<br>
> do what it wants with them.<br>
><br>
> --<br>
> Joshua Colp<br>
> Digium, Inc. | Senior Software Developer<br>
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA<br>
> Check us out at: <a href="http://www.digium.com" target="_blank">www.digium.com</a> & <a href="http://www.asterisk.org" target="_blank">www.asterisk.org</a><br>
><br>
> _______________________________________________<br>
> asterisk-app-dev mailing list<br>
> <a href="mailto:asterisk-app-dev@lists.digium.com" target="_blank">asterisk-app-dev@lists.digium.com</a><br>
> <a href="http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev" target="_blank">http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev</a><br>
<br>
<br>
<br>
--<br>
Julian Lyndon-Smith<br>
IT Director, Dot R Limited<br>
<br>
"I don’t care if it works on your machine! We are not shipping your machine!”<br>
<br>
The kangaroo dances: <a href="http://www.youtube.com/watch?v=MAWl5iYOaUg" target="_blank">http://www.youtube.com/watch?v=MAWl5iYOaUg</a><br>
<br>
_______________________________________________<br>
asterisk-app-dev mailing list<br>
<a href="mailto:asterisk-app-dev@lists.digium.com" target="_blank">asterisk-app-dev@lists.digium.com</a><br>
<a href="http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev" target="_blank">http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev</a><br>
</blockquote></div>
</div>