locked
Lync CAC issue RRS feed

  • Question

  • We turned on Logging on Bandwidth Policy Server Configuration (set-csbandwidthpolicyserverconfiguration –enablelogging $true) so we can capture how much audio/video is being used between our Lync sites. 
    In our Lync environment, all video is CIF quality (we don’t allow VGA or HD).  We don’t want video to go higher than CIF because we don’t have the network bandwidth to handle it.   The Bandwidth log is reporting a peer-to-peer video call between user MWATSON(location:OAK) and TMARTINEZ(location:PHX) to use 520 Kbps while the Call Detail Report CIF and using much less bandwidth.

    Sunday, July 1, 2012 6:23 PM

Answers

  • It is clear from the Monitoring report that the call was only using CIF from both caller and callee.  I would adjust the bandwidth policies to match what you actually want to use and not an upper limit that cannot be achieved.  The only thing that I can think of is that the resource kit tool is showing bandwidth reserved and not bandwidth consumed.  When that CAC call is set up, the client will reserve the session bandwidth allowed and then should commit the actual bandwidth used.

    Tim Harrington | Lync: MCM/MVP | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

    • Proposed as answer by Sean_Xiao Friday, July 6, 2012 7:40 AM
    • Marked as answer by Sean_Xiao Wednesday, July 11, 2012 6:25 AM
    Monday, July 2, 2012 2:47 AM

