Comments inline... Thanks & Regards, Nataraju A.B. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:sip-implementors- > [EMAIL PROTECTED] On Behalf Of Andreas Byström > Sent: Friday, July 14, 2006 3:27 AM > To: [email protected] > Subject: [Sip-implementors] "override" expires in Inivte requests? > > Hi all, > > I have a question about the Expires header in an Invite. If a UA receives an > invite (in my particular case the UA is an IVR application) and the UA wants > to start sending and receiving voice without sending a 200 OK it can do so > by responding with say 180 or 183 that includes the SDP answer to the offer > in the Invite. Now if the incoming invite included an Expires header with > value 25, and the UA wants to keep the "early media" for a longer time > (still with no 200 OK "answer"), is there something the UA can do? I checked > the RFC and to me it looks like the Expires is setting how long time the > offered session is available, and there has to be a final response within > that time. Maybe I did misunderstand the RFC or is there some other way to > only use provisional response? Any help is appreciated >
[ABN] I dont know of any reference doc/section mentioning this one.. The following is my personal opinion about this topic. Once you get the response for any request you can update the life time of the transaction by the expires header in the response. Similar logic been used for SUB-NTFY mechanism (here it's been intended for dialog life time than transaction) and been updated by 2xx for SUBSCRIBE request. This is not exactly same as SUB-NTFY mechanism, but in the same line we can extend Expires duration for INV transaction by the 1xx responses. > Regards, > // Andreas > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
