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!

IPO 500 Overflow time being ignored 2

Status
Not open for further replies.

rider90

Technical User
Jun 17, 2011
64
GB
The problem: Calls to the number correctly go to "300 Main N" but that Hunt Group rings for 20 seconds, not 11 seconds. It then correctly overflows to "930 All N" where the call only rings for 9 seconds before falling back "300 Main N" and then continues to loop.

Setup:
We have an IPO 500 system with an ISDN number coming in on line 30. The Destination for this is Hunt Group "300 Main N" with the Fallback as "930 All N"

Hunt Group "300 Main N" has two users in the Collective Ring Mode. Voicemail is Off and the Overflow time is 11 Seconds overflowing to "930 All N"

Hunt Group "930 All N" has 10 users in the list including the two from the "300 Main N" list. Voicemail is Off and the Overflow is Off.

The Voicemail is embedded. The handsets are IP 1608 phones. The system has had a reboot with no change.

HELP!
Why is this doing this? What am I missing? I can't work out why the first Hunt Group rings for 20 seconds instead of 11 seconds and why the second Hunt Group drops back after 9 seconds rather than continuing to ring until answered?

Any help or suggestions?

Many thanks,
Matt
 
I would set the no answer time on 10 seconds too.
If that fails then try changing the group name and don't use spaces (another bug that shows up once in a while)
If that fails delete the groups and build new groups without spaces in the name and use different numbers.


BAZINGA!

I'm not insane, my mother had me tested!

 
I am fairly certain on collective groups I have never run into issues with the overflow timer and no answer needing to be increments of it, but bugs are common thses days, in my initial post I hadn't realised it was collective :)

 
I have never had issue either but that does not mean that the bug is not there :)

BAZINGA!

I'm not insane, my mother had me tested!

 
I have for now removed the N from the end of the Hunt Group Names.

So First Hunt Group:
300 Main
No Answer Time 10 Seconds
Overflow 10 Seconds

Second Hunt Group
930 All
I want this group to ring forever. So what do I set as the No Answer Time and Overflow time?
 
Your only option is to add the group 20 times or so in the overflow group list.
It will always follow the timers of the first group so by adding the group multiple times it will stay there for x times the timers.


BAZINGA!

I'm not insane, my mother had me tested!

 
TekTips1.jpg


Is how I would do it.

| ACSS SME |
 
:O Thanks tlpeter, and Pepp

Right I may have mis-understood that from an earlier post. I didn't realise that you needed to add all the overflow groups to the first Hunt Group, or that you could add the same Hunt Group repeatedly!

I have now done that and it does now work!

Legends!

We have another system in our Head Office which was set up the same but it was never a problem so I assumed it was the correct way to set it up. Turns out that its just down to the extra number of staff which means the call is always answered in time anyway. I may re-visit that system and correct the timings on it.

Many thanks for your help. I guess on this occasion it wasn't a system fault or a bug but more a user error. Either way I have learned something from it! Generally, I'd say the system works rather well seeing as I set it up all my self :)

Again many thanks
 
I have counted 4 versions where the overflow timer on a collective group is impacted by the no answer timer, call it a bug. In that there is no real point in having the no answer time NOT be an interval of the overflow timer it is just best to make that standard practice.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
Also set your timers closed to IPO ring cycles. say 2 or 3 seconds / ring cycle.

Also - the view you have it in makes life hard (for me) change it to the three pane view - the button next to your ! button.

Also the way Pep shows there is the correct method and what Kyle says makes sense and you then sort your times out in your head easier later.

ACSS - SME
General Geek



1832163.png
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top