Thanks, buffs. There's nothing in the call timers that affects the number of rings before an auto attendant answers - at leat not in 5.0.6. I did get around it by sending that one line card port to the ATA port (we're not using it for anything on this system), then setting the call coverage...
In one of my installations 5.0.6 almost gets rid of it, but not quite. I have a case open and engineering is working on it right now. My other installation is rock solid with 5.0.6, so you'll probably be OK with just that.
No, I did not replace the country pack. I will try this on Monday, and I am also going to try deleteng 4.4.8 from the unit and re-installing it. I hope that this will make a difference. Thanks for the post.
Just an update to my progression with this problem. The V3000s that I got back from 3COM came in with 4.4.2 code, and I left them with 4.4.8 because it was late in the day and I hadn't got 5.x the license codes yet. This has been nagging at me, so I took one off the shelf that had 4.4.2 today...
I did have a case open on one of them, but I requested the RMAs on my own initiative. I only suspect that there could have been a production problem since I ordered these two at the same time and had the exact same problem with them. Also, the trouble went away immediately after replacing the...
I just finished a wrestling match with two of these myself. Both V3000s were purchased at the same time, and both exhibited the same symptoms. 5.0.6 helped, but did not completely get rid of the echo. The loop current was high on the analog lines which I've always seen to be a contributing...
I've had that problem with low loop current before. If it drops below 21 mA or so it will drop calls intermittantly. Especially if the user is talking loud.
I have a new V3000 installation using 5.0 code. 4 phones, two analog lines, 8-Port OfficeConnect switch with 802.1p capability, and inline power injectors. We started out from the git-go with echo problems on the analog lines which were quickly isolated to high loop current (44 ma) on the CO...
I thought about that, Don, but don't really know if it can be done. Called Adtran and they didn't seem to think so. At the remote end is an Atlas 550, and on the NBX side is a TSU 120. I saw some stuff in the 550 about dial plans and digit filters, but the filter values would only accept...
Tried the striplead thing - unfortunately the T-1 card is not sending the # to the NCP for processing, so no dialplan or pretranslator entires have any effect. If (let's say) the remote system is transferring a call to extension 106, it sends #106 across the T. The T-1 card sees #10 and...
Got an NBX 100 sending/recieving inter-office and trunk-to-trunk calls across a PTP T-1. Simple setup, sending/recieving 3 digits for call routing. Remote office has Executone PBX that sends a #-sign to indicate a trunk-to-trunk transfer if the call is originating from an outside line. Trouble...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.