[SIPSERVLET_SPEC-5] Access to active SipApplicationSessions Created: 04/Oct/12  Updated: 26/Mar/14  Resolved: 26/Mar/14

Status: Resolved
Project: sipservlet-spec
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0-pr

Type: New Feature Priority: Major
Reporter: echeung Assignee: binod
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Currently there is no way to obtain a list of active SipApplicationSession within an application. Although most containers have a way to obtain the number of active SipApplicationSession and SipSession through some proprietary management interface, there is really no way to get to the actual SipApplicationSessions, and do things like check on their status and invalidate them for cleanup.

This feature request is for a way to obtain the list of all active SipApplicationSessions, probably as a method on SipSessionsUtil class. Note to maintain separation of applications, only the SipApplicationSessions belonging to the same application should be obtained.

From EG meeting on 3 October 2012: Due to concern about performance implications in a distributed environment,
even if optimizations are possible, it was agreed that this API method will only return the SAS within the same JVM, and not across a cluster.



 Comments   
Comment by binod [ 26/Mar/14 ]

Section 16.3 explains the details about accessing application sessions.

Generated at Wed May 27 11:47:52 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.