Mahesh,
when UAS is sending 200 after ACK then it could be that UAS is not understaending your ACK request.
ensure that your ACK request is matching:
- request uri from INVITE (or record route) - to/from headers incl. TAGS (to-tag from 200) - call-id from INVITE - cseq from INVITE
Have in mind this could also be a proxy bug and without further details it is only possible to give hints. At least, maybe your ACK is never reaching the right destination.
Regards,
Michael
On Nov 30, 2004, at 6:17 AM, mahesh akarapu wrote:
Hi all,
I have a doubt regarding how ACK requests are handled.
I am trying to establish a SIP session. The following is the scenario.
A------------B
INV--------->
<----------100
<----------180
<----------200
ACK--------->
Till this point, it is OK.But after this there are repeated 200Ok from B
as below.
<----------200
ACK--------->
<----------200
ACK--------->
I guess according to the RFC 3261, once ACK is received, the UA should stop sending the 200 OK.Could someone please tell me if this a possible scenario, that is under what circumstances 200 OK is sent after recieving ACK. I could not get the answer for this from the RFC.
Could someone answer this.
thanks Mahesh
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
