Session Closing State

Session Closing State

Last updated: May 24, 2006

The access terminal (AT) may close the session to conserve battery power, or because the user has turned it off. The network may order the AT to close the session (to free up its assigned UATI) if there is no activity for an extended time (see Session Close ).

In the session closing state, the test set is in the process of closing the current session.

Close the session by sending the CALL:SCLose command, or by selecting Close Session . This will close the data connection and the session at one time. See also Close Session Before Testing New AT .

You can close the session at any time, and the data connection will be taken to the idle state. However, most ATs will try to immediately re-establish a session (see Session Negotiate State ). You can prevent the AT from re-establishing a session by turning Call Limit Mode on (see Other Considerations for details).

The session closing state is a transitory state (see TAP/ETAP Data Connection Processing Lifecycle and Packet Data Connection Processing States Lifecycle ).

To query the state of the data connection, see Data Connection State Synchronization .

Related Topics


GPIB Command: CALL:SCLose

Programming: Step 7: End the Connection

Manual Operation: How Do I Close the Session?

TAP/ETAP Data Connection Processing States Lifecycle

TAP/ETAP Data Connection Call Flow

Packet Data Connection Processing States Lifecycle ( Lab Application Only )

Packet Data Connection Call Flow ( Lab Application Only )

Data Connection State Synchronization

Troubleshooting Data Connection Processing