Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
TAPI assigns session identifiers that are unique for each session and application. An application uses a session identifier to communicate with TAPI concerning a specific session. An application typically obtains an identifier either by creating a new communications session or when TAPI offers a session.
A session identifier cannot be used to pass information to another application. For this purpose, use the Call ID, which may be assigned by a service provider.
See Initiate a session for information on operations that create sessions and return a session identifier. See Respond to session initiated elsewhere for operations that acquire session identifiers from TAPI. See Terminate a Session for information on releasing session resources.
All service providers must support some form of session identification.
TAPI 2.x: The primary identifier of a communications session is the call handle.
TAPI 3.x: A session is represented by a Call Object and the primary identifier is a pointer to the ITCallInfo interface.