I'm not sure if the trouble is in the MICS or in the CP.....

The back story.....customer is an executive center with 25 - 30 office suites that they lease out. Each suite has a Norstar T7316e phone. Some tenants have more than one suite, so they then have more than one phone. Also, there may be 1 or 2 CO lines on the phones. Each phone has its own mailbox. Each tenant has their CO lines set up in their own ring group so calls that come in after hours are properly routed to their specific voice mail.

The above scenario has worked fine for 5 years. There have been customers added and deleted over the years and there has never been a glitch. Now to my problem. Yesterday I added a new tenant. He got 1 CO line, 1 extension with a T7316e phone, and a voice mailbox. This morning I got a phone call that the new tenant's after hours phone calls were being routed to another tenant in the building. I went back to the customer's site and reviewed the programming. It looked fine....there was nothing in programming that connected the new tenant to the existing tenant. The new station had been properly set up to be prime to the new CO line, and the new station was assigned to the ring group. I compared all of my programming for the new CO line and the new extension to a long standing tenant and there was nothing that popped out as being programmed wrong.

Soooo....I then changed the ring group to see if that was the problem, but the trouble followed. I changed the new CO line to another CO port (also changed the programming in the ring groups, etc.) but the trouble followed. Then I assigned a new extension (also changed the prime station, etc.) and now the calls no longer go to the wrong tenant, but they go to the attendant instead, day and night modes both.

Then I rebooted MICS and CP, but trouble did not clear. All other tenants seem to be OK, just this new one is not working properly.

First, I am not sure if this if a MICS problem or a CP problem. Any suggestions? I am at a loss where to look next and would appreciate any feedback.

Kind of got lost...why ring groups? why not just FNA to their own mailbox?
You need to explain your setup.

I know this is confusing and debated about how to explain everything initially.

During the day incoming calls are answered by the attendant. The attendant transfers the calls to the tenant and if they are not in their offices, the calls are forwarded to the tenants own mailboxes.

After hours the management company did not want the calls to be answered by the main greeting. They wanted the calls to route to the tenants mailboxes where the tenants greeting is heard by the caller. In order for it to work this way, each tenant was set up in their own ring group. This has not been a problem until the other day.

I don't know if this helps or not...if you need more info on the set up, please let me know.

Hey Judy,
I understand what you are trying to do and your approach is exactly how I would handle it.

You are going to have to scan for everything the DN that you don't want ring is programmed into. Any ring group, DRT etc.

Your post says you got a phone call and you checked programming. Did you simulate the problem and see it for yourself? Was it a button ringing or an I/C path? Are these POTS or PRI lines?

Judy,
You have to remember that by default all lines in Ringing Group 1. So, if the Line you are working with is the member of VM Pilot ext. then at Nite it will go to Main griting. Set up a separate Ringing Group and make your Line to be pointed to the extension you needed to be the answer point around the clock and don't ignor all Marv's suggestions..

Marv, vad60, and CurlyCord, thank you for your suggestions. Here is what ended up being the problem.

One of the 2 answering positions had CFNA. When I removed CFNA, the new tenants calls processed properly. Why it took almost 5 years for this gliche to present itself is a mystery, but at least the problem has been identified and fixed.

Judy

Another mystery solved, is another mans puzzle resolved and life goes on.

THanks for letting us know.