Hello, I have a call manager bug. I am not goign to open a TAC case for this, because Cisco is charging us for TAC cases. This relates to CM 4.1.3 as well
as 6.0 and maybe 6.1 as well.
Let's take a look at an example. You have Calling search space X containing partition A. Calling search space Y contains partition B. There is a translation pattern in partition A. An incomming gateway has a calling search space X, which ony contains the translation pattern. The translation pattern has a calling search space Y. There is also a CTI port in partition B.
When you perform a call through the gateway to the CTI port you get a busy tone. The only solution is to assign a calling search space to the original gateway which contains both partitions A and B.
This is not specific to any specific scenario or call manager service release. It alwas appears once a CTI port gets involved.
You don't believe? just test it and you will see.