cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1852
Views
20
Helpful
17
Replies

CM 4.1 and Avaya ip office H.323

      When I call from CM to Avaya call established but no voice in both destination are send.

I have no direct access to Avaya.

Can any explane from Cisco side can I determine remote destination ip in traces or other loggs?

remote destination is not Avaya H.323 gateway adress     ...

thank you all

17 Replies 17

Ayodeji Okanlawon
VIP Alumni
VIP Alumni

You need to understand how to read cucm traces. You also need to understanding H323-h225 and h245 negotiations to be able to know this...

If you attach the traces here I can help you analyze it. Please include the calling and called number and the time of call for the trace you attach

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts

hello!

        calling party 2888

called party 0621055

sniffer trace from CM 2888 registred

call established but now voice transmited

Thank you veru much!

Hi,

I have looked at the trace and the problem is that there is no H245 negotiation going on...

From the trace the avaya requested that all h245 signalling should be sent to this address

  10.37.17.10 on port  13758

h323-message-body connect :

      {

        protocolIdentifier { 0 0 8 2250 0 5 },

        h245Address ipAddress :

          {

            ip '0A25110A'H,

            port 13758

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared" 10

Please rate all useful posts

Thank you very much!

but can you explain what does it mean "Please rate all useful posts"???

What should I check? On CM or on network path?

Are You sure what it is a root problem? Call established succesfully. On ip phone display call timer started, but no voice transmited...

First of all...Please confirm that in yoru CUCM trace configuration you have detailed trace enabled..

Second..It could be network related issue because we cant see h245 negotiation in the cucm traces...It could also be that I cant see it because you have not enabled detailed traces..

lastly.."Please rate all useful posts" means that you should use the stars to rate answers that help you..

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts

detailed trace is enabled...

10.37.17.10 - is known address of avaya

but after call established no packets from this address recived  on ip phone...

Hi,

There  are certain things that need to happen before you can get audio. The IP  phone needs to know where to send its RTP stream to. This information  is provided by CUCM. CUCM gets this information from the h245  negotiation it performs with the avaya system. In your case there is no  H245 negotiation going on, hence there is no way for CUCM to know where  to tell the ip phone to send its media to.

Do you have a firewall between CUCM and the Avaya system?

Can you also confirm that H245 trace is enabled in your cucm trace settings...If it is not please enable it, do another test call and send me the cucm sdi traces

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts

Hello!

Thank you very much for description provided.

H245 was not enabled.

I have gatered new traces...

test call was from 2888 to 0621055 (only atempt) ip phone does not answered...

second test call was from 2888 to 0621013 IVR was answered... but no voice was transmitted...

Ayodeji Okanlawon
VIP Alumni
VIP Alumni

I have looked at the traces provided and I still cant see H245 negotiation between CUCM and Avaya. After the phone displays connected, the H245 negotiation should start and media flows shortly after that. The problem is that there is no H245 negotiation and CUCM sends a disconnect with cause code of 80AF wich means resource unavailable.

++++++

11/11/2013 09:17:57.512 CCM|Ie - Q931CauseIe IEData= 08 02 80 AF |<:STANDALONECLUSTER><:10.38.13.10>

The trace I have posted below is an example of a working call with H245 negotiation. You can see from where CUCM tells the phone to display status of "connencted"

++++Phone shows connected++++

11/11/2013 09:15:42.243 CCM|StationD:    (0000996) DisplayPromptStatus timeOut=0 Status='€ ' content='Connected' line=1 CI=50370219 ver=85720011.|<:STANDALONECLUSTER><:10.38.13.10><:3><:><:>

11/11/2013 09:15:42.243 CCM|StationD:    (0000996) (3,100,132,15869) CallInfo callingPartyName='Andreeva Olga Gennadevna' callingParty=0612717 cgpnVoiceMailbox=    calledPartyName='Sazonova IA' calledParty=61556 cdpnVoiceMailbox=    originalCalledPartyName='' originalCalledParty=61556 originalCdpnVoiceMailbox= originalCdpnRedirectReason=0    lastRedirectingPartyName='' lastRedirectingParty=61556 lastRedirectingVoiceMailbox= lastRedirectingReason=0    callType=2(OutBound) lineInstance=1 callReference=50370219. version: 85720011|<:STANDALONECLUSTER><:10.38.13.10><:3><:><:>

11/11/2013 09:15:42.243 CCM|StationD:    (0000996) StopTone.|<:STANDALONECLUSTER><:10.38.13.10><:3><:><:>

11/11/2013 09:15:42.243 CCM|StationD:    (0000996) DEBUG- star_DSetCallPhase updateACall=50370219 from Phase=0 to  callPhase=1.|<:STANDALONECLUSTER><:10.38.13.10><:3><:><:>

11/11/2013 09:15:42.243 CCM|StationD:    (0000996) DEBUG- star_DSetCallState(9) State of cdpc(25311) is 6.|<:STANDALONECLUSTER><:10.38.13.10><:3><:><:>

11/11/2013 09:15:42.243 CCM|StationD:    (0000996) (3,100,132,15869) CallInfo callingPartyName='Andreeva Olga Gennadevna' callingParty=0612717 cgpnVoiceMailbox=    calledPartyName='Sazonova IA' calledParty=61556 cdpnVoiceMailbox=    originalCalledPartyName='' originalCalledParty=61556 originalCdpnVoiceMailbox= originalCdpnRedirectReason=0    lastRedirectingPartyName='' lastRedirectingParty=61556 lastRedirectingVoiceMailbox= lastRedirectingReason=0    callType=2(OutBound) lineInstance=1 callReference=50370219. version: 85720011|<:STANDALONECLUSTER><:10.38.13.10><:0><:10.41.2.2><:>

++++Next thing is that CUCM initiates a H245 negotiation to the gateway++++

11/11/2013 09:15:42.275 CCM|H245ASN - TtPid=(3,100,144,8327) -Outgoing -value MultimediaSystemControlMessage ::= request : terminalCapabilitySet :

    {

      sequenceNumber 1,

      protocolIdentifier { 0 0 8 245 0 3 },

      multiplexCapability h2250Capability :

        {

          maximumAudioDelayJitter 60,

          receiveMultipointCapability

          {

            multicastCapability FALSE,

            multiUniCastConference FALSE,

            mediaDistributionCapability

            {

              {

                centralizedControl FALSE,

                distributedControl FALSE,

                centralizedAudio FALSE,

                distributedAudio FALSE,

                centralizedVideo FALSE,

                distributedVideo FALSE

              }

            }

          },

          transmitMultipointCapability

          {

            multicastCapability FALSE,

            multiUniCastConference FALSE,

            mediaDistributionCapability

            {

              {

                centralizedControl FALSE,

                distributedControl FALSE,

                centralizedAudio FALSE,

                distributedAudio FALSE,

                centralizedVideo FALSE,

                distributedVideo FALSE

              }

            }

          },

          receiveAndTransmitMultipointCapability

          {

            multicastCapability FALSE,

            multiUniCastConference FALSE,

            mediaDistributionCapability

            {

              {

                centralizedControl FALSE,

                distributedControl FALSE,

                centralizedAudio FALSE,

                distributedAudio FALSE,

                centralizedVideo FALSE,

                distributedVideo FALSE

              }

            }

          },

          mcCapability

          {

            centralizedConferenceMC FALSE,

            decentralizedConferenceMC FALSE

          },

          rtcpVideoControlCapability FALSE,

          mediaPacketizationCapability

          {

            h261aVideoPacketization FALSE

          },

          logicalChannelSwitchingCapability FALSE,

          t120DynamicPortCapability FALSE

        },

      capabilityTable

      {

        {

          capabilityTableEntryNumber 1,

          capability nonStandard :

            {

              nonStandardIdentifier h221NonStandard :

                {

                  t35CountryCode 181,

                  t35Extension 0,

                  manufacturerCode 18

                },

              data '010000000A000000100019043C8ACF08'H

            }

        },

        {

          capabilityTableEntryNumber 2,

          capability receiveAudioCapability : g729wAnnexB : 6

        },

        {

          capabilityTableEntryNumber 3,

          capability receiveAudioCapability : g729AnnexAwAnnexB : 6

        },

        {

          capabilityTableEntryNumber 4,

          capability receiveAudioCapability : g729 : 6

        },

        {

          capabilityTableEntryNumber 5,

          capability receiveAudioCapability : g729AnnexA : 6

        },

        {

          capabilityTableEntryNumber 44,

          capability receiveAndTransmitUserInputCapability : hookflash : NULL

The most likely reason this is happening is that CUCM is unable to establish TCP connection to the port that is required for H245 negotiation.  Do you have a firewall between the Avaya and CUCM? If you do then you need to ensure that the TCP ports required for H245 negotiation are allowed on the firewall between CUCM and Avaya

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts

>The most likely reason this is happening is that CUCM is unable  to  establish TCP connection to the port that is required for H245   negotiation.  Do you have a firewall between the Avaya and CUCM?

I am not sure about full traffic path... I will investigate this...

Thank you very much...

I will back soon...

I have inspected succsesfully working configuration with CM 7.1

And I detected what when call established - Transcoding resourse is used...

I don't understand why it used... but it's fact....

67326910   73821040     xcode sendrecv g729a   21134 49152 10.37.17.10         

67326910   73821037     xcode sendrecv g711u   18724 21968 10.38.3.143      

end point supported 729a codec...

I will check on my configuration - reachibility trancoder bridge from remote office...

This is not a xcoding issue. Before CUCM knows what codecs will be involved in a call..CUCM need to exchange "Terminal capabilities set (TCS)" with the gateway. TCS is part of the H245 negotiation. The call that you saw working had H245 negotiation. You need to investigate why there is no H245 negotiation

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts

Hello!

The issue is not resolved yet...

But I have some additional info.

Test call from avaya to Cm is successfull...

I attached trace for this call

can you determy any usable info?

Thank you very much!

Chernyakov,

Yes the trace is very useful and I can see the H245 negotiation now. What did you do for this to start working? Do you still have any issues...Calls from Avaya to CUCM is succesfull, what about calls from cucm to Avaya? Is that not working..If it is not then you need to do a test call and send me the traces

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts