call flow help needed

[rongill]

So here is the situation

We have our reception - 8750
Parts - Direct line 8000
Service - Direct line 9000

When the receptionist leaves for lunch she forwards her phone to the parts main line and all the calls that come into the main branch number go into parts. What they want is for all the parts and service phones to ring. I was thinking to just MCR 8750 to all the parts and service sets. This will work but I'm thinking when customers call the parts number directly its going to follow the same pattern which I don't want.

So I'm thinking the receptionist forwards to a phantom DN and that phantom is MCR on all the sets?? Is that the best way?

Our vendor has already created alot of phantoms but I don't know how. Can anyone help me out if this is the best way to do it? Thanks

 

[thattekguy]

Just add the new mcr extension to all sets needed. You will also want to make sure the dn is available, PRT LUDN.

 

[rongill]

thattekguy - did you mean create a phantom and add that DN?

I didn't see an edit function so im posting again with some corrections ..

So here is the situation

We have our reception - 8750
Parts - Direct line 8000
Service - Direct line 9000

When the receptionist leaves for lunch she forwards her phone to the parts main line (8000) and all the calls that come into the main branch number go into parts. What they want is for all the parts and service phones to ring. I was thinking to just MCR 8000 to all the parts and service sets. This will work but I'm thinking when customers call the parts number directly its going to follow the same pattern which I don't want.

So I'm thinking the receptionist forwards to a phantom DN and that phantom is MCR on all the sets?? Is that the best way?

Our vendor has already created alot of phantoms but I don't know how. Can anyone help me out if this is the best way to do it? Thanks

 

[GHTROUT]

Let's put "Phantom" into perspective. A Phantom is a DN which does not appear on any physical TN. You use a phantom to make one DN always rings at another DN.

An example of a phantom might be this: Employee Joe Smith is terminated and his work is now done by his co-worker Jane Doe. Joe Smith's office is turned into a bathroom and his phone is removed from service. The problem is customers still ring Joe's number so we make his DN a Phantom that directs callers to Jane. Now, whether you call Joe or Jane, you get Jane's phone.

As for your issue at the Reception - Parts - Service areas, I would add a "night bell" (just any bell ringer on an analog TN) on the wall in each of the areas that must back up Reception. Now when Reception takes a bathroom break, they forward to the DN of the bell and whomever can answer it does, using the "Call Pickup" feature.

If pulling new wire is not in the cards, remember you can just spare off a wire pair from an existing location, and put the bell at desk or jack height.

If adding new bells and whistles is not in the cards, then add a new DN that appears on each and every one of the phones that must back up Reception - then tell Reception that the new DN is the one they Forward to when they take a break.

You can add it as an MCR. But remember, MCR has good and bad to it:

http://www.ghtrout.com/ghtrout/files/Example_of_MCR.html

In your scenario, there is no application for Phantoms - you just need a DN to appear where you want Reception calls to ring - so she can forward to that DN, and it rings where it needs to.


[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators