sundance-communications.com/forum Forums Other TDM Phone Systems ESI Telephones & Systems Lose Ability To Dial Out

You never answered the question of what type of lines you have......which plays a big part in trying to ID the problem.

If it is a PRI it isn't a disconnect issue.....fast busy indicates a problem with the circuit or else the system.

If it's POTS lines then they could all be locked up and no line is available.

I have had this issue several times. When we get it, the PRI has lost the D channel and the ESI has trouble reestablishing the link. In the end it is a carrier issue.

I've never heard that before! :rofl: Just Joking

New member! I wish I had a buck for every time I have heard that. I would split it with you and we both would be rich. :thumb:

The ESI's usually struggle if the carrier drops the D channel. Almost 100% of the ESI's will need a re-boot. Its probably Windows based and not really "propriatary" like everyones led to believe

Have an NIU log performed, clear MB598. Blue alarm = carrier and yellow = ESI or do I have that ass backwards?

Oh wait... before you go re-booting the system just reset the span the old fashioned way by pulling the plug to the PRI and pluging it back in.

That will fix it too, temporarily there is a problem with the carrier if the PRI is only dropping the D channel.

I will take a guess that the ESI 600 is using an EMBARQ HDSL PRI circuit. I will also guess that the dialing out problem is only on certain channels. There are two totally seperate issues with the system. The first is a problem with the software. This problem usually locks out channel 23. This first issue has supposedly been resolved in one of the recent "software versions of the week". The second problem is a toss up between ESI and NORTEL. It happens consistently starting with channel 20 and working its way down to 19,18 and others. This problem usually appears when there are more than 3 outgoing calls going on at the same time. Hence the once a week problem. The day when most businesses make the most calls.

This reply is in response to the "It is a Carrier Issue"

The D-Channel drop problem is an ESI problem. The ESI system is "Losing sight" of the D-Channel. When the D-Channel is supposedly lost the existing system calls never drop. If the Carrier drops the D-Channel all calls on the circuit are lost. This doesn't happen in the case. If you go into the alarm mailbox after one of these events you will most likely find that the messages are one sided starting with ESI asking: Where is the Carrier? There is usually no alarm from the Carrier to prompt this request from the ESI system.

Jeff
I am not experiencing this problem, I was just repling to the original poster that when I do have this issue where the esi locks up and has to be rebooted on a daily basis. We have found that it is the esi not able to bring the D channel back up, which is an esi problem, but the d channel shouldn't be going down, that is why I said it is a carrier issue. The only way we figured this out was we had a lec willing to work with us and monitor the pri while watching it in real time.

I had this trouble with an E-class Gen 2, not to the same extent, but it was definitely a carrier fault. The d-channel would drop, about once a week, requiring the customer to go to the phone room and unplug the cable from the smart jack to re-synchronize the PRI. It never did drop calls, so it would only be discovered when someone tried to call out and couldn't get through. The carrier insisted that nothing was wrong until they did "intrusive testing", after which they promptly agreed to install a brand new circuit, and migrated the customer's service onto it. It's been fine ever since.

I agree that it would be nice if ESI's PRI implementation had some way to recover from these types of carrier faults. From the sounds of it, most other systems do..............or not?