Use this procedure if you want to split the audio and video bandwidth deductions into separate pools for video calls. By default, the system deducts the bandwidth requirement for both the audio stream and video stream from the video pool for video calls.
Note: When you enable this feature, CAC includes the bandwidth required for the IP/UDP network overhead in the audio bandwidth deduction. This audio bandwidth deduction equates to the audio bit rate plus the IP/UDP network overhead bandwidth requirement. The video bandwidth deduction is the video bit rate only.
Procedure
Step 1
|
From Cisco Unified CM Administration, navigate to System > Service Parameters.
|
Step 2
|
From the Server drop-down list, choose the publisher node.
|
Step 3
|
From the Service drop-down list, choose Cisco Call Manager.
|
Step 4
|
From the Clusterwide Parameters (Call Admission Control) area, set the value of the Deduct Audio Bandwidth Portion from Audio Pool for a Video Call service parameter to True.
|
Step 5
|
Click Save.
|
Verify
Use this section to confirm that your configuration works properly.
RTMT Alerts
Name : Hub_None->Tampa-MLK
ResourceType : 2
AppID : Cisco Location Bandwidth Manager ClusterID : PUB01-Cluster NodeID : SUB01 TimeStamp : Tue Aug 01 11:15:25 EDT 2018.
The alarm is generated on Tue Aug 01 11:15:25 EDT 2018
Alert Definition:
LocationOutOfResources: This counter represents the total number of times that a call through Locations failed due to the lack of bandwidth.
Explanation: The Location or Link connecting locations has run out of audio/video/immersive bandwidth and hence no further calls can originate or pass through the location/link. The out of resource condition may be temporary due to high number of calls during peak hours and may correct by itself when calls terminate and bandwidth is freed up.
Recommended Action: Consider adding additional bandwidth to the location/link under below option:
System > Location info > Location.
Enum Definitions - ResourceType
Value Definition
1 Audio bandwidth out of resource
2 Video bandwidth out of resource
3 Immersive bandwidth out of resource
You can also monitor this instance from CLI:
show perf query class "Cisco Locations LBM"
show perf query counter "Cisco Locations LBM" "BandwidthMaximum"
show perf query counter "Cisco Locations LBM" "BandwidthAvailable"
show perf query counter "Cisco Locations LBM" "CallsInProgress
Note: In case video bandwidth, you would need to increase by at least 384 kbps in order to allow one more video call to traverse this path. It might be set as high as the your network design supports.
You can also monitor the instances from RTMT as well:
Configure Alerts on RTMT
Ref Guide : RTMT Guide

Error Message:
%UC_Location Bandwidth Manager-5-LBMLinkISV: %[RemoteIPAddress=String][LinkID=String][LocalNodeId=UInt][LocalApplicationId=Enum][RemoteApplicationId=Enum][AppID=String][ClusterID=String][NodeID=String]: LBM link to remote application restored.
Explanation: This alarm indicates that the LBM has gained communication with the remote LBM. Note that the remote LBM should also indicate LBMLinkISV.
Recommended Action: Informational only; no action is required.
Reason Code - Enum Definitions
Enum Definitions - LocalApplicationId
Value Definition
700 LocationBandwidthManager
Enum Definitions - RemoteApplicationId
Value Definition
700 LocationBandwidthManager
Error Message:
%UC_Location Bandwidth Manager-1-LBMLinkOOS: %[RemoteIPAddress=String][LinkID=String][LocalNodeId=UInt][LocalApplicationID=Enum][RemoteNodeID=UInt][RemoteApplicationID=Enum][AppID=String][ClusterID=String][NodeID=String]: LBM link to remote application is out of service.
Explanation: This alarm indicates that the local LBM has lost communication with the remote LBM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).
Recommended Action: In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also, check for any alarms that might have indicated a CallManager OR location bandwidth manager failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.
Reason Code - Enum Definitions
Enum Definitions - LocalApplicationID
Value Definition
700 LocationBandwidthManager
Enum Definitions - RemoteApplicationID
Value Definition
700 LocationBandwidthManager
Troubleshoot
This section provides information you can use to troubleshoot your configuration.
In order to troubleshoot further you need these logs from Call manager with the use of RTMT:
- Call Manager Detailed level traces
- Location bandwidth manager traces