Re: [Users] Locally generated single-hop ACKs with Route headers

Hello, Hi Klaus, Thanks for your response. In answer to your question: yes, the INVITE does contain a Route header. Further info on the problem: There are 3 proxies between A and B parties. The INVITE message is routed from A-Party through Proxy-1, through Proxy-2 before finally reaching B-Party. The Route header first appears in the INVITE message sent by Proxy-1 and is removed at Proxy-2. There is an errored response message to this INVITE (e.g. 'Busy' or 'Request Terminated'). The errored response is acknowledged with a one-hop locally generated ACK at each point between B and A. I expected the ACK at Proxy-2 to take the same one-hop route as the original INVITE at Proxy-2, i.e. the ACK sent by Proxy-2 will contain routing data based on routing data from the INVITE previously sent by Proxy-2. What actually occurs is that the Route header in the ACK sent by Proxy-2 is a duplicate of the Route header of the INVITE that Proxy-2 has RECEIVED from Proxy-1 and NOT that of the INVITE message it had previously sent. Are you aware of this problem and any resolution and/or workarounds? We would like to remove this unwanted Route header from the ACK. How is it possible to do this (i.e. which routing block?)? The known issue described in the previous email (below) appears to prevent us from removing this header from the ACK. Are you or anyone else in the OpenSER community aware of any fix or resolution to this problem? Best regards, Andrew Augustin -----Ursprüngliche Nachricht----- Von: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Gesendet: Dienstag, 25. Juli 2006 18:15 An: Augustin, Andrew (external) Cc: users(a)openser.org Betreff: Re: [Users] Locally generated single-hop ACKs with Route headers I wonder why there are route headers in the ACK - they are only necessary if the INVITE also hed route headers (RFC3261, 17.1.1.3) regards klaus Augustin, Andrew (external) wrote: