CM 4.1 and Avaya ip office H.323 trace...

[Mikhail Chernyakov]

Can any comment whay H.323 connection not establish?

CM 10.38.4.10 calling part (061) 2088

called (062)1055

h 323 gat 10.37.17.10

Thank you very much!

[Manish Gogna]

Hi,

The call is failing with the following

Cause i = 0x80E6 - Recovery on timer expiry

Basically there is no response to the initial outbound h225 setup message sent from cucm to Avaya.

This will require a check of the configuration on Avaya side to see if they are recieving the setup and why is there no response to it.

HTH

Manish

[Mikhail Chernyakov]

I am some confused... in what file what string was found?

Can you provide exact string?

Thank you very much!

[Manish Gogna · Accepted solution]

I used a tool to filter h225 messages.

You can see the following in trace file

10/01/2013 14:16:04.368 CCM|Out Message -- H225ReleaseCompleteMsg -- Protocol= H225Protocol|<:STANDALONECLUSTER><:10.38.4.10>

10/01/2013 14:16:04.368 CCM|Ie - Q931CauseIe IEData= 08 02 80 E6 |<:STANDALONECLUSTER><:10.38.4.10>

The h323 call can be tracked by its unique guid value, which in this case is

809B7A748548411E22007B020A2D1C99

HTH

Manish

[Mikhail Chernyakov]

Thank you very much!

We will check Avaya configuration...