Le site web de Pierre Damien GATOUILLAT

Après avoir chercher partout comment ajouter une route statique sur une Livebox Pro Inventel (firmware > 5.x), j'ai trouvé ça : http://jean.thecoderblogs.com/2008/12/05/got-root/

Utilisateurs avertis seulement ! A vos risques et périls

En installant un serveur ssh (dropbear) sur la Box, en autorisant le ssh au niveau du firewall dans l'interface web pour une IP du réseau local, on peut se connecter dessus, on se retrouve sur un bon vieux Linux (mais assez récent, kernel 2.6.x) et on peut donc faire un ip route add network/mask via gateway. Ajouter cette commande à la fin de /etc/bluedsl.conf pour que la route soit active au démarrage et voilà!

Du coup on peut également voir toutes les pages html cachées, dans /webs

Penser évidemment à changer le mot de passe root par défaut.

Aussi à nettoyer le fichier bluedsl.conf

C'est quand même dingue qu'on ne puisse pas à travers l'interface web faire ce genre de chose, c'est la base du réseau. Bon vous me direz, 99% des gens ayant une livebox n'ont pas d'autres réseaux à router que le local... mais moi je faisais parti des 1%... et j'ai maudis Orange et ses Livebox de m...

Le package ipcalc/linux/debian contient un calculateur IP en ligne de commande et aussi un script cgi, c'est donc bien pratique pour calculer les subnet mask, etc. ça se trouve ICI (j'ai adapté un peu le script pour les images, liens, etc.)

CODE ERREURS RNIS 1

CODE ERREURS RNIS 2

ISDN ERROR CODE CAUSE VALUES
This table describes ISDN standard cause values that may be displayed on your video conferencing system to indicate ISDN call or line errors.
Value Cause Description
Definition
1 Unassigned
number
The switch received the sent ISDN number in the correct format; however, no destination equipment
uses the number.
2
No route to specified transit network The ISDN exchange can not recognize the intermediate network through which to route the call.
3
No route to destination
The intermediate network through which the call is routed does not service the destination address.
6
Channel unacceptable
The specified channel does not provide sufficient service quality to accept the requested connection.
7
Call awarded and delivered
The user is assigned an incoming call that is being connected to an already-established call channel.
16
Normal call clearing
Normal call clearing has occurred.
17 User
busy
All B channels are in use; the called system acknowledges the connection request, but is unable to
accept the call.
18
No user responding
The destination does not respond to the call so the connection cannot be completed.
19
No answer from user (user alerted)
The destination fails to complete the connection within the prescribed time after responding to the
connection request. The problem occurs at the remote end of the connection.
21
Call rejected
The destination rejects the call for an unknown reason, although capable of accepting the call.
22 Number
changed
No system has been assigned the ISDN number used to set up the call. (The diagnostic field of the
message may return an alternate address is assigned to the called equipment.)
26
Non-selected user clearing
The destination rejected the call, although capable of accepting it, because the call was not assigned
to the user.
27
Destination out of order
A signalling message can not be delivered because the interface is not functioning correctly, and
therefore the destination can not be reached. This condition might be temporary, though of extended
duration; for instance, remote equipment might be turned off.
28
Invalid number format
Destination address presented in an unrecognisable format or an incomplete destination address
made the connection unable to be established.
29
Facility rejected
The network can not provide facility requested by the user.
30
Response to STATUS ENQUIRY
The prior receipt of a status inquiry message generated the status message.
31
Normal, unspecified
A normal event has occurred with no standard cause applying. No resulting action is required.
34
No circuit/channel available
The call cannot be taken because no appropriate channel is available to establish the connection.
38
Network out of order
The network is not functioning correctly and this condition may persist for an extended period. The
call cannot reach the destination and an immediate attempt to reconnect will probably fail.
41
Temporary failure
The network is not functioning correctly and an error occurred. The problem will be resolved shortly.
42
Switching equipment congestion
The network switching equipment is temporarily overloaded and the destination cannot be reached.
43
Access information discarded
The requested access information cannot be provided by the network.
44
Requested circuit/channel not
An unknown reason prevents the remote equipment from providing the requested channel. This
available
might be a temporary problem.
47
Resource unavailable, unspecified
An unknown reason prevents the remote equipment from providing the requested channel. This
might be a temporary problem.
49
Quality of service unavailable
The network can not provide the requested quality of service (as defined by CCITT recommendation
X.213). This might be a subscription problem.
50
Requested facility not subscribed
The remote equipment supports the requested supplementary service, but only by subscription.
57
Bearer capability not authorized
The caller has requested a bearer capability that the network can provide, but the user is not
authorized to use. This might be a subscription problem.
58
Bearer capability not presently
The network normally provides the requested bearer capability, but not at the present time. This
available
might be due to a temporary network problem or to a subscription problem.
Zylotech Ltd ­ Sydney PH 02 9428 8988, Melbourne. PH 03 9535 6847 - www.zylotech.com.au - ABN 15 008 720 223

