Installation made busy: IMB
Installation made busy, or IMB, is a protected state that is usually imposed by your carrier on an entire circuit to prevent it from generating alarms in the carrier's network. For example, if you unplug your hardware from the circuit, your carrier immediately sees alarms at its end of the span. The technician who is listening to the piercing screech of the alarm doesn't have your contact name and phone number, so he or she does the easiest thing to end the maddening alarm. Usually, the easiest thing to do is to busy out the circuit, or place the circuit into the IMB state. The bad news is that when you plug your hardware back in, you won't be able to use it because the carrier has been busied it out.
Remember Every carrier has its own procedure for placing a circuit into the IMB state. The process might be manual, with a policy to wait until the circuit has been in alarm mode for eight or ten hours before busying out the circuit. Sometimes, however, the process is automated; you may have as little as an hour before the carrier automatically busies out your system.
Carrier failure: CFL
Carrier failure is like IMB, because it generally affects your entire circuit, and not just a few channels. The bad news about a circuit in carrier failure is that this state commonly indicates a substantial problem that needs to be addressed pronto by your carrier. If your CSU fails, or if someone accidentally cuts through the wiring of your circuit with a backhoe, or if your carrier's switch sustains a direct lightning strike, your circuit is in carrier failure.
Remember Carrier failure indicates a more serious issue and generally takes several hours to diagnose. After the technician finds the source of the problem, it can be another 4 to 24 hours before your circuit is back in service. Keep this in mind when you set expectations. (In other words, it's time to have a chat with the head of your telemarketing department.)
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