[OpenSIPS-Users] Async Event route_replies

[Bogdan-Andrei Iancu]

Hi Brett,

Yes, that is on the TODO list, to have the dialog module exporting some 
dialog related events. Not sure if it will make it in 2.1 as there are 
many other on TODO list (like the proto stack rework, adding WS, etc). 
If time allows, why not :)

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 28.01.2015 15:14, Brett Nemeroff wrote:
> Hey All,
> An idea that I've tossed out before that is similar here is event
> routes that are triggered on dialog state changes. I have to admit I
> don't know if the 2.x already has this or not but I think especially
> on the context of a billing engine, tying and event to a dialog state
> change makes sense. I like this more than embedding the event logic
> into the acc module since you can do things like manage a list of
> connected calls with dialog events and external REST calls very easily
> and its a more efficient push model instead of a MI pull model, which
> is unwieldy for larger switches
>
>
>
>
>
> Sent from my iPhone
>
>> On Jan 28, 2015, at 4:10 AM, DanB <danb.lists at gmail.com> wrote:
>>
>> Hey Bogdan,
>>
>> Thank you for your input and support!
>>
>> Regarding existing mechanisms, I would still prefer the event part as it works now since it generates automated CDR vs http rest or exec where I need to make up my own one. Http would be my second choice if you ask me.
>> On the other hand, what about the idea of unparking a transaction over the MI commands? Would that be possible? In that way I could get the call authorization event generated manually and park the request right after. When billing answers, I could unpark it (and set maximum dialog timeout) over mi.
>>
>> Thanks,
>> DanB
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users