[reSIProcate] Re: Different contact in 180 & 200

[Robert Sparks]

Both the 180 and 200 have the same To tag? You should send the ACK to 
the
Contact in the 200. UPDATE can change the remote target between these
messages as well.

(Its a normal case to get a 180 from one leg and a 200 from another, 
but the To tags
  will be different - that's not the case you're talking about, right?)

RjS

On Feb 7, 2005, at 3:47 PM, derek wrote:

> If an endpoint sends you a INV-180 and a INV-200(same dialog) with two 
> different contact values, dum uses the contact in the 180 as the 
> remote target of the dialog.  As a result, the ACK to the 200 is 
> delivered to the wrong place. 
>
>   
>
> What’s the spec. say on this; can an early dialog have a different 
> remote target than the final dialog? 
>
>   
>
> In general, we don’t seem to handle target refresh requests properly.  
> When should the remote contact of a dialog change; AFAIK, it’s a 
> re-invite or the 200 to a re-invite only?
>
>  
>
> --Derek