We put in a PRI configured as NI2 and intermittenly it will go out of service for a few seconds and then come back. I suspect it is the carrier AT&T but they have done a stress test and say it is our equipment. We have another PRI configured for LD and it is working fine and this is programmed the same. I have it configured b protocol on the DS1 baord but the Trunk group and signalling group is using protocol a. It will not let me use b since basic QSIG is not activated in the customer options page. Could this be the problem even though the other PRI is configured the same with no isue. I am also getting errors when I do a list measurements DS1 log.
Sometimes it will go for 2 days without an issue. I also did a status trunk when it was happening and got a OOS/FE-idle which is the carrier which causes our port to go out-of-service-NE
Member Port Service State Mtce Connected Ports
09/15 01B1615 in-service/idle no
09/16 01B1616 in-service/idle no
09/17 01B1617 in-service/idle no
09/18 01B1618 in-service/idle no
09/19 01B1619 in-service/idle no
09/20 01B1620 OOS/FE-idle no
09/21 01B1621 out-of-service-NE no
09/22 01B1622 out-of-service-NE no
09/23 01B1623 out-of-service-NE no
Sometimes it will go for 2 days without an issue. I also did a status trunk when it was happening and got a OOS/FE-idle which is the carrier which causes our port to go out-of-service-NE
Member Port Service State Mtce Connected Ports
09/15 01B1615 in-service/idle no
09/16 01B1616 in-service/idle no
09/17 01B1617 in-service/idle no
09/18 01B1618 in-service/idle no
09/19 01B1619 in-service/idle no
09/20 01B1620 OOS/FE-idle no
09/21 01B1621 out-of-service-NE no
09/22 01B1622 out-of-service-NE no
09/23 01B1623 out-of-service-NE no