[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference irocz::common_brouters

Title:Digital Brouters Conference
Notice:New common-code brouter family: RouteAbout, DECswitch 900
Moderator:MARVIN::HARTLL
Created:Mon Jul 17 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:929
Total number of notes:3736

807.0. "Cause-Codes" by MUNICH::WIESHEU () Wed Mar 19 1997 06:34

    Hello,
    
    I try to figure out the Cause-Codes of ELS-Messages. 
    eg.:
    ISDN.003: ConnID 0x0 Status msg cause (0x5:0x12) NLS Cause Indication
    on nt 2 int ISDN/0
    
    My HW/SW: 
    RtAbt Acces EI/MP,  Brouter: 1 Enet 1T1 1BRI,HW=1,RO=1,#403,SW=V2.0-2
    
    Does somebody know, where to find the description of these Case-Codes?
    
    
    Thanks for any help
    
       Johann
    
T.RTitleUserPersonal
Name
DateLines
807.1MARVIN::CLEVELANDThu Mar 20 1997 04:385
    They are in Q.931...in a future release, they'll be decoded by ELS and
    DTF.
    
    0x12 is 'no user responding'.
        
807.2Cause-Code: first HEX-DigitMUNICH::WIESHEUThu Mar 20 1997 10:389
    The same with the first HEX-Digit?
                               |
                               v
                       cause (0x5:0x12)
    
    Thanks
    
       Johann
    
807.3here's a guessMARVIN::RIGBYNo such thing as an alpha betaFri Mar 21 1997 04:2166
without checking I'd guess that the 5 is the location field and 0x12 the cause

,/*0*/"user"
,/*1*/"local private network"
,/*2*/"local public network"
,/*3*/"transit network"
,/*4*/"remote public network"
,/*5*/"remote private network"
,/*6*/Illegal
,/*7*/"international network"
,/*8*/Illegal
,/*9*/Illegal
,/*A*/"network beyond internetworking point"

,0x01,"Unallocated number"
,0x02,"No route to specified transmit network"
,0x03,"No route to destination"
,0x06,"Channel unacceptable"
,0x07,"Call awarded - dleivered in established channel"
,0x10,"Normal call clearing"
,0x11,"User busy"
,0x12,"No user responding"
,0x13,"No answer"
,0x15,"Call rejected"
,0x16,"Number changed"
,0x1A,"Non selected user clearing"
,0x1B,"Destination out of order"
,0x1C,"Invalid number format"
,0x1D,"Facility rejected"
,0x1E,"response to status enquiry"
,0x1F,"Unspecified"
,0x22,"No circuit available"
,0x26,"Network out of order"
,0x29,"Temporary failure"
,0x2A,"Switching equipment congestion"
,0x2B,"Access information discarded"
,0x2C,"Requested circuit unavailable"
,0x2F,"Unspecified"
,0x31,"QoS unavailable"
,0x32,"Facility not subscribed"
,0x39,"Bearer capability not authorized"
,0x3A,"Bearer capability not available"
,0x3F,"Unspecified"
,0x41,"Bearer capability not implemented"
,0x42,"Channel type not implemented"
,0x45,"Facility not implemented"
,0x46,"Only restricted digital available"
,0x4F,"Unspecified"
,0x51,"Invalid call reference"
,0x52,"Identified channel does not exist"
,0x53,"Suspended Call - invalid identity"
,0x54,"Call identity in use"
,0x55,"No call suspended"
,0x56,"Call already cleared"
,0x58,"Incompatible destination"
,0x5B,"Invalid transit network selection"
,0x5F,"Unspecified"
,0x60,"Mandatory ie missing"
,0x61,"Message type not implemented"
,0x62,"Message type not consistent"
,0x63,"ie not implemented"
,0x64,"ie contents invalid"
,0x65,"Message not compatible with state"
,0x66,"Recovery on timer expiry"
,0x6F,"Unspecified"
,0x7F,"Unspecified"
807.4MARVIN::CLEVELANDFri Mar 21 1997 06:536
    You've stumped me here...I think it might be an internal code, not
    relevant to any standard.  Anyway, the code treats 0x5 as 'NLS Cause
    Indication' -- in other words, it's already translated the 0x5 into
    text for you.  In a future release, you'll see the translations of the
    second byte as well (in other words, it will tell you that the 0x12
    means 'No user responding').