There are few things to consider for Early Update :
1. As session is established with 200ok Invite response only so whatever
happens before 200ok , those would be of no effect.
Having said that , Update should still carry same or different
session-expire params and 200ok update would be responded to as per RFC
4028 .
Once 200ok Invite comes then only the refresher and session-expire
interval would be finalized for the session .
2. Any refresh request(Reinvite/Update) after the session is established
will have effect on session expiry interval or refresher .
Regards
Ankur Bansal
On Mon, Jan 4, 2021 at 8:02 AM Ranjit Avasarala <ranjitka...@gmail.com>
wrote:
> yes it should
>
> On Mon, Jan 4, 2021 at 9:39 AM akashdeep vishnoi <akashanshu...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I am sending an Early Update request from UAC/UAS with changed
> > Session-Expire timer and refresher.
> > Should this Session Expire header value in Early Update request need to
> > follow the rules defined in RFC 4028 for response.
> >
> > Thanks,
> > Aakash
> > _______________________________________________
> > Sip-implementors mailing list
> > Sip-implementors@lists.cs.columbia.edu
> > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> >
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
