We have following devices:-
Avaya PBX 8730 server with CM 5.2
Both these devices are integrated over H.323. Avaya PBX is configured as h.323 gateway in CUCM. I am facing two problems:-
1. If Avaya phones calls Cisco IP phone, the call gets connected but the caller id is not displayed on Cisco IP phone. Cisco IP phone displays as unknown number.
2. If Cisco phone try to call Avaya phone the call does not get connected & user hear fast busy tone. In dial number analyzer tool it shows that call is getting properly routed to h.323 gateway (Avaya PBX).
Please suggest to resolve this issue.
Paolo is right - you need to work with your Avaya compatriots to figure this out.
I'd start troubleshooting the caller ID at the source, but since there is no (Cisco) gateway to run debugs on can you verify from the Avaya side that caller ID information is being sent to your CallManager using the "Display Information Element (IE)"?
As for Cisco->Avaya call routing, if everything looks good in DNA right up to where it routes the call to the Avaya PBX I'd double-check all your configuration parameters on both sides, but pay particular attention to how the Avaya is going to accept the call. Make sure both sides of the link match and any necessary media resources are in place.
Troubleshooting these issues is going to be difficult since you have no physical gateway between the PBXs that you can run debugs on. I suppose if you really wanted to get down and dirty you could span one of the ports (Cisco or Avaya), run Wireshark, and see if you can pull out the H.323/H.225 call setup info.
Avaya has a proprietary message code or "feature" that needs to be turned on for caller ID to come across the trunk. And they charge for this. I forgot exactly what its called, but I know you have to pay for it and it has to be turned on. If you do not see it in the H323 logs at the router.. then they are not sending (they being avay)
Beside any technical matter, I would like to ask to the person that unfairly rated "3" two perfectly correct and helpful posts above, to avoid to do again in the future and to use better judgement when it comes to recognizing the free help received by professionals.
I also rated the posts above for what they are worth: 5 stars.
^Thank ya, sir.
To the original poster: Another option for information gathering would be to collect detailed traces from your CUCM cluster but detailed traces can be a beast to decode if you don't know what you're looking for. I don't mean to be snide but the Cisco UC Troubleshooting book is really helpful with detailed trace decodes.