Re: [OpenSIPS-Users] Async Event route_replies

2015-01-29 Thread Bogdan-Andrei Iancu
Hi Dan, The event mechanism is by definition an one way communication system. I understand what you are looking for, but the event system is not the answer for it (at least not anymore if you do look to get a sort of replies back). You can get CDRS or others via events, but for auth purposes,

Re: [OpenSIPS-Users] Async Event route_replies

2015-01-29 Thread 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

Re: [OpenSIPS-Users] Async Event route_replies

2015-01-29 Thread DanB
Hey Bogdan, Thanks for your input, I think we are on the same page here. Maybe I was the one forcing events to be the solution just because we already implemented the protocol for it :). The perfect solution would be as you said, a 2 way protocol (I was calling them events since I imagined

Re: [OpenSIPS-Users] Async Event route_replies

2015-01-28 Thread Brett Nemeroff
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

Re: [OpenSIPS-Users] Async Event route_replies

2015-01-28 Thread Bogdan-Andrei Iancu
Hi Dan, Indeed, the idea is quite old and it exists since the old SER times when a very similar mechanism was used for SER and SEMS integration - see the t_write_fifo() function in TM - this creates a transaction, writes down stuff to SEMS via a fifo file and puts transaction on hold. It was

Re: [OpenSIPS-Users] Async Event route_replies

2015-01-28 Thread DanB
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

Re: [OpenSIPS-Users] Async Event route_replies

2015-01-27 Thread DanB
Hi Bogdan, I cannot claim IPR of the idea since we are using it already inside CGRateS with another proxy so it was not invented by us :). The process should be something like: when OpenSIPS sends out an event over a connection, it should be also possible to receive data (answer or not)

Re: [OpenSIPS-Users] Async Event route_replies

2015-01-27 Thread Bogdan-Andrei Iancu
Hi Dan, Could you detail a bit more your idea ? I'm not sure I get the whole concept. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 27.01.2015 13:38, DanB wrote: Hey Guys, Now that async script routes is an actual subject, I was wondering