This chapter describes common POTS and DSL problems and the causes of these issues for troubleshooting purposes.
For more information on the POTS issues presented here, see "Best Practices for Setting Up MetaSolv Solution Data".
Issue: networkElementIdentifier (LineServiceActivationType) is not populated for a line service.
Cause:
The switch equipment is not associated with a network element that has an element type associated with a technology/role of voice/switch.
NEID field is not populated on the properties window for the network element.
The port was changed in design without disconnecting the line and adding a new line. The Activation API does not currently return port information for both the old and the new port on a line service. The workaround when a port must be changed is to disconnect the line and add a new line with the same telephone number.
Issue: lineEquipmentNumber (LineServiceActivationType) is not populated for a line service.
Cause: Node Address is not populated on the equipment containing the assigned port. Node Address is captured on the equipment specification.
Issue: originatingEquipmentType (LineServiceActivationType) is not populated for a line service.
Cause: The value was not entered in the Mounting Type field on the equipment specification for the shelf equipment.
For more information on the DSL issues presented here, see "Best Practices for Setting Up MetaSolv Solution Data".
Issue: networkElementIdentifier (NetworkElementType) is not populated for a network element.
Cause: NEID field is not populated on the properties window for the network element.
Issue: activityCd (ConnectionAssignmentType) is not populated on a connection assignment.
Cause: The connection is not on the order. The activityCd is populated only if the item is the order. A connection is included in the export when it is not on the order if it is between two elements that are included in the path of an ordered virtual connection.