---

63
Service or option not available,
An unspecified reason prevents the network or remote equipment from providing the requested
unspecified
service option. This might be a subscription problem.
65
Bearer capability not implemented
The network cannot provide the bearer capability requested by the user.
66
Channel type not implemented
The requested channel type is not supported by the network or the destination equipment.
69
Requested facility not implemented
The supplementary service is not supported by remote equipment.
70
Only restricted digital information
The network is unable to provide unrestricted digital information over bearer capability.
bearer is available
79
Service or option not available,
The network or remote equipment is unable to provided the requested service option for an
unspecified
unspecified reason. This might be a subscription problem.
81
Invalid call reference value
The remote equipment received a call with a call reference that is not currently in use on the user-
network interface.
82
Identified channel does not exist
The receiving equipment is requested to use a channel that is not activated on the interface for calls.
83
A suspended call exists but this call
The network received a call resume request. The call resume request contained a call identify
identity does not
information element that indicates that the call identity is in use for a suspended call.
84
Call identity in use
The network received a call resume request that contained a Call Identify information element that
indicates that it is in use for a suspended call.
85
No call suspended
The network received a call resume request when there was not a suspended call pending. This
might be a transient error that will be resolved by successive call retries.
86
Call having requested call identity has The network received a call resume request. The call resume request contained a call identity
been cleared
information element, which once indicated a suspended call. How ever, the suspended call was
cleared either by timeout or by the remote user.
88
Incompatible destination
Indicates that an attempt was made to connect to non-ISDN equipment. (ie: to an analogue line.)
91
Invalid transit network specified
The ISDN exchange was asked to route the call through an unrecognised intermediate network.
95
Invalid message, unspecified
An invalid message was received, and no standard cause applies. This is usually due to a D-channel
error. If this error occurs systematically, report it to your ISDN service provider.
96
Mandatory information element is
The receiving equipment received a message that did not include one of the mandatory information
missing
elements. This is usually due to a D-channel error. If this error occurs systematically, report it to your
ISDN service provider.
97
Message type nonexistent or not
The receiving equipment received an unrecognised message, either because the message type was
implemented
invalid or because the message type was valid but not supported. Cause 97 is due to either a
problem with the remote configuration or a problem with the local D channel.
98
Message incompatible with call state The remote equipment received an invalid message, and no standard cause applies. Cause 98 is
or message type nonexistent.
usually due to a D-channel error. If this error occurs systematically, report it to your ISDN service
provider.
99
Information element nonexistent or not The remote equipment received a message that includes information elements, which were not
implemented
recognized. This is usually due to a D-channel error. If this error occurs systematically, report it to
your ISDN service provider.
100 Invalid information element contents The remote equipment received a message that includes invalid information in the information
element. This is usually due to a D-channel error.
101 Message not compatible with call state The remote equipment received an unexpected message that does not correspond to the current
state of the connection. This is usually due to a D-channel error.
102 Recovery on timer expiry
A timer expiry initiated an error-handling (recovery) procedure. This problem is typically temporary.
111 Protocol error, unspecified
An unspecified D-channel error when no other standard cause applies.
127 Interworking,
unspecified
An event occurred, but the network does not provide causes for the action that it takes. The precise
problem is unknown.
145 ISDN layer 1 and/or 2 link not
User needs to check cabling, ISDN adapter status and network connections.
established.
146 ISDN layer 3 connection to the ISDN A switch protocol error exists, or (in the United States or Canada) a SPID assignment problem.
switch/network inactive.
There is either a switch protocol error, or (in the United States or Canada) a SPID assignment
problem.
255 ISDN command processing error.
The ISDN signalling code has encountered an error processing an ISDN action. ISDN adapter busy-
wait and retry.

