This document describes how to troubleshoot the 480 Temporarily Not Available or No Route for Bandwidth Calculation error messages that appear on an endpoint or in the Cisco TelePresence Video Communication Server (VCS) search history.
Troubleshoot Bandwidth Issues
These error messages can appear in the VCS search history or on the endpoint that initiated the call, and they usually indicate that there is not enough bandwidth available to route the call. If any of the endpoints in the call are registered to a VCS, or if the call passes through a VCS, then the messages might appear due to bandwidth restrictions that are applied on the system or missing links.
Complete these steps in order to troubleshoot the issue on any of the endpoints in the call that are registered to a Cisco VCS:
- Navigate to Status > Registrations > By device or Status > Registrations > By alias in order to determine the subzone to which the endpoint is registered.
- Click the endpoint registration in order to reach the Registration Details page. The name of the subzone appears in the Node field.
- Check the bandwidth restrictions that are applied to that subzone:
- If the endpoint is registered to the default subzone, navigate to VCS configuration > Local Zone > Default Subzone.
- If the endpoint is registered to any other subzone, navigate to VCS Configuration > Local Zone > Subzones.
Complete these steps in order to troubleshoot the issue on any VCS through which the call passes, which includes any VCS to which the endpoints are registered:
- Navigate to VCS Configuration > Bandwidth > Links and verify that links exist between the subzones and zones (that are involved in the call) over which the call can be routed. You might need to manually add the necessary links or restore the default links. In order to complete this process, enter the xcommand DefaultLinksAdd command into the CLI.
- If the links exist, click each link name in order to reach the Edit Link page. In the Status section, check the current number of calls in progress on the link. These calls might have consumed all of the available bandwidth.
- Check the bandwidth limitations on any pipes that are applied to the links in order to verify that there is sufficient bandwidth to place a call.