- Gold, 750 points or more
The calls made within a Cisco CallManager cluster can fail with these symptoms:
- Wrong destination: The call might reach a wrong destination if the called phone has call forward configured and this information is not synchronized with the Structured Query Language (SQL) database.
- Busy signal: To resolve any busy signal issues, refer to MWI is not turning off or on for all Cisco IP phones and voice mail is integrated via a VG248 using SMDI
- Re-order (fast busy) tone: The most common reason for receiving re-order (fast busy) is that the calling party does not have the rights to call the called party.
A re-order tone can be caused by these various Calling Search Space (CSS) and partition configuration issues:
- The calling phone does not contain any CSS, but the called phone is in a partition or the calling phone has CSS configured, but the called phone is in a different partition other than the configured CSS.
To resolve this issue, ensure that the calling party's phone contains a CSS that includes the called party's partition.
- The calling phone has CSS configured, but the called phone is not in any partition or the calling phone does not contain any CSS nor does the called phone's directory number belong to any partition.
To resolve this issue, restart the devices associated with the CSS (if any), restart the devices associated with the partition (if any) and restart the called party phone. If the failure still occurs, perform the steps in Set Up Cisco CallManager Traces for Cisco Technical Support.
- The configuration appears acceptable (the calling phone's CSS includes the called phone's directory number partition).
To resolve this issue, try resetting the CSS, partition and both phones involved. If the failure still occurs, perform the steps in the Set Up Cisco CallManager Traces for Cisco Technical Support document.
For more information on CSS and partitions, refer to these documents: