Hi, I think a UAS is forbidden to include a Session-Expires header field in the UPDATE request and a UAC should reject it. In that case, the value of session refresher in 200 OK of INVITE MUST be uac.
Regards, Shinji >Hello, > >I have some queries in the below scenario : > UAC UAS > ----- INVITE --------------------------------> > (Session-Expires:3600;refresher=uac) > > <------------------ 183 Session Progress ----- > > ----- PRACK ---------------------------------> > > <------------------------ 200 OK (PRACK) ----- > > <-------------------------------- UPDATE ----- > (Session-Expires:3600;refresher=none) > > ----- 200 OK --------------------------------> > (Session-Expires:3600;refresher=uac) > > <----------------------- 200 OK (INVITE) ----- > (Session-Expires:3600;refresher= ???) > >[Query]: What should be the value of session refresher in 200 OK of INVITE? > >There could be two cases: > >Case 1: The value of refresher can be according to INVITE received. > >* In this case if UAS sends 200 OK of INVITE with refresher value >which was in INVITE then the question is "can UAS send a different refresher >in early UPDATE?" Or we can say that "can UAS have a different negotiation >for refresher value in early UPDATE transaction and in INVITE received >transaction?" >Case 2: The value of refresher in 200 OK of INVITE can be according to the >value of refresher negotiated in early UPDATE. > >* In this case if UAS sends 200 OK of INVITE with refresher value >which was negotiated in early UPDATE then it will violate RFC 4028 as in fig. >below : > > >[cid:image003.jpg@01D17A2C.3DFE22F0] > > > >Please share your inputs for the above queries. > >Thanks & regards, >Mayank Sharma --- このEメールはアバスト アンチウイルスによりウイルススキャンされています。 https://www.avast.com/antivirus _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
