<div dir="ltr">Reposting the query below.<div><br></div><div>Thanks</div><div>Ramesh</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 2, 2019 at 2:03 PM Ramesh Kandasamy <<a href="mailto:ramelcom@gmail.com">ramelcom@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>I have a question on the below call flow and if it is related to target refresh.</div><div><br></div><div>SIP UA establishes a TCP connection with SIP Proxy to initiate the call.</div><div> INVITE from SIP UA was sent from TCP port, say p1.</div><div>Call got answered and ongoing.</div><div>At some point, SIP UA closes TCP port p1 by exchanging TCP FIN/FIN ack.</div><div>Later within the same dialog, SIP UA establishes another TCP connection with the same SIP Proxy for the same call to send SIP INFO.</div><div> INFO from SIP UA was sent from TCP port, say p2.</div><div>SIP Proxy sends back the INFO response to this new TCP port p2.</div><div>But subsequent SIP requests are not routed from SIP Proxy to this new TCP port p2 of SIP UA. Rather, it attempts to send on p1 which fails.</div><div><br></div><div>My question is, is this INFO above considered as target refresh? Please note that Contact and dialog-id (From, To, Call-Id, R-uri) between the initial INVITE (from p1) and INFO (from p2) remains the same. IP address doesn't change either.</div><div><br></div><div>My thought is that the above flow is allowed and this is not a target refresh. So, So, any subsequent SIP requests from SIP Proxy should ideally be sent to this new TCP port p2.</div><div><br></div><div>Please advise.</div><div><br></div><div>Thanks</div><div>Ramesh</div><div><br></div></div>
</blockquote></div>