cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
488
Views
0
Helpful
7
Replies
Highlighted

Fail Call to Avaya phone

Hi Gents,

I have an legacy Avaya PBX that requires to works with CUCM. Based on Avaya documentation that I found which based on CM v4, I create a trunk using H323 by creating H323 GW with Avaya IP address. On on the Avaya sides, AGC networks guy has configured on his portion accordingly.

So, from Avaya phone can now call to Cisco phone by dialing full DN (eg: 91011234), however from Cisco phone unable to call Avaya DN (eg: 2345). The avaya dude insists that he could not see any sort of incoming signal from Cisco to his device. However, I could verify my call flow is works by using DNA in CUCM.

Below is the call traces I captured from rtmt. Anyone can shed something here?

Good Call (Inbound Avaya to Cisco)
 
Inbound H225 SETUP message from 10.242.75.52 at timestamp 01/12/2016 08:19:30.062
 
SETUP, pd = 8, callref = 0x0041, Message Size = 221 bytes
 
Sending Complete
Bearer Capability i = 0x9090A3, ITU-T standard, 3.1kHz audio, Circuit mode, 64k, A-law
Called Party Number i = '91013177' - Plan: ISDN, Type: National
User-User, i = 0x052090060008914A00053CC0B5004C54114176617961204D756C746976616E746167650F52303136782E30322E302E3832332E301003140504010000C02C0504010000C03C0504010000C020010380C43464AA00807CB59206C1E501030056A4C652000000D51D800007000AF24B3406B81100807CB59206C1E501030056A4C65200003402130000640C6013800B0F0001000AF24B360803001E400064060401004C60138012150001000AF24B360802000AF24B36080300010001800100010010800180
 
UUIE ASN.1 Decode:
 
SPROCRas - {
 
  h323-uu-pdu
  {
    h323-message-body setup :
      {
        protocolIdentifier { 0 0 8 2250 0 5 },
        sourceInfo
        {
          vendor
          {
            vendor
            {
              t35CountryCode 181,
              t35Extension 0,
              manufacturerCode 19540
            },
            productId '4176617961204D756C746976616E746167 ...'H,
            versionId '52303136782E30322E302E3832332E30'H
          },
          gatekeeper
          {
          },
          gateway
          {
            protocol
            {
              h320 :
                {
                  supportedPrefixes
                  {
                    {
                      prefix dialedDigits : "9"
                    }
                  }
                },
              h323 :
                {
                  supportedPrefixes
                  {
                    {
                      prefix dialedDigits : "9"
                    }
                  }
                },SPROCRas -
              voice :
                {
                  supportedPrefixes
                  {
                    {
                      prefix dialedDigits : "9"
                    }
                  }
                }
            }
          },
          mcu
          {
          },
          mc TRUE,
          undefinedNode FALSE
        },
        destinationAddress
        {
          dialedDigits : "91013177"
        },
        activeMC FALSE,
        conferenceID '807CB59206C1E501030056A4C6520000'H,
        conferenceGoal create : NULL,
        callType pointToPoint : NULL,
        sourceCallSignalAddress ipAddress :
          {
            ip '0AF24B34'H,
            port 1720
          },
        callIdentifier
        {
          guid '807CB59206C1E501030056A4C6520000'H
        },
        fastStart
        {
          '0000640C6013800B0F0001000AF24B3608 ...'H,
          '400064060401004C60138012150001000A ...'H
        },
        mediaWaitForConnect FALSE,
        canOverlapSend TRUE,
        multipleCalls FALSE,
        maintainConnection FALSE
      },
    h245Tunneling TRUE
  }
}
 
