reat concern among trading partners. Network problems happen. There's no way around it. Thus, when one IIC is dependent upon another, it is also dependent upon the other's ability to fix network problems and resolve trouble tickets rapidly. The general rule is that only the IIC that issues the trouble can decide when it has been resolved to satisfaction. In practice, however, it does not always work this way. 6.2.2 Trouble Management Gone Awry Picture this scenario: A DLEC co-locates its equipment in an NSP's switching center and purchases backbone capacity wholesale. The DLEC provides T-1 Internet services to business customers over circuits it leases from a local CLEC, who also maintains a presence in the NSP's switching center. The DLEC orders T-1 service from the CLEC and wants the circuit connected through its cabinet to the NSP's network and, thus, to the Internet. The DLEC orders added backbone capacity from the NSP to support the new customer circuit. The NSP then connects the CLEC T-1 circuit to the DLEC's cabinet and the DLEC's cabinet to the backbone network. The CLEC says the T-1 is active and the NSP says the added capacity is ready to go. When the Chapter 2 - A Detailed Look at OSS DLEC tries to activate service to its customer, however, the traffic cannot get through. The DLEC opens trouble tickets with both the NSP and the CLEC, asking for each to test its piece of the service and identify the problem. The NSP tests its link to the DLEC's cabinet and everything looks fine. The CLEC tests the T-1 circuit to its equipment, and it also seems to be okay. Each party closes its trouble ticket and points a finger at the other - but traffic still cannot get from the customer site to the DLEC. What is missing? After days of finger pointing and conference calls with account managers, provisioning staff and technicians, the DLEC discovers that one piece was taken for granted and never tested. The patch cable from the CLEC's cabinet to the DLEC's was bad all along. The NSP never tested it because while it per