HuntGroup Overflow

[TOPBAY]

Hi All,

Can you do this?

1. Having incoming call

|​

2. HuntGroup1 5 rings. If no answered,

|​

3. HuntGroup2 5 rings. If no answered,

|​

4. HuntGroup3 ring forever.

IPO v500 R10 Ess

Thanks for your advice in advance.

 

[intrigrant]

Group 1 overflow time 25 seconds
Overflow list:
Group 2
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3
Group 3

 

[holdmusic34]

You should have an announcement in there, or the carrier won't recognise the call as answered and will disconnect adter 60 secs.

Try to spend the next 10 seconds not thinking about a blue eyed polar bear.

 

[IPGuru]

Technicaly no

when he IPO reaches the end of the overflow list it will start at the main group again
Integrants (extreme) example s
hows that you can repeat a group in the overflow group list to extend the amount of time it rings & is the best that can be done to extend the time an overflow group rings for


Do things on the cheap & it will cost you dear

 

[holdmusic34]

Technically yes. The carrier hasn't detected an answer and will auto hang up. An announcement, even of 1 sec of silence, will answer the call and make it an internal problem. It can ring until the cows come home to roost then.

Try to spend the next 10 seconds not thinking about a blue eyed polar bear.

 

[Pepp77]

Never had a call disconnect after 60 seconds because it hasn't been answered!

| ACSS SME |

 

[janni78]

It happens here as well, all ISDN carriers drop the call if it hasn't connected after 60 or 90 secs.

"Trying is the first step to failure..." - Homer

 

[Pepp77]

Got me doubting myself then for a minute so made some test calls.

Outgoing via ISDN2 to SIP DDI - rang for 2 minutes with no issues.
Outgoing via SIP to ISDN2 DDI - rang for 2 minutes with no issues.
Outgoing via ISDN2 to ISDN2 DDI - rang for 2 minutes with no issues.


| ACSS SME |

 

[janni78]

It's up to the carrier so your carriers might not do that.

I suspect that since the don't get paid while it's just "ringing" they want to get a connect so they can start billing people =)

"Trying is the first step to failure..." - Homer

 

[IPGuru]

holdmusic
I was referring to the "Stay on last over flow group" issue not the carrier timeout issue.
(Of course the correct answer to this problem is get enough staff to answer the alls in reasonable time period)

The timeout is carrier dependent & easily avoided by having call queueing announcements enabled (+ it is better for the caller if they get a comfort message at least then they know they are calling the right place)

He guess what my previous comment about staffing levels also "Fixes" this one.
This is the type of issue i refer to as a BOS problem (Bums On Seats)


Do things on the cheap & it will cost you dear

 

[holdmusic34]

Sorry IPGuru. Thanks for the clarification.

Try to spend the next 10 seconds not thinking about a blue eyed polar bear.