3301

Protocol error level 1

The connection between the ISDN Unit/Router and the ISDN network is broken. Check the connection. The error may have its cause somewhere between your own ISDN hardware and the "target hardware". Even a defect in a distribution box can be the cause, although this should only be the reason in the very rarest of cases.

3302

Protocol error level 2

Error during communication in the D channel. The set D-channel protocol is incompatible with the connection. Possibly the connection is disturbed. This may be due to incorrect termination or another device.

3303

Protocol error level 3

The protocol used in the B channel does not match the protocol of the remote end. On the remote side, a device or software accepts the data call that is not compatible with the Odette standards. This can be another data transfer software (e.g. Fritz!Data) or a remote maintenance access. In very rare cases, the PBX of the other party tries to accept the call if the device on the called number cannot be reached.

3481

Unknown number

The dialled number or the own call number is unknown to the exchange or the own PABX.

During online registration: Check the call number entered in the "ISDN number Odette" field. PBXs often expect only the internal extension number here. The number should be available on the internal S0 bus.

In !MC5: Check the phone number entered for the partner. If no partner can be reached, the connection or settings in the PBX have been changed.

3482

No connection to the specified network

3483

No connection to the remote terminal

Check the phone number entered

3486

Channel not acceptable

3487

Call accepted and forwarded to existing connection

3490

Normal disconnection

This error code means that one of the participants has initiated the disconnection, i.e. has "hung up". If error 3490 is displayed in !MC5, this means that the connection was disconnected in a situation where it was not expected from the OFTP protocol.

Probably the most common cause for this is that the partner is using OFTP software that does not follow the OFTP protocol correctly: Connection and data transfer run successfully, but when the connection is terminated, the other party hangs up early. In this case, error 3490 is not a critical error, just an "inconvenience". Nevertheless, !MC5 will always report it as an error, since the software cannot know the actual cause of the error. In the case of the non-compliant OFTP software, only a software update or a software change on the other side would help.

3491

Participants occupied

This error corresponds to the busy signal on the telephone, i.e. all lines are busy on the other end. As long as the line is busy, !MC5 will try to dial again every three minutes.

3492

Participant does not answer.

In this case, a dial tone would be heard on the telephone, but no one answers. There could be various reasons for this: The OFTP software on the other side might not be running or a wrong number has been entered in the partner data which exists but where no OFTP software picks up. It could also be that the far end is already busy on another line. As long as the far end does not respond, !MC5 will try to redial every three minutes.

3493

Participant does not answer (but has signalled).

3495

Call rejected

3496

Number has changed

349A

Call was answered by another device

Incoming connections only.

Make sure that no other device or software providing ISDN data services is configured to the same number as !MC5.

349B

Remote terminal defective

349C

Number has invalid format

Check the entered phone number of the partner.

349D

Transmission property rejected

349E

Response to status request

349F

No ISDN connection, reason unknown

34A2

No channel available

An active connection attempt cannot be made because there is no free line on the local port. The connection setup will probably be successful at a later time.

34A6

Network defective

The own PBX or the exchange reports a defect.

34A9

Temporary error

The own PBX or the exchange reports a short-term defect, which will probably be repaired in the short term.

34AA

Overload of the switching equipment

Doesn't really happen anymore.

34AB

Access data rejected

34AC

Requested channel not available

34AF

Resources not available, no further details

34B1

Service not available

34B2

Requested service feature not available

34B9

Transmission property not permitted

34BA

Transmission property temporarily unavailable

34BF

Service or option not available, not specified

34C1

Transmission property not implemented

34C2

Channel type not implemented

34C5

Requested property not implemented

34C6

Only transmission property available for limited digital information

34CF

Service or option not implemented

34D1

Invalid value of the connection identifier

34D2

Specified channel does not exist

34D3

An interrupted call exists, but the specified call identifier does not.

34D4

Call identity in use

34D5

No call ended

34D6

Call with the specified identifier was reset

34D8

Remote terminal not compatible

Is output by some PABXs if no device for digital transmission can be reached under the dialled call number, i.e. if necessary even if all channels are occupied on the other side. You will also receive this error message if you enter an analogue connection as the call number.

34DB

Invalid selection of the transmission network

34DF

Invalid message, no further details

34E0

Required message element does not exist

34E1

Message type does not exist or is not implemented

34E2

Message type is incompatible with call status or message type does not exist

34E3

Message element does not exist or is not implemented

34E4

Invalid content in the message element

34E5

Message type incompatible with call status

34E6

Termination after time-out

34EF

Protocol error, not specified

34FF

Network usage, not specified