On Thursday 04 October 2007, Bogdan-Andrei Iancu wrote: > Hi Henning, > > I have some concerns (even on a first view things work) about couple of > issues: > > - there are some direct access to the sip_msg structure as a > requests (the struct contains a union for reply and requests) and the > read information will be bogus. Like we have a filter: > msg->first_line.u.request.method_value==METHOD_ACK > which will be bogus for a reply. > > - routing - the module determins where to send the reply in two ways: > 1) based on top most via (assuming a request is processed), > so for a reply it will be again bogus > 2) based on the received field from sip_msg struct - to send > it where the request came from; again bogus.... > > It will be safer to undo the change until we understand all the > implications...
Hello Bogdan, ok, i'll revert this later. Dan suggested to use t_reply, but this function is also not available here. So it is not possible to send reply in a ONREPLY route? Cheers, Henning _______________________________________________ Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
