<div class="gmail_quote">
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div> </div>
<div>I'm facing a CANCEL problem now. The problem can be described as "UAC canceled the INVITE but UAS still state ringing status"</div>
<div>The UAS is a desk phone connected to VoIP network by a VoIP gatway, the SIP server is OpenSIPS 1.5.</div>
<div> </div>
<div>Based on the SIP singaling at UAC side, there scenarios to cause the problem:</div>
<div><strong>1. Cancel before 407 Proxy Authentication Required</strong><br>INVITE -><br>100 -><br>CANCEL-><br>200 for CANCEL ( from proxy server)<-<br>407 for INVITE <-<br>ACK -><br>INVITE (with authorization) -><br>
180 <-</div>
<div> </div>
<div>In this case, the INVITE with authorization caused the UAS rining. </div>
<div>My question is shall UAC send INVITE after receive 407 if the first INVITE is canceling?<br>...</div>
<div><strong>2. Cancel after 407 Proxy Authentication Required.</strong><br>INVITE -><br>100 -><br>407 <-<br>CANCEL-><br>400 for CANCEL <-<br>ACK -><br>INVITE (with authorization) -></div>
<div>180 <-<br></div>
<div>The reason caused UAS rining is same with case 1. </div>
<div>How to handle this scenario?<br clear="all">The cancel was treated as bad request due to the INVITE has generate final response 407.</div>
<div>Shall UAC send CANCEL again when receive 180?<br>-- </div>
<div>Best Regards,<br>Steven Wu<br></div></blockquote></div><br><br clear="all"><br>-- <br>Steven Wu<br>Teleca Mobile Solution<br>