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) over these connections.
OpenSIPS should make the events received (replies or not, depending on
the script admin to identify them) somehow available in some script
routes where we can pick up parked transactions (sharing the ids via the
replied events).
We use such scenario for call authorization inside billing (send
call_auth to billing engine and receive maximum duration for it).
Processing the answer is done in the script and whole thing would happen
asynchronously, hence not anymore depending on the time it takes for
billing to process the request.
Another usage would be for dialog kill when the funds available for the
calls are emptied on billing side. The same event_route will receive the
disconnect request from billing side, will identify there the dialog and
kill it.
If this two way communication would be not suitable for events
infrastructure which you have already developed, would it be possible to
"wake up" the transaction over MI and send it to a script route plus
setting some avps for it maybe?
Thanks for your thoughts on this!
DanB
On 27.01.2015 18:07, Bogdan-Andrei Iancu wrote:
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 if
you are considering event replies in script routes (eg: have a
dedicated event_reply route where we can pick up a specific
transaction parked and continue processing it).
A particular applicability is 2 way communication with an external
application like billing engine.
Thanks in advance!
DanB
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
