I think the Path module from ser experimental tree, recently updated by Andreas Granig, could do that. Probably you would have to port it to openser.

Hi Klaus, Seems like I missed to mention the most important thing: We do have the mechanisms to store and retrieve all routes in place. What I am looking for is just the mechanism (OpenSER calls, order of calls) where/how to add some route headers within the registrar so that it can route the message to the destination. It's about plain SIP routing, nothing to do with path (although it's a path implementation). regards --Joachim _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

Hi Daniel, another question concerning this set of proxies I want to travers. I insert the first one with avp_pushto($duri...) But how do I get openser to insert this new header without forwarding it to itself (using forward).

It works with the following config Avpushto("$duri","adress1"); Avpushto("$Route","adress2"); Forward("itself"); Regards Johannes -----Ursprüngliche Nachricht----- Von: users-bounces(a)openser.org [mailto:users-bounces@openser.org] Im Auftrag von Daniel-Constantin Mierla Gesendet: Freitag, 21. Oktober 2005 10:47 An: Joachim Fabini Cc: 'Joachim Fabini'; users(a)openser.org Betreff: Re: [Users] Registrar-initiated Route changes on Invite? Hello Joachim, the solution is rather simple. If you have a set of proxies where you want to send the message, you have to add the address of the first one in dst_uri (see avp_pushto() -> $duri: http://www.voice-system.ro/docs/avpops/ar01s06.html#avp_pushto) and the rest of them in Route headers. Cheers, Daniel On 10/20/05 18:12, Joachim Fabini wrote: _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

Hi Daniel, Unfortunately your solution did not solve the problem. Any other idea? Maybe a detailed description of the task can help: Assume an OpenSER registrar that is responsible for our domain. This registrar receives an Invite for a callee within our domain. Our registrar has stored a route that is associated with the callee's contact (the callee is obviously registered with our registrar). Task: The Invite message is supposed to follow exactly this stored route to the contact/callee. How can we do this. Our approach: the OpenSER Registrar must do the following: 1. Replace the destination/Request URI with the contact address (no other proxy on the path can do this) 2. Insert the Route header (stored in an AVP) into the received Invite. 3. Relay this Invite message (including our route header) to the callee via the route described by our route header (i.e. relay the Invite to the first entry in our route header). It seems obvious and straight-forward how to do this - unfortunately our attempts do not show the expected result. (1) works and (2) works also, all we struggle with is (3). t_relay() ignores the route header field that we added and forwards the Invite directly to the contact address. This nonregarding that the route header field that we pushed into the Invite in step (2) IS added correctly to the message (Ethereal traces show that OpenSER appends the route header correctly to the message. But it does not send the message according to the route header but forwards it directly to the contact) Surprisingly: when the Registrar statlessly forwards the Invite message to itself (after step 2, i.e. with added route header) and then does t_relay, the route is taken correctly. Probably needless to mention that this forward to itself is not what we want... So: Any idea how we can overcome this problem? Can you maybe detail on the routing logic that prevents OpenSER from sending the INVITE via the correct route? Many thanks in advance, best regards --Joachim _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users