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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Office 4.1 HuntGroup Setup Similar to 3.2

Status
Not open for further replies.

PhoneGuy98

Programmer
Nov 17, 2006
20
CA
We have a client who wishes to upgrade from 3.2 to 4.1.

The issue is that they want to keep a similar setup to their 3.2 Huntgroups so that when a call is sent to the huntgroup and no one answers the call goes to voicemail (after timer period, with 4.1 this will continue until the voicemail timer expires). If Extensions for the huntgroup are busy then it quest the call until they are free (they user a number of huntgroups with just one extension in them).

I have tried emulating this using an overflow group but not having much success. I have also tried the call routing condition to do a busy check, but this does not work well if the user becomes available after it has been queued and decides not to answer the call.

Anyone else had any success with this ?

Thanks in advance,



 
You simply need to turn queuing on for the groups with a single member :)

ACS - IP Office Implement

"What the Crocodile Hat....was that?
 
Thanks for the quick reply. On a 4.1 system when I enable queuing the and the annoucements (so that users in queue get messages played) it appears to take the voicemail answer time to go to VM (even if the call is ringing).

I have tested this with their current config.

Here is an example

We have a huntgroup for one user. Queuing and announcements are turned on so that if the user is on the phone the caller has the option to wait until they are available. The problem lies in that if the user is not around, the call will ring the phone until the voicemail timer expires, this timer is fairly high (10minutes) for the announcement messages while a user waits in queue.

What I am hoping for is similar to 3.2 in that if the call goes unanswered after 15 seconds it goes directly to their VM mailbox. If they are on the phone the caller has the ability to wait with announcements.

Not sure if I am missing something simple. Call routing status seems to work, but can be a bit flaky if the user leaves a call and decides not to pickup the incoming call.

Thanks in advance
 
Is this capability in 4.2 ?

Main reason is this is a 406v2 IP office.

 
This corrected in V5 ? and is V5 supported on the 406v2 ? I thought it was only IP Office 500 devices

Any alternative for 4.1 for the time being ?

Thanks again
 
if it runs 4.0+ v5 will work on a 406v2

The "rules" of the first target HG apply to any subsequent groups.

What you could try is using overflow groups, with virtual members forwarding to other groups, this will then take the caller out of the first groups rules and then you can apply a second set of rules for the next group. (not that im in work mode really and not really taking in what you are trying to achieve.)
 
Thanks for the reply, gave that a try and didnt seem to work. Again as you mention I think the issue is that the initial group settings is overriding all overflow groups.

Bascially what I am hoping to achieve is as follows:

1. Have a hunt group with one extension as member.
2. On a no answer go directly to voicemail IE after 15 seconds go directly to VM
3. On busy queue with announcements. When available ring the phone. If the call goes unanswered after 15 seconds go to VM.

The issues look to be the voicemail timer, as this needs to be set fairly high for the announcements when the phone is busy to play the annoucements. If I turn this off everything works well, but no announcements get played.

I will take a look at V5, but after doing some quick reading it looks like it will have the same issue.

Thanks again for any insights.

 
you are better off doing this in VM Pro.

you can use an assisted transfer with a busy AND no-answer paths.

 
Thanks again for the reply, thats actually what I ended up doing, but not nessecarily in love with it, basically just had it do a check if the extension was in use and if so use the HG, if not sent to extension.

Forgot to mention this was all with VM PRO.

While I like the way they do the HG in 4.0+, I do wish they had an easy opt out to make it similar to 3.2. Not all clients want to queue on ringing.

Thanks again for the replies.
 
the IPO features are driven in two ways.
1) what the american market wants
2) what their competitors do.
 
the IPO features are driven in two ways.
1) what the american market wants

Go USA! All kidding aside, the product was taken from the UK way back when introduced, and I've always felt some features and development come from the EU market. (T3 sets... etc...) Nowadays, us pesky Americans have had our way with it. :)
 
.... i wrote a very nasty message here for our US members but i deleted it, it was over the top.
I just don't like the most of the US features and our customers hate them and consider them as "silly", "stupid", "insane" etc.
Just to remember:
When version 3.0 was introducedthen we got "appearance keys" and "line keys" etc.
Version 3.0 and 3.1 were a nightmare, these were the version with the US features built in even version 1.0 was more stable. So you can see what the UK developers thought about US "features". it took two years to fix the problems and make IP Office stable again.
I consider version 2.1 (3.0DT) and version 5 as the most stable versions available.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top