Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

Current Sessions Overview

SBR Carrier tracks the status of user connections that it authenticates in a current sessions table (CST). Because the CST is based on RADIUS accounting data, the list of active sessions is accurate only if all of your NAD are configured to support RADIUS accounting. To accurately track session activity, you need to ensure:

  • All clients in your configuration support RADIUS accounting
  • All clients are configured to send accounting messages to SBR Carrier

You use the Web GUI to search for all sessions, or specify certain criteria and display only sessions that match that criteria. The Web GUI searches the current session table (CST) to find the sessions.

The Current Sessions page is used for managing and controlling sessions. With the basic SBR Carrier license, you can perform the query, view, and delete functions. The Query button displays all sessions that meet the criteria defined by the Session Query parameters. The View button displays the details for the selected session. The Delete button deletes the selected session from the SBR Carrier current sessions table.

Note: For tunnel connections, if SBR Carrier was used to authenticate both the user and the tunnel, then two entries are displayed in the Current Sessions page: one entry for the authenticated user, and one for the authenticated tunnel.

Note: Deleting a session does not disconnect the session, it only deletes the session from the CST. To disconnect a session, see Executing CoA and Disconnect Requests Using Web GUI .

If you are using the optional Session Control module license, you can also issue CoA/DM actions from the Current Sessions page. By default, the special actions of Query, View and Delete are predefined in the deviceModels.xml file.

When you define an action in the deviceModels.xml file, it appears as a button in the Current Sessions page. In the example discussed in Figure 252, the action boost is defined as an action in the deviceModels.xml file. If this action is defined in your deviceModels.xml file, a button labeled “boost” would be displayed in the Current Sessions page.

The Web GUI also contains buttons for the actions Disconnect, InterceptOn and InterceptOff. These buttons reflect CoA actions defined in the deviceModels.xml file. The Disconnect option or button disconnects one or more selected sessions. The InterceptOn and InterceptOff options or buttons enable you to comply with Law Enforcement Agency (LEA) requests for lawful intercept. To start the lawful intercept using the Web GUI, select a session and then select Device Action > InterceptOn. To stop the lawful intercept using the Web GUI, select the same session and then select Device Action > InterceptOff.

Note: To support the Disconnect and InterceptOn and InterceptOff actions on a NAD in your network, you must define the make and model of each NAD in the deviceModels.xml file. If these are not defined, invoking the action fails.

Modified: 2017-09-27