Topic Last Modified: 2012-09-28
Each record represents one peer-to-peer session, which could be a VoIP-VoIP phone call, two-party IM session, or other type of session. You can perform a table join with the Media Table to find the details of each media involved in this session.
Note that the IsUser1IntegratedWithDeskPhone and the IsUser2IntegratedWithDeskPhone fields have been dropped from the SessionDetails table used in Microsoft Lync Server 2013.
Column | Data Type | Key/Index | Details | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SessionIdTime |
datetime |
Primary, Foreign |
Time of session request. Used in conjunction with SessionIdSeq to uniquely identify a session. See the Dialogs Table for more information. |
||||||||||||||
SessionIdSeq |
int |
Primary, Foreign |
ID number to identify the session. Used in conjunction with SessionIdTime to uniquely identify a session.* See the Dialogs Table for more information. |
||||||||||||||
CorrelationId |
uniqueidentifier |
A GUID to correlate multiple sessions. |
|||||||||||||||
ReplaceDialogIdTime |
datetime |
Foreign |
ID number to identify the dialog which was replaced by current session. See the Dialogs Table for more information. |
||||||||||||||
ReplaceDialogIdSeq |
int |
Foreign |
ID number to identify the session. Used in conjunction with ReplacesDialogIdTime to uniquely identify a session that is replaced by this session. See the Dialogs Table for more information. |
||||||||||||||
User1Id |
int |
Foreign |
ID of one user in the session. See the Users Table for more information. |
||||||||||||||
User2Id |
int |
Foreign |
ID of the other user in the session. See the Users Table for more information. |
||||||||||||||
User1EndpointId |
uniqueIdentifier |
GUID that identifies the endpoint used by the first user in the session. This field was introduced in Microsoft Lync Server 2013. |
|||||||||||||||
User2EndpointId |
uniqueIdentifier |
GUID that identifies the endpoint used by the second user in the session. This field was introduced in Microsoft Lync Server 2013. |
|||||||||||||||
TargetUserId |
int |
Foreign |
The original To user URI in the SIP request. see the Users Table for more information. |
||||||||||||||
SessionStartedById |
int |
Foreign |
ID of the user who started the session. See the Users Table for more information. |
||||||||||||||
OnBehalfOfId |
int |
Foreign |
Indicates the ID of the user of who the caller is on behalf. See the Users Table for more information. |
||||||||||||||
ReferredById |
int |
Foreign |
ID of the user by who the call is referred. See the Users Table for more information. |
||||||||||||||
ServerId |
int |
Foreign |
ID of the front-end server used for this session. See the Servers Table for more information. |
||||||||||||||
PoolId |
int |
Foreign |
ID of the pool in which the session was captured. See the Pools Table for more information. |
||||||||||||||
ContentTypeID |
int |
Foreign |
Content type used in the session. See the ContentTypes Table for more information. |
||||||||||||||
User1ClientVerId |
int |
Foreign |
Client version used by User1. See the ClientVersions Table for more information. |
||||||||||||||
User2ClientVerId |
int |
Foreign |
Client version used by User2. See the ClientVersions Table for more information. |
||||||||||||||
User1EdgeServerid |
int |
Foreign |
Edge Server used by User1. See the EdgeServers Table for more information. |
||||||||||||||
User2EdgeServerid |
int |
Foreign |
Edge Server used by User2. See the EdgeServers Table for more information. |
||||||||||||||
IsUser1Internal |
bit |
Whether User1 is logged on from internal or not. |
|||||||||||||||
IsUser2Internal |
bit |
Whether User2 is logged on from internal or not. |
|||||||||||||||
InviteTime |
datetime |
The time of the first INVITE request. This field is typically populated by data generated from the initial INVITE message in the session. If there is no INVITE message then the field is populated with the date and time of the first relevant SIP message (BYE, CANCEL, MESSAGE, or INFO). This field is typically populated by data generated from the initial INVITE message in the session. If there is no INVITE message then the field is populated with the date and time of the first relevant SIP message (BYE, CANCEL, MESSAGE, or INFO). |
|||||||||||||||
ResponseTime |
datetime |
The time of the response to the first INVITE message. This field is typically populated by data generated from the initial INVITE message in the session. If there is no INVITE message then the field is populated with the date and time of the first relevant SIP message (BYE, CANCEL, MESSAGE, or INFO). |
|||||||||||||||
ResponseCode |
int |
SIP response code to the session invitation. This field is typically populated by data generated from the initial INVITE message in the session. If there is no INVITE message then the field is populated with the date and time of the first relevant SIP message (BYE, CANCEL, MESSAGE, or INFO). |
|||||||||||||||
DiagnosticId |
int |
Diagnostic ID captured from SIP header. |
|||||||||||||||
CallPriority |
int |
Foreign |
Call priority. See the CallPriorities Table for more information. |
||||||||||||||
User1MessageCount |
int |
Number of messages sent by User1 during the session. |
|||||||||||||||
User2MessageCount |
int |
Number of messages sent by User2 during the session. |
|||||||||||||||
SessionEndTime |
datetime |
Time at the end of the session. |
|||||||||||||||
MediaTypes |
int |
A bit set that indicates the media type of this session. Listed are the definitions of the types:
|
|||||||||||||||
User1Flag |
smallint |
A bit set that indicates the User1 attributes. The following attribute definitions are listed:
|
|||||||||||||||
User2Flag |
smallint |
A bit set that indicates the User2 attributes. The following attribute definitions are listed:
|
|||||||||||||||
CallFlag |
smallint |
A bit set that indicates the call attributes. The following attribute definitions are listed:
|
|||||||||||||||
Processed |
bit |
For internal use by the Monitoring service. This field was introduced in Microsoft Lync Server 2013. |
* For most sessions, SessionIdSeq will have the value of 1. If multiple sessions start at exactly the same time, the SessionIdSeq for one will be 1, for another will be 2, and so on.