Remembering the first rule of troubleshooting
The first rule of troubleshooting is to keep an open mind. Suspecting that a problem can be attributed to a particular source is fine, but don't be so sure you're right that you lose perspective. All the circuit states I describe in the following sections do suggest a likely source for the problem you're experiencing with your dedicated circuit. Most of the time, for example, a channel in RMB (remote made busy) state is having hardware troubles. However, there is that tiny chance that a glitch within your carrier is causing it to send the channel a message, or triggering the channel to sit in RMB. Alternative scenarios are always possible, not just for channels in an RMB state, but for all the circuit states listed in this tutorial. Use the information to guide your troubleshooting, but don't be so hung up on a single right answer that you dis-count the possibility that something else is causing the issue.
In this tutorial:
- Troubleshooting Your Dedicated Circuits
- Identifying the Level of Your Problem
- Identifying circuit variables in circuits that are DS-3 or larger
- Identifying DS-1-level circuit variables
- Identifying DS-0 or individual channel issues
- Categorizing the Nature of Your Problem
- Understanding dedicated call quality issues
- Understanding circuit failure issues
- Opening a Trouble Ticket for Your Dedicated Circuit
- Letting your channels be your guide
- Remembering the first rule of troubleshooting
- Remote made busy: RMB
- Installation made busy: IMB
- Avoiding permanent IMB status
- Managing Your Dedicated Trouble Ticket
- Getting the Basics of Dedicated Outbound Troubleshooting
- Step 1: Rebooting your hardware
- Understanding your trouble ticket options
- Step 2: Intrusively testing: Looping the CSU
- If looping the CSU fails
- Using a T-1 test set
- Step 3: Looping the NIU
- Getting the scoop on loops
- Step 4: Looping to your T-1 jack
- If you can't loop the T-1 jack
- Step 5: Looping the CFA point
- Following a Dedicated Troubleshooting Shortcut
- Validating the Circuit You Are Testing
- The Basics of Dedicated Toll-Free Troubleshooting
- Step 1: Identifying a provisioning issue
- Step 2: Redialing your dedicated toll-free number
- Step 3: Validating your dedicated RespOrg
- Step 4: Validating the DNIS configuration
- Step 5: Head-to-head dedicated toll-free testing