Zylotech Ltd ­ Sydney PH 02 9428 8988, Melbourne. PH 03 9535 6847 - www.zylotech.com.au - ABN 15 008 720 223

---

Technical Notes: Selected Cause Codes for ISDN Routers
Page 1 of 4
NIR_044: Selected Cause Codes for Netopia ISDN routers
Written by: David James
Date: 04/10/98
Revised: 07/07/98
What selected cause codes mean and how to resolve them.
Problem:
What do commonly occurring ISDN Cause Codes mean and how do I fix the problem when I get
one?
Situation:
A cause code alerts you that something is wrong with your ISDN connection. This Technote will
give you the plain English version of what the cause code that is described and how to resolve it.
NOTE: This technote describes some of the more frequently seen cause codes; by no means the
entire list. It attempts to relate the cause code and the problem it represents to real life
experience. If you see a cause code that is not listed here, please refer to the complete list of
cause codes. If you need further assistance after referring to this technote and that list of cause
codes, please consult your local telephone company/ISDN line provider.
Cause No. 0
Cause No. 1
Cause No. 16
Cause No. 17
Cause No. 18
Cause No. 21
Cause No. 34
Cause No. 41
Cause No. 42
Cause No. 50
Cause No. 65
Cause No. 88
Cause No. 96
Cause No. 100
Cause No. 102
Cause No. 0
This is usually given by the router when none of the other codes apply. This cause usually
occurs in the same type of situations as cause 1, cause 88, and cause 100.
Cause No. 1: unallocated (unassigned number)
This cause indicates that the destination requested by the calling user cannot be reached
because, although the number is in a valid format, it is not currently assigned (allocated).
What it Usually Means:
1. The SPIDS may be incorrectly entered in the Netopia or the Telco switch, giving a
SPID failure in the WAN Event History.
2. The ISDN phone number being dialed by the router is invalid and the telco switch
cannot locate the number to complete the call, as it is invalid.
3. On long distance calls, the call cannot be properly routed to its destination.
Cause No. 16: normal call clearing.
This cause indicates that the call is being cleared because one of the users involved in the
call has requested that the call be cleared.
What it Means:
This could be almost anything; it is the vaguest of the cause codes. The call comes down
normally, but the reasons for it could be:
file://C:\WINDOWS\Desktop\technotes\hardware\NIR_044.html
1/2/01

---

Technical Notes: Selected Cause Codes for ISDN Routers
Page 2 of 4
1. Lack of protocol negotiation, possibly due to misconfiguration of TCP/IP parameters
on the router.
2. Link Timeouts of the call due to same.
3. Idle Timer at either end of the connection is activated.
4. A thousand other things.
Cause No. 17: user busy.
This cause is used when the called user has indicated the inability to accept another call.
It is noted that the user equipment is compatible with call.
What It Means:
Calling end is Busy; no tricks here.
Cause No. 18: no user responding.
This cause is used when a user does not respond to a call establishment message with
either an alerting or connect indication within the prescribed period of time allocated
(defined in Recommendation Q.931 by the expiry of either timer T303 or T310).
What It Means:
The equipment on the other end does not answer the call. Usually this is a
misconfiguration on the equipment being called.
Cause No. 21: call rejected.
This cause indicates that the equipment sending this cause does not wish to accept this
call, although it could have accepted the call because the equipment sending this cause is
neither busy nor incompatible.
What It Means:
This is usually a telco issue. The call never reaches the final destination. This can be
caused by bad switch translation from the Central office to the call's destination, or a
misconfiguration on the equipment being called (i.e. not configured properly to answer
calls).
Cause No. 34: no circuit/channel available.
This cause indicates that there is no appropriate circuit/channel presently available to
handle the call.
What It Means:
There is no place on the Public Telephone network to place the call. Usually a temporary
problem. The call never gets to its destination.
Cause No. 41: temporary failure.
This cause indicates that the network is not functioning correctly and that the condition is
not likely to last a long period of time: e.g., the user may wish to try another call attempt
almost immediately.
What It Means:
This means that there is a temporary failure at the physical layer on the ISDN network. If
you remove the ISDN cable from the Netopia, you would see this. It's usually temporary.
Cause No. 42: switching equipment congestion.
This cause indicates that the switching equipment generating this cause is experiencing a
period of high traffic.
file://C:\WINDOWS\Desktop\technotes\hardware\NIR_044.html
1/2/01

