10 Jul
2007
10 Jul
'07
9:27 a.m.
Hi Tim!
Generating the CANCELs on a received 200 OK is done by the tm module.
AFAIK this is not changeable. Further it requires correct routing of
CANCEL in openser.cfg too (most people just t_relay() CANCELs as then
all the CANCEL handling is done by the tm module)
But if you do not need statefull transactions you can try forwarding
stateless using forward(); but I'm not sure if this does also parallel
forking. Parsing the Request-Disposition header can be done using the
regards
klaus
Tim Madorma wrote:
Hi,
I was wondering if there is an option to disable the sending of CANCEL
towards the branches that have not yet responded when OpenSER performs
parallel forking and one endpoint has answered.
The request/question that I have is sort of outlined in RFC 3841 as
follows:
cancel-directive: This type of directive indicates whether the caller
would like each proxy server to send a CANCEL request downstream
("cancel") in response to a 200 OK from the downstream server
(which is the normal mode of operation, making it redundant), or
whether this function should be left to the caller ("no-cancel").
If a proxy receives a request with this parameter set to "no-
cancel", it SHOULD NOT CANCEL any outstanding branches upon
receipt of a 2xx. However, it would still send CANCEL on any
outstanding branches upon receipt of a 6xx.
But in this case, I was wondering if there was something that was
configurable.
thanks,
Tim
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users