Avoiding permanent IMB status
To prevent your circuit from spending more time in IMB than it needs to, open an information-only trouble ticket with your carrier before unplugging your hardware for any reason. This type of trouble ticket alerts the carrier to the fact that you will be removing your hardware from the circuit and gives you a trouble ticket number to reference when you call into have the circuit taken out of IMB.
If you don't want to go through this effort, simply place a loopback plug in the T-1 jack of the circuit from which you're disconnecting. This simple action tricks your carrier into thinking there is hardware connected on your end of the circuit for as long as the loopback plug is in place. This isn't an option if you have ISDN circuits, because your carrier needs to chat with your D channels to ensure that the hardware is active. The ISDN protocol is generally intelligent enough to know that it is speaking to itself and eventually places the circuit in alarm.
Removing a circuit from IMB takes about five minutes, after you reach a technician with the required credentials to make the change. The greatest potential delay comes from wading through the customer service department and waiting for the magic technician with the access to the switch to call you back.
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