Conference Connection is set up and a conference is scheduled, the user calls the conference directory number and immediately gets a fast busy signal

[TCC_2]

Core Issue

Call routing may not be properly configured.

Resolution

To resolve this issue, perform these steps:

1. Verify that the user has the n.!# Route Pattern (RP), where n is any number representing the RP.
2. Make sure the user has .!# for call termination, as Cisco CallManager expects this for call termination.

For more information, refer to these documents:

• Cisco Conference Connection Administration Guide 1.2
• Cisco Conference Connection 1.2 Users Guide
• Release Notes for Cisco Conference Connection 1.2
• Cisco Conference Connection Administration Guide (1.1)