Hey Guys,
do you know of any limitation on number of hunt groups for this version?
Rumour has it, can only support 300 Hunt groups.
I need 2000 :O
Of course they all overflow to one only..
If you wait until version 10 you can have 600 in select mode.
I'd expect most of these groups will have the same users in (let's face it Maximum of 3000 (server select) users with 2000 groups??? can't you just use a few groups and tag the incoming call route?
ACSS - SME
APSS - SME
APDS - Unified Communications
ACS - IP Telephony
ACA - IP Telephony
It's an Anmswering service.
Each Hunt group is a Client they answer for.
Any sugggestions are most welcome please.
Only 1 Group (apart the Monitor) has all the Operators in it..
All the others overflow.
Each Client, with its own hunt group has Announcements, VM access.
If there's another way. Please do let me know.
We have a similar customer with 1000 DDI numbers for 1000 customers.
As the group programming is beyond the capacities of IP Office we use tags in ICR and in the generic Leave/Queue/Still Queued actions we use the tags to provide unique wav files to the caller. The path to the wav files is /$TAG/Leave.wav, /$TAG/Welcome.wav or /$TAG/StillBusy.wav
Callers can leave a message which are emailed to a single email address with the tag as identifier.
Then you can serve 1000+ DDI numbers with minimal use of IP Office resources.
Thank you Intrigant
This sounds like the perfect solution.
I just need to figure the paths...
All emails with the tags will go to an email address.
But I guess Clients will not be able to listen to their own messages?
What system can handles this I wonder...
So did we, it is a separate field in TAPI but you need to be able to adjust the CTI software.
Another reason to match the groups to a part of the DDI number, that is available in TAPI by default.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.