Hi Ellie, Thanks for the response and for tracking this issue. I can continue using 600 in the meantime.
Alan On 5/2/14 11:34 AM, "Eleanor Merry" <[email protected]> wrote: >Hi Alan, > >Thanks for highlighting this! > >We added the function to control the session-expires time as we use >session refreshes in our RF billing solution (and the length of the >refresh is the margin of error for billing in the case where a call >disappears without a BYE transaction). > >As you've pointed out, this doesn't comply with RFC 4028. What we're >planning therefore is to add support for the Min-SE header, and also add >a new configuration option 'max-session-expires'. This new configuration >option will be the maximum acceptable session-expires value that >Clearwater will accept in a Session-Expires/Min-SE header - if a client >sets a greater value then Clearwater will reject the call. We're tracking >this issue at https://github.com/Metaswitch/sprout/issues/529. > >In the meantime, can you continue to use a Session-Expires value of 600 >on your AS? Alternatively you can raise the value in Clearwater by adding >'default_session_expires=1800' to the /etc/clearwater/config file on your >Bono/Sprout, and restarting it ('service stop <bono/sprout>' - it'll be >restarted by monit). > >Ellie > >-----Original Message----- >From: [email protected] >[mailto:[email protected]] On Behalf Of >Kwon, Alan >Sent: 01 May 2014 22:16 >To: [email protected] >Subject: [Clearwater] 422 Session Interval Too Small > >Hi, > >I'm seeing a problem with Session-Expires header in a SIP INVITE. Client >is sending an INVITE with Session-Expires set to 1800, but Bono changes >it to 600 when forwarding the INVITE to Sprout. Eventually, my AS >receives the INVITE and returns 422 Session Interval Too Small with >Min-SE header set to 1800. Client turns around and re-sends the INVITE >with Session-Expires set to 1800 and also Min-SE set to 1800. But again, >Bono changes Session-Expires to 600... and it goes on... > >I don't see any configuration where this value can be changed. Even if it >were configurable, it should not be changing the value client sent in the >INVITE. It does not seem to handle Session Timers specified in RFC 4028. > >I'm running "Elite" release that got released today, but I saw this with >previous versions as well... I'm getting around by lowering >Session-Expires to 600 at my AS, but I wanted to raise this issue. > >Thanks, >Alan > >_______________________________________________ >Clearwater mailing list >[email protected] >http://lists.projectclearwater.org/listinfo/clearwater _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
