asterisk users - Mar 2005 - capi debugging

Hi,
  Regarding capi debug, I don't know how to translate reasons like 0x3302 or
infos like 0. I didn't find any 'translator' googleing capi
debugging. Do you know about any 'translator' for this or should I be as
clever as to know what a reason 0x3302 is?

  What is this debug for if I can't interpret it?

Kind regards,
  Victor.
>From capi debug:
  == CAPI Call CAPI[contr1/number]/1     -- creating pipe for PLCI=-1
       > sent CONNECT_REQ MN =0x5
    -- CONNECT_CONF ID=002 #0x0005 LEN=0014
  Controller/PLCI/NCCI            = 0x101
  Info                            = 0x0

    -- CONNECT_CONF ID=002 #0x0005 LEN=0014
  Controller/PLCI/NCCI            = 0x101
  Info                            = 0x0

  == received CONNECT_CONF PLCI = 0x101 INFO = 0
    -- Called @number:number
    -- DISCONNECT_IND ID=002 #0x0009 LEN=0014
  Controller/PLCI/NCCI            = 0x101
  Reason                          = 0x3302
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20050303/23c7dc60/attachment.htm

I'm going to answer myself. I don't know If somebody already did it
because I'm using digest mode.

CAPI specification is available at http://www.capi.org/, It explains all the
commands and associated identifiers. Now I know that reason 0x3302 in
DISCONNECT_IND means Protocol error, Layer 2. I'll carry on with my
researching from here.

 I don't know what is the point of use messages like 0x3302 instead of speak
a human language but I've found my 'translator'.

 Victor.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20050303/fc837d9e/attachment.htm