H.245 Messages

[JustForVoice_2]

Hi,

I am trying to understand some H.245 messages and how I can use it in troubleshooting. things goes smoothly if I need to read the details of the message. but the question is:

In H.245 messages, no guide (Call Identifier). How I can know that this message is related to that call if I have too many calls?

In H.225 messages guide is useful but I am not able to find it in H.245 messages.

Example:

value MultimediaSystemControlMessage ::= request : masterSlaveDetermination :
    {
      terminalType 60
      statusDeterminationNumber 9146
    }

[Chris Deren]

I suggest you check out the "Troubleshooting Cisco IP Telephony" book as it covers the messages in details:

http://books.google.com/books?id=YcCjKsssklIC&pg=PA297&lpg=PA297&dq=troubleshooting+h.245&source=bl&ots=ZX1-nnNLMv&sig=vlh_WsTNhGqqkI4BpdQ_FxuyWcA&hl=en&sa=X&ei=8V-iUM7eJMjNqgHDpoCwDA&ved=0CDkQ6AEwAg

HTH,

Chris

[Ayodeji Okanlawon]

+5 to Chris for recommeding that book. I have a copy of the book and its been my best IPT investment to date!!

Usuallualy to identify calls you need to use the guid to quickly trace each phase of the call..

Ex:

h225 call setup....

003317: *Jun  8 07:46:06.874 GMT: H225.0 INCOMING PDU ::=

value H323_UserInformation ::=
    {
      h323-uu-pdu
      {
        h323-message-body setup :
        {
          protocolIdentifier { 0 0 8 2250 0 4 }
          sourceAddress
          {
            h323-ID : {"MILHA_GK"}
          }
          sourceInfo
          {
            vendor
            {
              vendor
              {
                t35CountryCode 181
                t35Extension 0
                manufacturerCode 18
              }
              productId '436973636F47617465776179'H
              versionId '32'H
            }
            gateway
            {
              protocol
              {
                voice :
                {
                  supportedPrefixes
                  {
                  }
                },                h323 :
                {
                  supportedPrefixes
                  {
                  }
                }
              }
            }
            mc FALSE
            undefinedNode FALSE
          }
          activeMC FALSE
          conferenceID '00BFD9859FAE11FDDC0B67200A6928C8'H
          conferenceGoal create : NULL
          callType pointToPoint : NULL
          sourceCallSignalAddress ipAddress :
          {
            ip '0A6928D2'H
            port 59406
          }
          callIdentifier
          {
            guid '00BFD9859FAE11FDDC0B67200A6928C8'H

Next Call proceeding

value H323_UserInformation ::=
    {
      h323-uu-pdu
      {
        h323-message-body callProceeding :
        {
          protocolIdentifier { 0 0 8 2250 0 4 }
          destinationInfo
          {
            vendor
            {
              vendor
              {
                t35CountryCode 181
                t35Extension 0
                manufacturerCode 18
              }
              productId '436973636F47617465776179'H
              versionId '32'H
            }
            gateway
            {
              protocol
              {
                voice :
                {
                  supportedPrefixes
                  {

                    {
                      prefix dialedDigits : "1#"
                    }
                  }
                },                h323 :
                {
                  supportedPrefixes
                  {
                  }
                }
              }
            }
            mc FALSE
            undefinedNode FALSE
          }
          callIdentifier
          {
            guid '00BFD9859FAE11FDDC0B67200A6928C8'H
          }

NB: the guid will be the same for the same call. So you can look at the h225 setup and h245 capabilities negotiation of the call. This is very useful when looking at a long traces....

[JustForVoice_2]

Thank you for your reply.

+5 for both but sorry to say you did not help

it looks like I did not explain what I need properly.

I do NOT have problem with H.225 messages. ( The examples that aokanlawon added are for H.225 messages). My problem is with H.245 messages. NO GUIDE in H.245 messages.

I do NOT need any details about H.245 messages (btw, I have Cisco press: Troubleshooting Cisco IP Telephony, hard copy and softcopy).

I have mentioned in my question the following:

"In H.225 messages guide is useful but I am not able to find it in H.245 messages."

[JustForVoice_2]

No one from Cisco TAC??

[antyeung]

As far as I know there's no GUID or call ID you can use in an H.245 message. The closest thing you can get is filter based on port number of the H.245 message that's being tunneled on. In slow start the H.245 port will be in the H.225 message and then you can use that to associate what H.245 message is associated w/ the H.225 message exchange. It's been awhile since I looked at these debugs but there may be a debug that show's the port number of the message exchange right before an H.245 is sent or received. It's been awhile so you'll have to play around with the various H.245 debugs to see if there is one-

e.g.

debug h245 ?

debug cch323 ?

etc.

If there isn't you can maybe come up w/ an ACL or something of the like to print out the ip/port to the console for H.245 messages to give you a reference. Just a thought, which may/may not work.

Generally speaking, H.245 messages are horrible on IOS. The messages are so long and they are prone to skip debug lines on a busy gateway. The only times that I really found it useful was when I could collect debugs in a controlled manner when there were not a lot of calls. Either than that I would rather read the H.XXX traces from Callmanager, sniffers, or the other device it's communicating with. If I don't need H.245 messages then I usually get the H225 on the gateway, but even still those can be verbose.

[JustForVoice_2]

Thank you too much antyeunq. and +5

I will try to test and see.

Thanks.