we are observing some differences in the WebSphere SIP Application session time out behavior between WAS 7 & WAS 8.
We set the SIPApplicationSession timeout to 1 minute in our code (SipApplicationSession.setExpires(1)). When we deploy our application on WAS 7, the session gets timed out in 30 secs although it is set to 1 minute where as in WAS 8 it works correctly and session expires after 60 secs.
Am wondering if in WAS 7 the SIP Timer B is always set to T1 * 64 (T1 is 500 millisecs) and can't be changed....
Can some one explain more on when the SIP Timers get triggered by the SIP Container ?
Pinned topic unable to override the SIP Timer B value in WebSphe 7
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-27T15:45:35Z at 2012-12-27T15:45:35Z by NitzanNissim
NitzanNissim 060001FVFS3 Posts
Re: unable to override the SIP Timer B value in WebSphe 72012-12-27T15:45:35ZThis is the accepted answer. This is the accepted answer.Hi
We do know of any difference in the way setExpires work on WAS7 vs. WAS8. If you are experiencing a problem on 7 (session timed out after 30 sec) you should open a PMR to address it.
Regarding timer B - there is no relation between timer B and the SipApplicationSession timer that is defined in the JSR.
Timer B controls transaction level timeouts as defined on RFC 3261, while the applicative expiration timer will initiate a session expiration, as defined in JSR 289/116.
Regardless, the SIP stack timers (like timer B) are using the default values defined on RFC 3261 by default, but these values can be changed on both versions (see infocenter: http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=tsip_cfgtime)
The rules for triggering these SIP stack timers are as defined on RFC 3261.
The rules for triggering the SAS expiration timer, or application timers can be found on JSR 289 (WAS 8) or JSR 116 (WAS7)