Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MICS 7.1 hunt group/ringing conflict/brain teaser 2

Status
Not open for further replies.

Phonehed

Programmer
Apr 25, 2006
452
US
Got a customer with a MICS 7.1 w/PRI and a CP-100.

Without going into a lot of detail, I'm trying to think of the best way to make this work like they want it to without creating any conflicts.

They have two operators who always try to catch all incoming calls to their 8 different, published, main numbers by the 3rd or 4th ring. (Apparently at one time they had many different numbers for different departments and also for another location that they no longer have and I have suggested that they point them all at one number but to no avail.)

The 8 DID's are programmed to appear and ring on both of the (M-7324) operator sets. After 4 rings with no answer, they want to fna to an operator back up type hunt group with 4 or 5 members. None of those members have these lines ringing on their sets and none of them are in any pick up groups, any other ringing groups or any page zones.

Then they want it to ring that hunt group some 10 or maybe even 15 times and eventually end up in the general delivery mailbox on a no answer during the day. At night they want all 8 lines answered immediately by the AA in auto night mode.

The system wouldn't allow me to program the hunt group to forward to mailbox 1000 after the queue timeout for some reason so I'm not sure what's happening there.

Just to get them going right away, I temporarily programmed the 8 lines to ring only on a dummy set in the switch room and made it fna to the hunt group on 4. I bumped the fna ring counts up on the operator sets to 10 and the AA line answer command to 12.

It's not ringing quite as long as they'd like in the hunt group before the GD mailbox grabs it but for the most part, it's working pretty much like they want it to during the day.

They still want the two system operators to fna after 6 rings to their mailboxes though so obviously that's an issue I'll have to address.

I thought about removing the lines from the operator sets and then making a common set ring near them so they could both answer with either the pick up key or an answer dn. I'm not so sure that everything will work the way they want it to with that method and the suggestion will probably go over like a lead balloon.

No matter what I do though, I can't seem to get several of their main numbers to answer immediately in the night ring mode even though they are in the same ring group as the ones that do pick up immediately. The only set in that night ring group is the prime dn to vmail.

The customer says it was working like this all along until a thunderstorm and extended power failure "messed up the ringing" a couple of weeks ago but I'm not entirely convinced that it was working the way they described it to me. It certainly didn't look that way to me in programming and I'm beginning to suspect that I may have some kind of software issue here with either the MICS the CP-100 or possibly even the carrier. I rebooted both systems just to see if it might clear any garbage data but that made no difference.

They haven't complained of any line quality or line service issues but I'm gonna dive in on the RAD tonight just to see if I'm getting any errors from the carrier.

I put one of those problem lines in it's own service mode and ring group last week just to see if the system could answer it immediately and it did so I may do that with the other problem lines for now but that's just a band aid solution at best in my opinion.

I'm definitely open to any suggestions on this one!

Thanks in advance for your help!

Phonehed in Dallas
 
You say you tried to overflow to mailbox 1000. Did you mean the extension assigned to mailbox 1000, because you can't overflow to a mailbox? If that doesn't work, what happens if you overflow the hunt group to the voicemail DN?

As for the night mode problem, did you assign the voicemail DN to the night ringing group? If not, that will make the AA answer immediately.

Brian Cox
Oregon Phone
 
Oh that's right, I forgot I can't send a hunt group directly to a mailbox. The fna command on the operator's set was already getting it there on 10 rings but I went ahead and changed the hunt group to forward to the prime vmail dn.

I've got them set up now to where they are happy for the moment but it's just a band aid solution in my mind so I still think I need to reconfigure the whole scenario for them.

I guess what I'm really looking for here is alternate (and hopefully better) suggestions than mine as to the best way to do this.

Since they are forcing their two system operators to double as the two primary hunt group agents, I'm thinking I should just take all lines off of their phones and build a special hunt group just for them with all of the main lines assigned to it. Then if they're both busy it could immediately overflow to the back up hunt group (or forward on a no answer) and they could just busy out with their dnd keys at any time. Then I could bump their fna commands back down to 4 so anyone could get to their mailboxes in a timely manner again. Of course the operators will probably hate it! I guess if I had any sense I'd just tell them not to force their operators to try to double as hunt group agents. lol

And yes, the vmail dn is the only one in the night ring group and it has been all along. I'm beginning to think the thunderstorm may have caused some kind of data corruption (possibly due to a power interruption in the middle of a reboot sequence) and I have been unable to make any progress on the night ring issue so I think I'm going to start a whole new thread on that as the problem appears to be more complex than I originally thought.

I've even been tempted to run start up just to try to clear any garbage data or corruption and then reload from my current back up but I've never tried that method before to clear such a problem and for all I know it may just reload the garbage. Anyone here ever tried a similar fix or have some input on that?

Thanks again for your help there Brian, you do good work!

Phonehed in Dallas
 
If it's pretty much working the way they want I'd leave it alone. You know how much people like change!

Double check your NVRAM cartridge to verify it is a Release 02. A Release 01 cartridge wreaks havoc with PRI's.

Since you have a PRI be sure you have the PRI Enabler keycode before you do a STARTUP as this will wipe out the keycode. The system ID will stay the same.



Brian Cox
Oregon Phone
 
2 HG's is a good idea.

You can over flow a HG to a mailbox but the mailbox number must be the same as the HG DN.
What you can then do is setup that mailbox (second HG) to notify of messages internal to the DN of the first HG.

i.e

HG001 -737 rings to 2 sets
overflow to HG002
HG002 -738 rings to 5 sets
overflow to F985
Create mailbox 738
Notify to 737 (maybe also set alt ext to a set that does not have vmail)

As for night service did you make sure the lines are also in that night group?
Does Manual night service work?.




=----(((((((((()----=
curlycord
 
I upgraded this one myself last year so I made sure it was a release 2 NVRAM pack back then and I verified that again last week and I always write the PRI key codes on the inside of the cabinet cover with a Sharpie for just such occasions.

All of the lines that won't answer at night are definitely assigned in the night ring mode and the only member in the ring group is the prime dn to vmail.

I just wonder if a start up and restore would really clear this problem and somehow I don't think it will so I'm gonna save that as a last resort.

Haven't tried manual night mode yet but that's worth a shot so I'll definitely give it a whirl. Of course everything may change if I reconfigure it with two hunt groups and put all 10 main lines in the primary group.

I'm thinking I've either got some kind of a software glitch or possibly some kind of conflict in the system somewhere that might be preventing an immediate answer at night on about 8 of those 10 lines. It's just weird and I suppose the carrier could also have something to do with it but since hunt groups are kind of finicky when it comes to line conflicts, I went ahead and checked all of my hunt group agents to make sure they didn't have any of those main lines assigned to their sets and I checked for any ringing group conflicts or overlaps, even took the agents out of all pugs & page zones.

I know I can't have more than 30 agents in a group and I only have 5 but I can't find anything about a maximum number of lines allowed in a hunt group anywhere. Seems to me that you should be able to assign as many as you want.

I guess the bottom line is that the dual hunt group solution is probably the best scenario we come up with for their daytime dilemma and perhaps when I reconfigure it that way, we may have a whole different story on the night ring issue.

I'm still open to suggestions on both though. Thanks again for all the help!

Phonehed in Dallas
 
Correction:

I forgot that when I was testing out on site last week I did use manual night ringing to test several of the problem lines and it made no difference.

Phonehed in Dallas
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top