Getting the Basics of Dedicated Outbound Troubleshooting
When you troubleshoot a dedicated circuit, you do it in the reverse order that you troubleshoot switched phone lines. If you have a problem calling Hoboken, New Jersey, on a switched phone line, for example, you should perform your troubleshooting before you call your carrier and open up a trouble ticket. When it comes to dedicated circuits, however, you begin your troubleshooting after you open the ticket.
The reason you should open your trouble ticket forthwith is because you don't have many testing options on a circuit without the aid of a technician from your carrier. You might know that your circuit isn't working, but only your carrier can tell that 10 of your channels are in an RMB state and 14 are in IDL. Even if you know the problem you are experiencing is caused by your hardware, you should still open a trouble ticket to receive help validating the source.
Remember The troubleshooting steps in this tutorial deal with a simple dedicated long-distance voice circuit with one local loop provider. If you have a type 2 or type 3 circuit that involves more than one carrier to deliver the local loop, the troubleshooting process is more involved. One thing I do suggest is that you put all the carriers involved in your circuit on a conference call at the same time.
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