El Thursday 12 June 2008 14:38:44 David Villasmil escribió:
The problem is that you are addressing the problem in a privative way while there are RFC's and techniques for that. For your proposal using Session Timers should be the best option,
Are you talking, i.e. Asterisk?
No, Asterisk is a bad example for this case since doesn't provide SessionTimers functions and so. In fact I'm not suggesting a specific product, but you could try other B2BUA more SIP compliants and develop a B2BUA between OpenSer and gateways that implements SessionTimers. Of course it's not an easy task.
You can take a look at those projects:
http://www.b2bua.org/ http://www.resiprocate.org/Main_Page https://sailfin.dev.java.net/ http://www.opensipstack.org/sbc_man_content.html
(at last one of both endpoinds). OpenSer cannot send it since it is a proxy so a B2BUA or gateway should doit. IMHO you are addressing the problem in the wrong place (but it could work of course).
I see what you're saying, problem with this is I don't WANT to HAVE to use an asterisk or whatever... I want to depend only on Openser.
OpenSer is a statefull proxy, it shouldn't control dialogs. With "dialog" module you can do things but obviously is not so complete as you need.
I believe I can be done with session timers, as you say. What I Don't KNOW is whether there is a timer to ask the UAC to send us a kind of "keep-alive" message. I don't know what that message is called, or what module creates it.
No one. The mos similar function in OpenSer is the registrar module sending NOT in-dialog OPTIONS to mantain NAT keepalive.
The thing is:
What module's function to use to make the UAC send uns a "keep-alive" whilst in a dialog every X senconds, setting a timeout for that keep-alive to be sent and resetting it everytime it's received.
There is not that function/module for now. :(