Hi All, My scenario is as follows, one SIP client sends one fresh SUBSCRIBE to SIP server via TCP, and SIP server sends 200OK back immediately. Unfortunately, SIP client does incorrect thing to retransmit SUBSCRIBE once before it gets final response. In this error case, when SIP server sends 200OK, associated transaction releases immediately. So for retransmitted SUBSCRIBE, transaction layer will regard it as a new msg, not retransmitted one, and will create a new transation. And dialog layer cann't find one matched dialog for retranmited msg because TO tag not match, so maybe will create a new dialog.
My question is how to defend the issue in SIP server. I think transaction layer cann't do anything. How about dialog layer, similar like early notify process to change dialog matching condition? Or let SIP server application layer check it, e.g., the user has been subscribed and reject it? Any suggestion, pls? Thanks and Regards, JC _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
