What does '480 Temporarily Not Available' or 'No Route for Bandwidth Calculation' on my endpoint or in the Cisco TelePresence Video Communication Server (Cisco VCS) search history mean?
These messages can appear in the Cisco VCS search history or on the endpoint that initiated the call. It frequently means that there is no bandwidth available to route the call. If any of the endpoints in the call are registered to a Cisco VCS, or if the call passes through a Cisco VCS, this could be due to bandwidth restrictions that have been applied on that system, or missing links.
If any of the endpoints in the call are registered to a Cisco VCS:
- Determine which subzone the endpoint is registered to (Status > Registrations > By device or Status > Registrations > By alias, and then click on the registration to go to its Registration Details page. The name of the subzone will be shown in the Node field).
- Check the bandwith restrictions applied to that subzone. If the endpoint is registered to the Default Subzone this is done via VCS configuration > Local Zone > Default Subzone; if it is registered to any other subzone this is done via VCS configuration > Local Zone > Subzones.
On any Cisco VCS through which the call passes, including any Cisco VCS to which the endpoints are registered:
- Go to VCS configuration > Bandwidth > Links and check that there are links in existence between the subzones and zones involved in the call, over which the call can be routed. You may need to manually add the necessary links, or restore the default links (this can be done via the CLI by typing xcommand DefaultLinksAdd).
- If the links do exist, click on each link name to go to its Edit Link page. In the Status section, check the current number of calls in progress on the link. These calls may have consumed all the bandwidth available.
- Check the bandwidth limitations on any pipes applied to that link. It may be that there is insufficient bandwith to place the call.
This article applies to the following products:
- Cisco Video Communication Server
|June 16th, 2011||TAA_KB_179|