Rollover not working

[TelecomTech34]

Hello everyone,

I've had a few complaints that users are getting a busy signal once in a while when calling x4479. This extension is MARP on one 3903 and has a rollover of 5479. The only other phone these extensions are on is his secretary's phone, she has his extensions on keys 2+3, not MARP and built as an SCR. She has her own extension and rollover MARP on keys 0+1. Both phones have LHK set to 1, and HTA(hunting) is allowed.I made several test calls and only was able to recreate the problem once when I called x4479 and had his secreatry answer it on her phone, then dialed x4479 and got a busy. I tried to do this several more times and the calls went through fine. I should add that in the past we had an issue where his phone was busy for every call and even went dead at some point. His phone was replaced, his cross connect was replaced and switched to a new feeder pair, switched his TN also, and we even switched to a different jack under his desk. Any advice is appreciated.

 

[TelecomTech34]

I would think that they would want callers to go to voice mail if there is no answer. Does that mean his callers will have to sit through several rings and won't it go to her voice mail eventually if she doesn't answer not his. I think they were setup like this because in some cases the Execs would like them to field their calls while in a meeting or away as opposed to bouncing callers around. Also I don't think having the possibility of a secretaries phone call rolling to an Exectives phone would be acceptable, it will probably be a slim chance of happeneing often but I can see that as being an issue. Hope I'm following you correctly.

 

[KCFLHRC]

OK, good luck with it

 

[nessman]

Any time I have weird issues with multiple phones sharing DN's and they want all sorts of weird hunt/forward patterns, I just program those DN's as their own MARP'ed 500 sets - so long as they have licenses, tag out the ports on the MDF, and build the specified hunting/forwarding patterns in there. Far more simpler, cuts out on the confusion - especially when dealing with sets that have a couple of AOM's (just too much crap to look at in programming), and prevents a user from screwing up the pattern if they manually forward their phone with MARP'ed DN's elsewhere.

Remember, the phone with the MARP'ed DN controls the hunt/forward behavior of that DN.

On the other hand, if you have several secretaries sharing the same DN for an executive, instead of hunting - may want to consider an MRC key at a key number above the LHK value instead. Rings all their phones.

 

[Funk49]

KCFLHRC (TechnicalUser)

30 Jan 14 11:41
Do I have to set LHK to 5 to accomodate those too Yes, you may have to do this

Also about the hunting, will this ever hunt from one users lines to the other? Yes

What if the scretary had her lines tied up wil another call to her roll to his line?Yes

Wouldn't this be no, no and no based on the DN MARP'd phone?
So if the boss has MARP SCR 4479 Key 0 and MARP SCR 5479 on Key 1 and has HTA and LHK 1, it doesn't matter what the secretary has as LHK because she has the line appearances of 4479 and 5479 ringing at both phones BUT hunt controlled by the boss's MARP's phone right? If she is not the MARP for that DN how would it then roll over to other boss lines on her phone?

 

[KCFLHRC]

I think the issue is when she answers his line, because it is actually busy on her phone and not his was my thinking. Either way, my point was all these scenarios are easy to try. He was getting intermittent busy's and couldn't figure out the problem. So I made some suggestions to try. Try it or don't, doesn't matter to me.

 

[KCFLHRC]

I think when the Marped TN is not actually busy is causing his issues. So the secretary answers his DN on her phone, the Marped TN is not actually busy because it got answered on her phone, next call comes into his prime DN and tries to hunt up the key strip but cant because the line is actually busy on another TN on a different key. That was my thought. I have seen these issues in the past. Sometimes all you have to do is out both phones and rebuild them and it will start working properly.

 

[TelecomTech34]

KCFLHRC I believe that's exactly what's happening. Testing has been very inconsistent because I have tried this scenario where the secretary is on his main line and I call his main line and it works sometimes and sometimes I get a busy. I will rebuild both to see if the issue goes away. The complaints have been weeks, sometimes months apart so it's hard to know if it's truly fixed but I'll give it a try.