---

Technical Notes: Selected Cause Codes for ISDN Routers
Page 3 of 4
What It Means:
Just too much going on at this point on the ISDN network to get the call through to its
destination.
Cause No. 50: requested facility not subscribed.
This cause indicates that the requested supplementary service could not be provided by
the network because the user has not completed the necessary administrative
arrangements with its supporting networks.
What It Means:
The switch looks at the number being dialed and thinks it is for another service rather
than ISDN. If the phone number is put in the correct format, the call should be placed
properly. There are no standards for this, all Telcos have their own system for
programming the number formats that the switches will recognize. Some systems want to
see 7 digits, some 10, and others 11.
Cause No. 65: bearer capability not implemented.
This cause indicates that the equipment sending this cause does not support the bearer
capability requested.
What It Means:
1. In most cases, the number being called is not an ISDN number but an analog
destination.
2. The equipment is dialing at a faster rate than the circuitry allows, for example,
dialing at 64K when only 56K is supported.
Cause No. 88: incompatible destination.
This cause indicates that the equipment sending this cause has received a request to
establish a call that has a low layer compatibility, high layer compatibility, or other
compatibility attributes (e.g., data rate) that cannot be accommodated.
What It Means:
1. This usually means that the Number To Dial in the Connection Profile is in the wrong
format. You may need to dial a 10 or 11 digit number, or dial a 9 in front of the
number if it is a Centrex line.
2. This problem may also give a Cause 111.
3. Dialing at the wrong line speed can also give this Cause.
Cause No. 96: mandatory information element is missing.
This cause indicates that the equipment sending this cause has received a message which
is missing an information element which must be present in the message before that
message can be processed.
What It Means:
This is rarely seen in North America but usually means that the number that is being
dialed is in the wrong format, (similar to cause 88). Some part of the format being used is
not understood by either the remote side equipment or the switching equipment between
the source and destination of the call.
Cause No. 100: invalid information element contents.
This cause indicates that the equipment sending this cause has received and information
element which it has implemented; however, one or more of the fields in the information
element are coded in such a way which has not been implemented by the equipment
sending this cause.
file://C:\WINDOWS\Desktop\technotes\hardware\NIR_044.html
1/2/01

---

Technical Notes: Selected Cause Codes for ISDN Routers
Page 4 of 4
What It Means:
Like cause 1 and cause 88, this usually indicates that the ISDN number being dialed is in a
format that is not understood by the equipment processing the call. SPIDs will sometimes
fail to initialize with a Cause 100, or a call will fail with this cause.
Cause No. 102: recovery on timer expiry.
This cause indicates that a procedure has been initiated by the expiry of a timer in
association with Q.931 handling procedures.
What it Means:
This is seen in situations where ACO (Alternate Call Offering) is being used. With this type
of call pre-emption, the Telco switch operates a timer. For example, when an analog call is
placed to a Netopia router that has two B Data Channels in place, the router relinquishes
the second channel, but if it doesn't happen in the time allotted by the switch
programming, the call will not ring through and will be discarded by the switch.
file://C:\WINDOWS\Desktop\technotes\hardware\NIR_044.html
1/2/01

---