I guess it all depends on where you want the redirection to take place. If you want to perform some type of call limitation to a specific network, then you need the redirection to take place at the proxy and besides it's another level of unnecessary signaling. Another thing is that it's easier to control how the processing of multiple routes in handled. Some proxies will fork out the request when no "Q" values are present and some will process them until you either have success or run out of routes. By routing the 300 back to the originating GW, each attempt to resolve the route would be considered as a call. -----Original Message----- From: Juha Heinanen [mailto:jh@tutpro.com] Sent: Monday, April 05, 2004 1:36 PM To: Mike Morrison Cc: 'serusers(a)lists.iptel.org' Subject: [Serusers] 3xx Response Processig Issue Mike Morrison writes: a i once wrote a function that did that, but then i started to think that it's not a good idea for the proxy to turn a 3xx response into a new invite. if the user has decided to redirect the call, it is best that the redirection reply goes all the way to the calling party, which can then decide if he/she wants to proceed with the new destination. the proxy is not in the position to do that decision. -- juha