3301 Protocol Error Layer 1
Contents |
CAPI_REGISTERMessage exchange errorsResource/Coding ErrorsErrors concerning requested servicesThe CAPI interface used here has its own coding of standard ISDN error codes. Most of the errors described in the section called “Internal CAPI errors” are only important for developers
0x3301 Protocol Error Layer 1
of the CapiSuite core. As user, you only need to know protocol error layer 2 the codes shown in the section called “CAPI errors describing connection problems” as they'll be used in the
Protocol Error Layer 3
CapiSuite Python functions like capisuite.disconnect.You'll find a list of all the codes and a short description below. A detailled description of the CAPI codes can be found in the CAPI specification available at http://www.capi.org.All numbers are given hexadecimal!CAPI errors describing connection problemsAll errors described here indicate some problem with the connection. These errors are also important for script writers as they're returned by some CapiSuite Python functions. See the section called “CapiSuite command reference” for further details.Protocol errorsProtocol errors indicate some problem during data transfer. Only messages for the transparent (voice) and fax protocols spoken by CapiSuite are shown here.0 - Normal call clearing, no error3301 - Protocol error layer 1 (broken line or B-channel removed by signalling protocol)3302 - Protocol error layer 23303 - Protocol error layer 33304 - Another application got that call3311 - T.30 (fax) error: Connection not successful (remote station is not a G3 fax device)3312 - T.30 (fax) error: Connection not successful (training error)3313 - T.30 (fax) error: Disconnect before transfer (remote station doesn't support transfer mode, e.g. wrong resolution)3314 - T.30 (fax) error: Disconnect during transfer (remote abort)3315 - T.30 (fax) error: Disconnect during transfer (remote procedure error)3316 - T.30 (fax) error: Disconnect during transfer (local transmit data underflow)3317 - T.30 (fax) error: Disconnect during transfer (local receive data overflow)3318 - T.30 (fax) error: Disconnect during transfer (local abort)3319 - T.30 (fax) error: Illegal parameter coding (e.g. defective SFF file)ISDN error codesThese codes are ISDN error codes which are described by the ETS 300 102-01 standard in more detail. It's currently avai
from GoogleSign inHidden fieldsSearch for groups or messages
Next message: [Asterisk-Users] Fritz Card ISDN in UK - Unable to dial. 0x3301/0x3302 errors Messages sorted by: [ http://lists.digium.com/pipermail/asterisk-users/2005-April/092683.html date ] [ thread ] [ subject ] [ author ] On Wed, 2005-04-06 at 10:58 +0100, Paul Redstone wrote: > I'm having major problems getting a Fritz card to dial out in the UK (or indeed > answer, but I've been concentrating on dialing out). I'm getting the 0x3301 or > 0x3302 error. protocol error > ---------------------- > The 0x3301 and 3302 errors seem to be protocol ones and it 'feels' like some > sort of country configuration issue or something like that. Can any one give me > any advice/help on this as I'm been stuck on this for a week. > Many thanks > According to my protocol error layer list +/*-- information about the clearing of a physical connection -----*/ + case 0x3301: + return "Protocol error layer 1 (broken line or B-channel removed by signalling protocol)"; + case 0x3302: + return "Protocol error layer 2"; + case 0x3303: + return "Protocol error layer 3"; + case 0x3304: + return "Another application got that call"; I remember getting these messages once. If I remember I just removed the cables from the telco box, waited while I had a coffee, and put them back in. Do you need the full MSN in the UK? Here in France I use just the last 4 digits. -- Dave Cotton