Hi Ron,
I guess the easiest way to go at the moment will be to have a way to
stop the PRACK to reset the timeout. I see to choices:
1) define as module parameter a mask of methods to be ignore at
timeout update - is simple, fast but not so flexible
2) if the avp timeout is set to value 0, ignore it - more flexible.
regards,
bogdan
Ron Winacott wrote:
On Thursday 05 October 2006 2:17 pm, Dan Pascu wrote:
On Thursday 05 October 2006 20:58, Ron Winacott wrote:
Bogdan,
With changes I am making to the SST module, I noticed that the dialog
module is updating the timeout value on a PRACK in the dlg_onroute()
callback. You ignore ACKs but you do not ignore PRACKs. The fix is a
PRACK as opposed to ACK is a method that has a reply. So if you do not
reset the timeout, and the transaction timeouts before the PRACK answers
comes back what will then happen with it?
Good point, but the problem is the AVP I am using to set the dialog timeout
value is tied to the transaction, not the dialog. So the AVP is not available
after the INVITE/200 OK request/response when the PRACK is seen. So the PRACK
over writes the set timeout value of the dialog with the default value.
(killing any changes I have made at INVITE/200OK time via the dialog timeout
AVP)
So, ether I need PRACK to stop resetting the dialog timeout or I need the AVP
to be bound to the dialog and not the transaction so the dialog module
will "remember" my value and not use the default.
As for your question about what will happen, is if the dialog times out in the
middle of the PRACK/200OK transaction, then the dialog has timed out. In my
case the Session Expire time has been reached and the PROXY is in its right
to delete the dialog and free the resources because the session was not
renewed with a reINVITE/UPDATE.
Comments?
Thanks,
ronw (karwin)
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
