[reSIProcate] what's different between stale and state

[Byron Campen]

	When the TU sends a 2xx response in a server INVITE transaction,  
this puts us in a unique state. The stack does not expect an ACK for  
this transaction (ACK/200 is a new transaction), and the TU may  
retransmit the 200 (and the stack is obligated to forward it). This  
state is not defined in 3261, but this is a known bug in the RFC.  
(see http://bugs.sipit.net/show_bug.cgi?id=769 for details)

Best regards,
Byron Campen

> Hello:
>
> In  TransactionState.cxx, there are some process(), contain   void  
> processClientStale TransactionMessage* msg);
>       void processServerStale(TransactionMessage* msg). I don't  
> know what is stale. I don't find stale in rfc3621 also. I only find  
> state and stateless in rfc3621.
>     I hope someone can help me.
> Thanks
>
> cloud_l
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061108/6c1a20a0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2369 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20061108/6c1a20a0/attachment.bin>