Re: [reSIProcate] what's different between stale and state

[Byron Campen <bcampen@xxxxxxxxxxxx>]

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@xxxxxxxxxxxxxxxxxxx

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

Attachment: smime.p7s
Description: S/MIME cryptographic signature