[cisco-voip] Display IE & CCM

[Andre Beck]

Re,

On Mon, Jan 09, 2006 at 04:45:52PM +0100, Andre Beck wrote:
> On Sat, Jan 07, 2006 at 05:07:05PM -0500, Wes Sisk wrote:
> 
> > Can you send me a complete CCM trace?
> 
> I'll have to figure out how to do this first ;)

Meanwhile I did, so here is the view from the other side:

1) A look at a NOTIFY Message bearing AOCD and an empty Display IE:

   In  Message -- H225NotifyMsg -- Protocol= H225Protocol
   Ie - Q931NotificationIndicatorIe -- IEData= 27 01 F1 
   Ie - Q931DisplayIe -- IEData= 28 00 
   Ie - Q931ConnectedNumIe -- IEData= 4C 0A 00 00 30 34 37 31 36 34 36 36 
   Ie - H225UserUserIe -- IEData= 7E 00 21 05 28 50 19 00 06 00 08 91 4A 00 04 00 80 E6 E7 68 2B 9F B1 1D 66 01 00 00 C0 A8 6F 1F 10 80 01 00 
   MMan_Id= 0. (iep=  0 dsl=  0 sapi=  0 ces= 0 IpAddr=fe6fa8c0 IpPort=1720)
   IsdnMsgData1= 08 02 81 66 6E 27 01 F1 28 00 4C 0A 00 00 30 34 37 31 36 34 36 36 7E 00 21 05 28 50 19 00 06 00 08 91 4A 00 04 00 80 E6 E7 68 2B 9F B1 1D 66 01 00 00 C0 A8 6F 1F 10 80 01 00 
   H225Cdpc::updateDisplayNameFromQ931DisplayIE(939, 16781532): INFO: fQ931Display=, fDisplayName=|<CLID::PHONY-Cluster><NID::phony><CT::0,0,0,0.0><IP::192.168.111.254><DEV::>
   H225Cdpc::updateDisplayNameFromQ931DisplayIE(939, 16781532): INFO: fQ931Display=, fDisplayName=|<CLID::PHONY-Cluster><NID::phony><CT::0,0,0,0.0><IP::192.168.111.254><DEV::>

   That one is actually looking quite promising, as it receives a Display IE
   and seems to invoke something called updateDisplayNameFromQ931DisplayIE,
   which might be what I want. Or not, if it hoses the original caller
   name ;)

2) A look at the transcribed INFORMATION message which should have a
   Display IE, but hasn't:

   In  Message -- H225InfoMsg -- Protocol= H225Protocol
   Ie - Q931CalledPartyIe -- IEData= 70 01 91 
   Ie - H225UserUserIe -- IEData= 7E 00 3E 05 24 80 06 00 08 91 4A 00 04 0B 00 11 00 80 E6 E7 68 2B 9F B1 1D 66 01 00 00 C0 A8 6F 1F 10 A0 01 00 1B 01 40 B5 00 00 12 14 60 01 01 00 01 28 0D 28 0B 31 20 45 69 6E 68 65 69 74 65 6E 
   MMan_Id= 0. (iep=  0 dsl=  0 sapi=  0 ces= 0 IpAddr=fe6fa8c0 IpPort=1720)
   IsdnMsgData1= 08 02 81 66 7B 70 01 91 7E 00 3E 05 24 80 06 00 08 91 4A 00 04 0B 00 11 00 80 E6 E7 68 2B 9F B1 1D 66 01 00 00 C0 A8 6F 1F 10 A0 01 00 1B 01 40 B5 00 00 12 14 60 01 01 00 01 28 0D 28 0B 31 20 45 69 6E 68 65 69 74 65 6E 
   value H323-UserInformation ::= 
   {
     h323-uu-pdu 
     {
       h323-message-body information : 
         {
           protocolIdentifier { 0 0 8 2250 0 4 },
           callIdentifier 
           {
             guid '80E6E7682B9FB11D66010000C0A86F1F'H
           }
         },
       h245Tunneling FALSE,
       nonStandardControl 
       {
         {
           nonStandardIdentifier h221NonStandard : 
             {
               t35CountryCode 181,
               t35Extension 0,
               manufacturerCode 18
             },
           data '6001010001280D280B312045696E68656974656E'H
         }
       }
     }
   }

   And that's it. This message doesn't trigger any further interpretation
   of the UU content it seems, especially not some digging out and turning
   back into a Display IE of the last Bytes from that data part.

So IMO the first thing that goes wrong is the translation from I.430/Q.931
to H.225/Q.931 by the Cisco IOS gateway.

Andre.
-- 
                  The _S_anta _C_laus _O_peration
  or "how to turn a complete illusion into a neverending money source"

-> Andre Beck    +++ ABP-RIPE +++    IBH Prof. Dr. Horn GmbH, Dresden <-