> Even though the RFC recommends this way, can you help > us to know how most of the stack do the transaction matching.
I have no clue how most stacks behave. > But in any case is it acceptable to have 2 UAs > generating the same branch value? RFC 3261 is inconsistent concerning if it must be globally unique or only globally unique for client. Even if the sender interprets as only unique for client, RFC 3261 section 17.2.3 still requires the receiver to use the Via sent-by within the transaction matching. > Also can you help me for #b question? > > b> In the same context, if the BYE is received by a UA, > >should the UA (underlying SIP stack) respond to BYE and > > immediately remove it from transaction table? The letter timers are discussed within RFC 3261. Appendix A presents a synopsis. RFC 3261 allows some timing flexibility since using the default value is not mandatory. > > Few questions > > > > 1> What is purpose of keeping the transaction data (i.e. branch ID) > > in transaction table once the BYE is processed? To follow rfc3261 or accommodate rfc2543 devices. Vendors also might have other reasons. > > 2> Is there any standard which mentions about how long it should > > keep the transaction in the table after it has processed BYE? RFC 3261; it obsoleted RFC 2543 which has different recommendations. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
