sundance-communications.com/forum Forums TDM Business Telephone Systems Mitel Telephones & Systems No Rollover to Night Bell

We recently cut over a customer from a 200 El to a 2000 Light. We are having a problem with the nightbell. Basically, it rings overhead and anyone can hit the feature code and pickup the line. Works fine when dialed directly. The problem is we cannot get the incoming lines to rollover to it if the attendant does not answer in time.

We have it set up as an ONS port, and we tried call rerouting first alternative to make it rollover to it, but it does not hit it. We made sure we selected the correct line, and when we go in the system and try to do it as a regular extension, the nightbell system goes off hook so it is always busy. I am sure it is something simple. Anyone have an idea on where to look? Thanks.

Look into the Misc form under Nite Bell . Check your stats on the ons port if it is locked out you have a hardware/wiring issue . Should reroute . Not enough info given to dig deep in the trenches ! Hope this helps

Here is a more detailed description of what we've got going on.

DID call comes in.On the Trunk Service Assignment form, all trunks set to - ABSORB 1 (first digit) - INSERT 2 (all extensions start with 2 and all extensions have a DID assigned to them).

Our case, XXX-9333 comes in. 9 is removed. 2 is added. 2333 is a softkey assignment on the Attendant Console. Rings in, attendant answers. no problem.

The reroute is set so for N N N N THIS THIS THIS THIS - 2000 (DN for the Nightbell.)

When we tested it, it will ring through and finally goes to voicemail (2000 is set like everyone else to go to the pilot number 2222 after 6 rings).

Our troubleshooting -

Dialing from any set - Nightbell rings overhead.

Transfer a call from one set to another to the nightbell - Nightbell rings overhead.

Attendant console dials NB (2000) directly - Nightbell rings overhead.

Attendant console transfers a call to NB, no ringing.

We watched 2000 on the second console to watch it go from IDLE to RINGING, and we then picked it up with #82000 (their feature code for remote pickup is #8) and we can get the call.

The call is routing, but if it is transferred or forwarded from the AC, the bell itself is not going off. But if it comes from another set, the bell rings no problem.

We think it is going to be a COS issue. On the 200, this setup worked exactly as the customer wanted, for a few years. On the 2000, it is not. We walked through to see what the COS's were set to (a third programmer did the bulk of the migration programming while we did the minor items) and all COS's are set to the default. Which leads us to believe it might be a COS option that we can't see yet.

While we sift through the options, we are also looking at burning a port to make 2333 a phantom set and setting maybe a DSS line on the AC, and test to see if that will ring the bell or not.

Any other ideas, or has anyone had a similiar problem? Thanks.

Do you have External SMDR turned on for all devices ? I so try to follow the call path when it fails . You could also do a CCS Trace when it fails . If you do a CCS trace run it during slow hours it captures a lot of system info . Have you tried it yourself from the console ?

We don't yet. We just monitored that of the extension to see if it was picking up the call or not. It still is, and if we transfer the call and hit #82000, we can pick up the call and speak to the person, just that the night bell indicator on the overhead paging system will not ring it. But I will get back to the site and the CCS trace to see if it is failing somewhere along the line. Thanks again .

Did you check to see if it might be a cadence issue by placing a buttset in parallel with the night bell?

johnp
ONS R Cadence ? That's a reach ! Fax maybe , Modem maybe . Loud Bell , I don't think so since sta to sta xfered calls ding a ling the bell ! My 2 cents !

It looks like we found it. The Bogan (sp?) device that is being used to deliver the night bell ringing is set for 1 full ring cycle. When external calls or calls being transferred from the attendant console reach it, they are ringing a double ring cadence, which delivers the call but did not trip the night bell ringing. Not knowing much about the device, my guess is so that it doesn't trip all the time.

On the ONS extension COS we set to ONS/OPS Internal Ring Cadence for External Callers = YES, and now it is ringing.

Thanks again everyone for your pointers.

I thought it was a Bogen, and I know they don't like the ring ring. :rofl:
Darrell,

That's "Thirty Days in the Hole" :dance:

Ok, coming back to this. Now we have an issue where the night bell is not ringing whether via external OR internal. We have done a bit of programming since Monday, and a third hand was also in. I've gone through and checked that the COS assignments are still correct, put an analog set inline with the circuit and it rings a single ring (but is sounds like a short ring), but it is now not ringing the overhead bell. There isn't a system-wide ring cadence setting other than the Tie trunks is there?