https://www.cisco.com/c/en/us/support/docs/voice/digital-ccs/15415-bri-voice-port-cfg.html
Telstra Exit Date
The final exit date for ISDN in all areas nationwide is 31 May 2022.
Interfaces
- U
- S/T
- S
- T
- R
- NT1
- NT2
- TA
- TE
B/D Channels
- 2 x 64kbps (B) channels
- 1 x 16kbps (D) channel
Protocols
- Q.921 describes data-link LAPD
- Q.931 describes network layer
TE startup sequence
- Line inactive
- TE becomes active and signals a 7E HDLC flag (7E = “01111110”)
- Network switch send frame with the A-bit set to 0 (A=0 = no activated)
- TE then synchronises on three successive pairs of line code voilations
- TE then starts sending physical frames
- NT synchronises using line code violations
- NT starts sending frames with A-bit set to 1 (A=1 = activated)
Alarms
OSI Layers
Layer 1
NIST Testing Procedures
User Mode (TE) States
| L1 State | L1 State Name | L1 State Description |
|---|---|---|
| F1 | Inactive | In this inactive (powered-off) state, the terminal equipment (TE)1 is not transmitting and can not detect the presence of any input signals. |
| F2 | Sensing | This state is entered after the TE has been powered on but has not determined the type of signal (if any) that the TE is receiving. When in this state, a TE may go into a low power consumption mode. |
| F3 | Deactivated | This is the deactivated state of the physical protocol. Neither the network termination (NT)2 nor the TE is transmitting. When in this state, a TE may go to a low power consumption mode. |
| F4 | Awaiting Signal | When the TE wishes to initiate activation, it sends an Activation signal to the NT and awaits a response. |
| F5 | Identifying Input | At first receipt of any signal from the NT, the TE stops sending Activation signals and awaits the activation signal or synchronized frame from the NT. |
| F6 | Synchronized | When the TE has received an activation signal from the NT, it responds with a synchronized frame and is awaiting a synchronized frame from the NT. |
| F7 | Activated | This is the normal active state, with the protocol activated in both directions. Both the NT and the TE are transmitting normal frames. State F7 is the only state where B-channel and D-channel contain operational data. |
| F8 | Lost Framing | This is the condition when the TE has lost frame synchronization and is awaiting re-synchronization. |
Network Mode (NT1) States
| L1 State | L1 State Name | L1 State Description |
| G1 | Deactivated | |
| G2 | Pending Activation | |
| G3 | Activated and Working | |
| G4 | Deactivated Request Received |
THE ACTIVATION PROCEDURE CAN BE INITIATED BY THE TE OR THE NT.
THE DEACTIVATION CAN ONLY BE INITIATED BY THE NT.
Physical Interface
BRI S/T Interface (RJ-45) Pinout
| RJ-45 Pin | TE | NT | Polarity |
| 3 | Transmit + | Receive + | + |
| 4 | Receive + | Transmit + | + |
| 5 | Receive – | Transmit – | – |
| 6 | Transmit – | Receive – | – |
BRI U Interface (RJ-45) Pinouts
| Wire | NT (RJ-45) | LT(RJ-45) |
| Tip | 4 | 4 |
| Ring | 5 | 5 |
Terminal Endpoint Identifier (TEI)
Layer 2 (Q.921)
Layer 3 (Q.931)
Q.931 ISDN Cause Codes
| Hex | Decimal | Cause |
|---|---|---|
| 0x1 | 1 | Unallocated or unassigned number |
| 0x2 | 2 | No route to specified transit network (Transit Network Identity) |
| 0x3 | 3 | No route to destination |
| 0x4 | 4 | Send special information tone |
| 0x5 | 5 | Misdialled trunk prefix |
| 0x6 | 6 | Channel unacceptable |
| 0x7 | 7 | Call awarded and being delivered in an established channel |
| 0x8 | 8 | Prefix 0 dialed but not allowed |
| 0x9 | 9 | Prefix 1 dialed but not allowed |
| 0xA | 10 | Prefix 1 not dialed but required |
| 0xB | 11 | More digits received than allowed, call is proceeding |
| 0x10 | 16 | Normal call clearing |
| 0x11 | 17 | User busy |
| 0x12 | 18 | No user responding |
| 0x13 | 19 | T.301 expired: – User Alerted, No answer from user |
| 0x15 | 21 | Call rejected |
| 0x16 | 22 | Number changed to number in diagnostic field. |
| 0x17 | 23 | Reverse charging rejected |
| 0x18 | 24 | Call suspended |
| 0x19 | 25 | Call resumed |
| 0x1A | 26 | Non-selected user clearing |
| 0x1B | 27 | Destination out of order |
| 0x1C | 28 | Invalid number format or incomplete address |
| 0x1D | 29 | EKTS facility rejected by network |
| 0x1E | 30 | Response to STATUS ENQUIRY |
| 0x1F | 31 | Normal, unspecified |
| 0x21 | 33 | Circuit out of order |
| 0x22 | 34 | No circuit/channel available |
| 0x23 | 35 | Destination unattainable |
| 0x24 | 36 | Out of order |
| 0x25 | 37 | Degraded service |
| 0x26 | 38 | Network out of order |
| 0x27 | 39 | Transit delay range cannot be achieved |
| 0x28 | 40 | Throughput range cannot be achieved |
| 0x29 | 41 | Temporary failure |
| 0x2A | 42 | Switching equipment congestion |
| 0x2B | 43 | Access information discarded |
| 0x2C | 44 | Requested circuit channel not available |
| 0x2D | 45 | Preempted |
| 0x2E | 46 | Precedence call blocked |
| 0x2F | 47 | Resource unavailable, unspecified |
| 0x31 | 49 | Quality of service unavailable |
| 0x32 | 50 | Requested facility not subscribed |
| 0x33 | 51 | Reverse charging not allowed |
| 0x34 | 52 | Outgoing calls barred |
| 0x35 | 53 | Outgoing calls barred within CUG |
| 0x36 | 54 | Incoming calls barred |
| 0x37 | 55 | Incoming calls barred within CUG |
| 0x38 | 56 | Call waiting not subscribed |
| 0x39 | 57 | Bearer capability not authorized |
| 0x3A | 58 | Bearer capability not presently available |
| 0x3F | 63 | Service or option not available, unspecified |
| 0x41 | 65 | Bearer service not implemented |
| 0x42 | 66 | Channel type not implemented |
| 0x43 | 67 | Transit network selection not implemented |
| 0x44 | 68 | Message not implemented |
| 0x45 | 69 | Requested facility not implemented |
| 0x46 | 70 | Only restricted digital information bearer capability is available |
| 0x4F | 79 | Service or option not implemented, unspecified |
| 0x51 | 81 | Invalid call reference value |
| 0x52 | 82 | Identified channel does not exist |
| 0x53 | 83 | A suspended call exists, but this call identity does not |
| 0x54 | 84 | Call identity in use |
| 0x55 | 85 | No call suspended |
| 0x56 | 86 | Call having the requested call identity has been cleared |
| 0x57 | 87 | Called user not member of CUG |
| 0x58 | 88 | Incompatible destination |
| 0x59 | 89 | Non-existent abbreviated address entry |
| 0x5A | 90 | Destination address missing, and direct call not subscribed |
| 0x5B | 91 | Invalid transit network selection (national use) |
| 0x5C | 92 | Invalid facility parameter 93 Mandatory information element is missing |
| 0x5D | 93 | Message type non-existent or not implemented |
| 0x5F | 95 | Invalid message, unspecified |
| 0x60 | 96 | Mandatory information element is missing |
| 0x61 | 97 | Message type non-existent or not implemented |
| 0x62 | 98 | Message not compatible with call state or message type non-existent or not implemented |
| 0x63 | 99 | Information element nonexistent or not implemented |
| 0x64 | 100 | Invalid information element contents |
| 0x65 | 101 | Message not compatible with call state |
| 0x66 | 102 | Recovery on timer expiry |
| 0x67 | 103 | Parameter non-existent or not implemented – passed on |
| 0x6F | 111 | Protocol error, unspecified |
| 0x7F | 127 | Internetworking, unspecified |
| 0x80+ | 128 orhigher | Proprietary diagnostic code (not necessarily bad). Typically used to pass proprietary control or maintenance messages between multiplexers. |