RE: [reSIProcate] 200 OK is not retransmited after 180 Ringing
The reason for this is described in RFC3261:
Section 13.3.1
Once the response has been constructed, it is passed to the INVITE
server transaction. Note, however, that
the INVITE server transaction will be destroyed as soon as it receives
this final response and passes it to
the transport. Therefore, it is necessary to periodically pass the
response directly to the transport until the
ACK arrives. The 2xx response is passed to the transport with an
interval that starts at T1 seconds and
doubles for each retransmission until it reaches T2 seconds (T1 and T2
are defined in Section 17). Response
retransmissions cease when an ACK request for the response is received.
This is independent of whatever
transport protocols are used to send the response.
-----Original Message-----
From: Aziz Sever [mailto:aziz.sever@xxxxxxxxxxxxx]
Sent: Thursday, August 11, 2005 4:47 PM
To: Scott Godin; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] 200 OK is not retransmited after 180 Ringing
Thanks for reply.
No I don't use DUM and unfortunately. Can you comment why I have to
use DUM to get this capability?
Regards,
Aziz
------------------------------------------------------------------------
----------------
Aziz Sever
ARGELA Technologies
Phone : +90 212 328 12 48 / ext:131
Fax : +90 212 328 12 47
E-mail : aziz.sever@xxxxxxxxxxxxx
Address: ITU Kampusu Yapi ve Deprem Uygar
Merkezi K.2 34469 Maslak ISTANBUL-TURKEY
-----Original Message-----
From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
Sent: Thursday, August 11, 2005 11:32 PM
To: Aziz Sever; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] 200 OK is not retransmited after 180 Ringing
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@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Aziz
Sever
Sent: Thursday, August 11, 2005 4:28 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxx
Address: ITU Kampusu Yapi ve Deprem Uygar
Merkezi K.2 34469 Maslak ISTANBUL-TURKEY
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel