Only possibility is UAC sending Initial Invite having SE:900 and on getting 200ok with SE:600 . UAC not updating value and still starting timer with 900 sec. UAC behaviour looks incorrect Check what value was sent from UAC .
Regards Ankur Bansal On Wed, Jun 8, 2016 at 8:09 PM, Brett Tate <br...@broadsoft.com> wrote: > Hi, > > If I understand your question, you are wondering why the BYE is sent so > long after session expiration. > > If your interpretation of the call flow is correct, it sounds like the > device didn't follow the RFC 4028 section 10 recommendation to send the > BYE prior to expiration. You might want to ask the vendor. > > > > -----Original Message----- > > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > > implementors-boun...@lists.cs.columbia.edu] On Behalf Of NK > > Sent: Tuesday, June 07, 2016 3:41 PM > > To: sip-implementors@lists.cs.columbia.edu > > Subject: [Sip-implementors] Session Expire (BYE after 5 minutes of > session > > expire) > > > > Dear All, > > > > I have one call example where Session Expire in 200 Ok set to 600 > Seconds. > > > > But UAS never sent the UPDATE before this timer expire. > > > > After 900 Seconds UAC is sending BYE because they were expecting the > UPDATE > > from UAS, since the refresher is uas. > > > > Anyone faced this kind of problem where we are receiving BYE after 5 > minutes > > or something of session expire? > > > > Can any one please help me to understand or there experience. > > > > Regards, > > Nitin > _______________________________________________ > 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
