If you read sec. <a href="http://17.1.1.3">17.1.1.3</a> of RFC#3261 you'll see that the ACK must be built almost exclusive with the HF values from the original INVITE (to-tag is taken from reply); that should filter out SER misbehaviour.
<br><br>A firmware update might help.<br><br><div><span class="gmail_quote">On 9/26/06, <b class="gmail_sendername">Teran Jesus</b> <<a href="mailto:jteran@mcmtelecom.com.mx">jteran@mcmtelecom.com.mx</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello, i have a problem with the ATA 186 in the SER 0.9.6, when i generate a<br>call from my ata, when the ATA received the OK from the SER, the ATA don't
<br>generates the ACK correctly, this missing the user in the ACK, something<br>like this, ACK sip:XXX.XXX.XXX.XXX SIP/2.0, i believe the sip poroxy is<br>missing something in the OK, because i have tested this in the SER version
<br>0.8.12 and this don't have the same problem. Do you know how can i resolv<br>the problem?<br><br>_______________________________________________<br>Serusers mailing list<br><a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org
</a><br><a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br></blockquote></div><br>