Entire Message:
010:  08 02 00 41 05 A1 04 03 90 90 A3 70 09 A1 39 31
020:  30 31 33 31 37 37 7E 00 C4 05 20 90 06 00 08 91
030:  4A 00 05 3C C0 B5 00 4C 54 11 41 76 61 79 61 20
040:  4D 75 6C 74 69 76 61 6E 74 61 67 65 0F 52 30 31
050:  36 78 2E 30 32 2E 30 2E 38 32 33 2E 30 10 03 14
060:  05 04 01 00 00 C0 2C 05 04 01 00 00 C0 3C 05 04
070:  01 00 00 C0 20 01 03 80 C4 34 64 AA 00 80 7C B5
080:  92 06 C1 E5 01 03 00 56 A4 C6 52 00 00 00 D5 1D
090:  80 00 07 00 0A F2 4B 34 06 B8 11 00 80 7C B5 92
0A0:  06 C1 E5 01 03 00 56 A4 C6 52 00 00 34 02 13 00
0B0:  00 64 0C 60 13 80 0B 0F 00 01 00 0A F2 4B 36 08
0C0:  03 00 1E 40 00 64 06 04 01 00 4C 60 13 80 12 15
0D0:  00 01 00 0A F2 4B 36 08 02 00 0A F2 4B 36 08 03
0E0:  00 01 00 01 80 01 00 01 00 10 80 01 80
 
Source Filename: ccm00000083.txt
 
 
Bad Call (Outbound Cisco to Avaya)
 
 
Outbound H225 NOTIFY message to 10.242.75.52 at timestamp 01/12/2016 08:19:30.067
 
NOTIFY, pd = 8, callref = 0x8041, Message Size = 56 bytes
 
Notification Indicator i = 0xF1 - Reserved
Connected Number i = '91013177' - Plan: Unknown, Type: National, Presentation Allowed, User-provided, verified and passed
User-User, i = 0x0528501900060008914A000500807CB59206C1E501030056A4C652000010800100
 
UUIE ASN.1 Decode:
 
{
 
  h323-uu-pdu
  {
    h323-message-body notify :
      {
        protocolIdentifier { 0 0 8 2250 0 5 },
        callIdentifier
        {
          guid '807CB59206C1E501030056A4C6520000'H
        }
      },
    h245Tunneling FALSE
  }
}
 
Entire Message:
010:  08 02 80 41 6E 27 01 F1 4C 0A 20 81 39 31 30 31
020:  33 31 37 37 7E 00 21 05 28 50 19 00 06 00 08 91
030:  4A 00 05 00 80 7C B5 92 06 C1 E5 01 03 00 56 A4
040:  C6 52 00 00 10 80 01 00
 
Source Filename: ccm00000083.txt
Regards,
Hidzwan
 
7 REPLIES 7
Highlighted
Cisco Employee

Hi Hidzwan,

Please provide the complete trace file or at least all messages filtered with the guid '807CB59206C1E501030056A4C6520000'H

Manish

Highlighted

Hi Manish,

Is this what you're looking for?

Regards,

Hidzwan

Highlighted

This one looks to be for the good call as it shows the call connecting and a normal call clearing message.

Manish

Highlighted

Does it means on the configuration is fine on CUCM side? Until now I'm still getting busy dial tone when dialing the Avaya extension number. Do u suggest to ask Avaya vendor to check on their end?

Highlighted

If we see the Setup message being sent out from cucm towards Avaya system then Avaya needs to confirm if they are receiving it or not. If the setup message is lost somewhere between cucm and Avaya then the underlying gateways / switches need to be checked as per the topology.

Manish

Highlighted

That's the weird part as we don't have anything sits in between CUCM and the Avaya server.

The Avaya CM itself does the GW function from the CUCM perspective, however they claimed that they don't see the call signal from their console.

avy phone -- avy CM ------H323 ------- CUCM ------ ip phone

-----------------------------------------> OK

<---------------------------------------- BUSY TONE

Highlighted

If we see the setup message going out from cucm then it should ideally reach Avaya with your setup. Try resetting the h323 gateway on cucm to see if that helps. It would be good if you can get on call with Avaya and ask them to collect the traces in real time and show that the call setup has not reached Avaya system.

Manish