Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Sip-Servlets MSS-2.1.0.FINAL
Roadmap-Fix
New issue 183 by [email protected]: Container invalidates Sip
Application Session while in conference, ignores session timeout setting
http://code.google.com/p/sipservlets/issues/detail?id=183
What steps will reproduce the problem?
1. Deploy latest conference-demo-jsr309.war file on latest MSS v2.0 and MMS
v3.0.CR1
2. Join 2 participants into a conference by dialing sip url for each user
3. Leave the conference running and wait for at least 5 minutes. Make sure
audio is passing through bi-directionally. Around 4 minute mark, the audio
will stop to pass through and you should see messages in server.log file
that sip application session for conference service is being invalidated.
4. The package-info.java file has annotation for
SipApplication(sessionTimeout=1000). According to javadocs this should be
in minutes, so this should be enough. Tried changing this value but no
difference, same result as in point 3.
5. Also tested with sip.xml file and setting session-timeout element, make
no difference still same result as point 3.
What is the expected output? What do you see instead?
In the past this service would have no problem with conference, would
expect the conference to remain on until parties decide to exist the
conference. Right now the conference stops transmitting audio but both
parties are still connected, but if you hangup sip server reports a problem
that the sip session is already invalid.
What version of the product are you using? On what operating system?
Testing using MSS v2.0.0.FINAL-jboss-as-7.1.2 with media that comes with
archive, MMS v3.0.CR1. Testing on Mac OS X 10.7.5
Please provide any additional information below.
Should be able to checkout the latest code base from mobicents for
conference-demo-jsr309 and build and test to reproduce this problem.
