> According to the SIP RFC the UAS seems to be entitled > to treat the re-transmitted MESSAGE request as a new > request since it can rely on the fact that SIP requests > are never retransmitted over reliable transports. Has > anyone encountered this particular problem and come > up with a pragmatic solution?
The UAS cannot assume that requests will not be retransmitted over reliable transports (such as TCP). RFC 2543 indicated to use the same retry rules when sending over reliable and non reliable. RFC 3261 adjusted the retry rules; however I don't think that it adjusted how the UAS would behave upon receiving the retry. The issue with RFC 3261 was that it indicate 0 as the default Timer J value for TCP/SCTP. You can fix the issue by increasing Timer J to be the same as it would be for UDP. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