All replies

  • We turned on Logging on Bandwidth Policy Server Configuration (set-csbandwidthpolicyserverconfiguration –enablelogging $true) so we can capture how much audio/video is being used between our Lync sites. 
    In our Lync environment, all video is CIF quality (we don’t allow VGA or HD).  We don’t want video to go higher than CIF because we don’t have the network bandwidth to handle it.   The Bandwidth log is reporting a peer-to-peer video call between user MWATSON(location:OAK) and TMARTINEZ(location:PHX) to use 520 Kbps while the Call Detail Report CIF and using much less bandwidth.

    • Merged by Sean_Xiao Tuesday, July 3, 2012 7:26 AM
    Sunday, July 1, 2012 6:21 PM
  • The monitoring report will show the last codec used.  What is your video per session limit set at in your CAC bandwidth policy?  Set it to 300K and it should never connect with VGA.

    If you want to create a policy outside of CAC to control video codecs for everyone, you can use the Set-CsMediaConfiguration -MaxVideoRateAllowed parameter and set to CIF250K.  You can also control conferencing codecs with the conferencing policy, Set-CsConferencingPolicy.


    Tim Harrington | Lync: MCM/MVP | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

    Sunday, July 1, 2012 8:20 PM
  • Hi Tim,

    Thank you for your reply. Here is my CAC bandwidth policy info and I already set my CIF usage by running the command Set-CsMediaConfiguration -MaxVideoRateAllowed parameter and set to CIF250K.

    ------------------------------------------------------------------------

    Get-CsNetworkBandwidthPolicyProfile | fl 

    Identity          : NA YYC
    BWPolicy          : {BWLimit=300;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=260;BWSessionLimit=700;BWPolicyModa
                        lity=Video}
    BWPolicyProfileID : NA YYC
    Description       :

    Identity          : NA CLE
    BWPolicy          : {BWLimit=450;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=520;BWSessionLimit=700;BWPolicyModa
                        lity=Video}
    BWPolicyProfileID : NA CLE
    Description       :

    Identity          : NA HOU
    BWPolicy          : {BWLimit=600;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=520;BWSessionLimit=700;BWPolicyModa
                        lity=Video}
    BWPolicyProfileID : NA HOU
    Description       :

    Identity          : NA TRI
    BWPolicy          : {BWLimit=750;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=520;BWSessionLimit=700;BWPolicyModa
                        lity=Video}
    BWPolicyProfileID : NA TRI
    Description       :

    Identity          : NA LGV
    BWPolicy          : {BWLimit=450;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=260;BWSessionLimit=700;BWPolicyModa
                        lity=Video}
    BWPolicyProfileID : NA LGV
    Description       :

    Identity          : NA MEX
    BWPolicy          : {BWLimit=450;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=520;BWSessionLimit=700;BWPolicyModa
                        lity=Video}
    BWPolicyProfileID : NA MEX
    Description       :

    Identity          : NA YUL
    BWPolicy          : {BWLimit=300;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=520;BWSessionLimit=700;BWPolicyModa
                        lity=Video}
    BWPolicyProfileID : NA YUL
    Description       :

    Identity          : NA PHL
    BWPolicy          : {BWLimit=1200;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=1300;BWSessionLimit=700;BWPolicyMo
                        dality=Video}
    BWPolicyProfileID : NA PHL
    Description       :

    Identity          : NA PHX
    BWPolicy          : {BWLimit=900;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=520;BWSessionLimit=700;BWPolicyModa
                        lity=Video}
    BWPolicyProfileID : NA PHX
    Description       :

    Identity          : NA OAK
    BWPolicy          : {BWLimit=3600;BWSessionLimit=200;BWPolicyModality=Audio, BWLimit=6500;BWSessionLimit=700;BWPolicyMo
                        dality=Video}
    BWPolicyProfileID : NA OAK
    Description       :

    Identity          : SA GRU
    BWPolicy          : {BWLimit=450;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=260;BWSessionLimit=700;BWPolicyModa
                        lity=Video}
    BWPolicyProfileID : SA GRU
    Description       :

    Identity          : NA SAV
    BWPolicy          : {BWLimit=450;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=5;BWSessionLimit=700;BWPolicyModali
                        ty=Video}
    BWPolicyProfileID : NA SAV
    Description       :

    Identity          : EMEA FRA
    BWPolicy          : {BWLimit=2000;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=3000;BWSessionLimit=700;BWPolicyMo
                        dality=Video}
    BWPolicyProfileID : EMEA FRA
    Description       :

    Sunday, July 1, 2012 9:52 PM
  • Hi Tim,

    This is the CAC policy defined for affected sites (OAK, PHX):

    Video per session (OAK) : 700

    Video per session (PHX) : 700

    ---------------------------------------------------------

    Description       :

    Identity          : NA PHX
    BWPolicy          : {BWLimit=900;BWSessionLimit=175;BWPolicyModality=Audio, BWLimit=520;BWSessionLimit=700;BWPolicyModa
                        lity=Video}
    BWPolicyProfileID : NA PHX
    Description       :

    Identity          : NA OAK
    BWPolicy          : {BWLimit=3600;BWSessionLimit=200;BWPolicyModality=Audio, BWLimit=6500;BWSessionLimit=700;BWPolicyMo
                        dality=Video}
    BWPolicyProfileID : NA OAK

    ---------------------------------------------------------

    Sunday, July 1, 2012 9:58 PM
  • I would definitely drop the per session bandwidth to 300 if all you want to support is CIF.  I am assuming that both users are using Lync clients (not legacy OCS clients since those do not support CAC).

    Tim Harrington | Lync: MCM/MVP | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

    Sunday, July 1, 2012 10:06 PM
  • Tim,

    I've enclosed the Lync logging file data and CDR reports which seems differing in Video utilization.

    -----------------------------------------------

    Lync logging file data:

    Time - 2012-05-29T12:02:12
    LinkID
    Name(IS:Inter-Site Link; R:Inter-Region Link; S:Site to Region Link) - 8706baae-b446-5201-b9bc-dd582a90bd19
    Region - S:NA PHL

    Link Cap(Audio) -1200
    Link Util(Audio)- 361
    Link Cap(Video) -1300Link Util(Video) - 700

    -----------------------------------------------

    CDR Report

    -----------------------------------------------

    Video Stream (Callee -> Caller)

    Codec: x-rtvc1

    Inbound frame rate 14.8564 Outbound frame rate 14.8525

    Packet utilization: 6841 Bandwidth estimates: 90477 Kbps

    Avg. allocated bandwidth 698 Kbps Local frame loss rate 0.00 %

    Resolution: 352x288 Frame loss rate: 0.00 %

    Avg. round trip: 95 ms Max. round trip: 132 ms

    Avg. jitter: 0 ms Max. jitter: 1 ms

    Avg. bit rate: 239 Kbps Max. bit rate: 263 Kbps

    Avg. packet loss rate: 0.00 % Max. packet loss rate: 0.00 %

    Common Intermediate

    Format (CIF) quality ratio

    100.00 % VGA quality ratio 0.00 %

    HD quality ratio 0.00 %

    % time without frame drop 100.00 % % time with B frame drop 0.00 %

    % time with BP frame drop 0.00 % % time with BPSP frame

    drop

    0.00 %

    ---------------------------------------------------------

    Video Stream (Callee -> Caller)

    Codec: x-rtvc1

    Inbound frame rate 14.8564 Outbound frame rate 14.8525

    Packet utilization: 6841 Bandwidth estimates: 90477 Kbps

    Avg. allocated bandwidth 698 Kbps Local frame loss rate 0.00 %

    Resolution: 352x288 Frame loss rate: 0.00 %

    Avg. round trip: 95 ms Max. round trip: 132 ms

    Avg. jitter: 0 ms Max. jitter: 1 ms

    Avg. bit rate: 239 Kbps Max. bit rate: 263 Kbps

    Avg. packet loss rate: 0.00 % Max. packet loss rate: 0.00 %

    Common Intermediate

    Format (CIF) quality ratio

    100.00 % VGA quality ratio 0.00 %

    HD quality ratio 0.00 %

    % time without frame drop 100.00 % % time with B frame drop 0.00 %

    % time with BP frame drop 0.00 % % time with BPSP frame

    drop

    0.00 %

    % time with BPSPI frame

    drop

    Sunday, July 1, 2012 10:42 PM
  • It is clear from the Monitoring report that the call was only using CIF from both caller and callee.  I would adjust the bandwidth policies to match what you actually want to use and not an upper limit that cannot be achieved.  The only thing that I can think of is that the resource kit tool is showing bandwidth reserved and not bandwidth consumed.  When that CAC call is set up, the client will reserve the session bandwidth allowed and then should commit the actual bandwidth used.

    Tim Harrington | Lync: MCM/MVP | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

    • Proposed as answer by Sean_Xiao Friday, July 6, 2012 7:40 AM
    • Marked as answer by Sean_Xiao Wednesday, July 11, 2012 6:25 AM
    Monday, July 2, 2012 2:47 AM