Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

H.323 trunk between CUCM 7 and CCM3


I need help in the mentioned topic.

We have some version 3.2 callmangers on different sites. These CCMs are h.323 gateways of one so this is a star totpology.

We would like to migrate it to CUCM 7. So in the HUB a CUCM 7 was installed and I would use the old CCM 3 as a transit H323 GW till in the others will be added the new server as H.323 gw for the new phone numbers.

But one problem raised. If a phone registered to the old CCM 3 and try to call a phone registered to the new CUCM 7, the called phone can ring but the voice path doesn`t build, after ~7 second the call terminates. The CCM 3 waits for Media Negotiation. The CUCM 7 doesn`t send anything. It doesn`t send negotiation if I uncheck the "Wait for Far End Terminal Capability Set"

The other direction works properly. (Call originated from CUCM 7 registered phone to CCM 3 reg. phone.)

As I seen as difference, the CUCM 7 sends a NOTIFY message after the CONNECT message.

These don`t start negotiation of Teriminal Capability, nor the CCM 3 neither CUCM 7.

Could anybody help me?


Cisco Employee

Re: H.323 trunk between CUCM 7 and CCM3

You may be hitting CSCea52747 where masterslave negotiation of H245 connection fails.

3.2(3)SR1 has the fix for this, what version u running?

hope this helps

New Member

Re: H.323 trunk between CUCM 7 and CCM3

The versions are:


I am not sure,

CSCea52747: Calls through an Avaya H323 gateway sometimes fail at Master/Slave determination.

But Master/Slave determ. is after the H.245 negotiation. (once I seen this kind of faliure, but int the good direction)