Topic Last Modified: 2012-06-29
The Call Admission Control Report provides information about peer-to-peer and conferencing sessions that were conducted under restrictions set in place by Call Admission Control. Call Admission Control, introduced in Microsoft Lync Server 2010, provides a way for administrators to allow (or not allow) communication sessions based on bandwidth constraints. For example, administrators can create policies that impose a limit on the amount of bandwidth available for voice and video calls. If that bandwidth limit has been reached, then no new voice or video calls can be placed until one of the current calls has ended and freed up the required network resources.
Accessing the Call Admission Control Report
The Call Admission Control Report is accessed from the Monitoring Reports home page. From the Call Admission Control Report you can drill down to either of the following reports:
-
Conference Detail Report – To access this report, click the Details metric from a conference session.
-
Peer-to-Peer Session Detail Report – To access this report, click the Details metric for a peer-to-peer session.
Making the Best Use of the Call Admission Control Report
To get a list of calls that failed because of insufficient bandwidth, select Calls rejected because of call admission control from the Call category dropdown list. Most of the returned calls will likely have a diagnostic ID of 5:
Insufficient bandwidth to establish session. Attempt PSTN re-route.
That indicates that Call Admission Control limitations were preventing the call from being made on the VoIP network.
Filters
Filters provide a way for you to return a more finely-targeted set of data or to view the returned data in different ways. For example, the Call Admission Control Report enables you to filter calls by the user who initiated the call or by the user who was being called. You can also choose how data should be grouped. In this case, calls are grouped by hour, day, week, or month.
The following table lists the filters that you can use with the Call Admission Control Report.
Call Admission Control Report Filters
| Name | Description |
|---|---|
|
From |
Start date/time for the time range. To view data by hours, enter both the start date and time as follows: 7/17/12012 1:00 PM If you do not enter a start time, the report automatically begins at 12:00 AM on the specified day. To view data by day, enter just the date: 7/17/12012 To view by week or by month, enter a date that falls anywhere within the week or month that you want to view (you do not have to enter the first day of the week or month): 7/13/2012 Weeks always run from Sunday through Saturday. |
|
To |
End date/time for the time range. To view data by hours, enter both the end date and time as follows: 7/17/12012 1:00 PM If you do not enter an end time, the report automatically ends at 12:00 AM on the specified day. To view data by day, enter just the date: 7/17/12012 To view by week or by month, enter a date that falls anywhere within the week or month that you want to view (you do not have to enter the first day of the week or month): 7/13/2012 Weeks always run from Sunday through Saturday. |
|
Pool |
Fully qualified domain name (FQDN) of the Registrar pool or Edge Server. You can either select an individual pool or click [All] to view data for all the pools. This drop-down list is automatically populated for you based on the records in the database. |
|
Activity type |
Type of activity. Select one of the following activities:
|
|
Call category |
Indicates the reason that CAC was used for the call. Select one of the following:
|
Metrics for Peer-to-Peer Sessions
The following table lists the information provided in the Call Admission Control Report for peer-to-peer sessions (that is, sessions involving just two participants).
Metrics for Peer-to-Peer Sessions
| Name | Can you sort on this item? | Description |
|---|---|---|
|
Detail |
No |
When you click this item, the report shows you a Peer-to-Peer Session Detail Report for the specified session. |
|
From user |
Yes |
SIP address of the user who initiated the session. |
|
To user |
Yes |
SIP address of the user who was invited to join the session. |
|
Modalities |
Yes |
Communication modalities (such as audio and video) that were used during the session. |
|
Invite time |
Yes |
Date and time the initial session invitation was sent to the From user. |
|
Response time |
Yes |
Date and time that the invitation acceptance was received. |
|
End time |
Yes |
Date and time that the session ended. |
|
Diagnostic ID |
Yes |
Unique identifier (in the form of an ms-diagnostics header) attached to a SIP message that often provides information useful in troubleshooting errors. Diagnostics headers are optional (it is possible to have SIP sessions that do not include these headers), and diagnostic IDs are reported only for sessions that experienced problems of some kind. |
Metrics for Conferencing Sessions
The following table lists the information provided in the Call Admission Control Report for conferencing sessions (that is, sessions involving three or more participants).
Metrics for Conferencing Sessions
| Name | Can you sort on this item? | Description |
|---|---|---|
|
Conference URI |
Yes |
Unique identifier for the conference. When you click this item, the report shows the individual conference participants. |
|
Organizer |
Yes |
SIP address of the user who organized the conference. |
|
Pool |
Yes |
Edge Server used in the conference. |
|
Start time |
Yes |
Date and time that the conference started. |
|
End time |
Yes |
Date and time that the conference ended. |
Metrics for Individual Conference Participants
The following table lists the information provided in the Call Admission Control Report for individual conference participants.
Metrics for Individual Conference Participants
| Name | Can you sort on this item? | Description |
|---|---|---|
|
Role |
No |
Role (for example, Presenter) played by the conference participant. |
|
Participant |
No |
SIP address of the conference participant. |
|
Connectivity |
No |
Network connectivity (typically From Internal or From External) for the participant. |
|
Modality |
No |
Conference type (for example, A/V conferencing). |
|
Join time |
No |
Date and time that the participant joined the conference. |
|
Leave time |
No |
Date and time that the participant left the conference. |
|
Diagnostic ID |
No |
Unique identifier (in the form of an ms-diagnostics header) attached to a SIP message that often provides information useful in troubleshooting errors. Diagnostics headers are optional (it is possible to have SIP sessions that do not include these headers), and diagnostic IDs are reported only for sessions that experienced problems of some kind. |