[reSIProcate] 200 OK is not retransmited after 180 Ringing

[Scott Godin]

Are you using DUM?  It is the application (UAS) layers responsibility to
retransmit 200's not the core stack.  If you are using DUM - this should
be handled.

-----Original Message-----
From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of Aziz
Sever
Sent: Thursday, August 11, 2005 4:28 PM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] 200 OK is not retransmited after 180 Ringing


Hello,
I am using resiprocate-0.9.0-5019 stack. The 200 Ok after 180 is getting
lost along the way.So there is no ACK from the other end
and resiprocate stack is not retransmiting 200 Ok. But RFC3261 in
section
13.3.1.4 it is mentioned that 200 Ok needs to be retransmited
until an ACK is received. Can anyone comment and help me out who needs
must
retransmit the 200 Ok, if there is no ACK.

Regards,

Aziz
------------------------------------------------------------------------
----
------------
Aziz Sever
ARGELA Technologies
Phone   : +90 212 328 12 48 / ext:131
Fax       : +90 212 328 12 47
E-mail   : aziz.sever at argela.com.tr
Address: ITU Kampusu Yapi ve Deprem Uygar
Merkezi K.2 34469 Maslak ISTANBUL-TURKEY


_______________________________________________
resiprocate-devel mailing list
resiprocate-devel at list.sipfoundry.org
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel