Skip to main content

Huntgroup question

Posted by DruRoland on Fri, 11/05/2010

I'm trying to set up a relatively simple huntgroup, and encountering a few odd bugs.
The huntgroup I'm setting up should do the following:
Announce caller, ring internal ext 2025, offsite ext 2026, and external cell. Call should be presented to all 3 for 25 seconds, then drop the cell (avoid going to cell VM), ring an additional 10 seconds, and go to ext 2025 VM.
To accomplish that, I've done the following:
Within the PBX Manager, I set up a huntgroup to simultaneously ring 2025, 2026, and external cell for 25 seconds, with a final action of forwarding to a 2nd huntgroup. 2nd huntgroup rings 2025 and 2026 for 10 seconds, and has a final action of dumping to 2025's VM.

The extensions and cell ring properly, but there's a couple issues:
There's no caller announcing
The VM message isn't the one associated with 2025, instead it's the default.

Am I designing this properly and these are just bugs to be worked out, and/or is there a better way to do this?

Also, running manager 6.1.1.6, user portal 2.1.5.6, asterisk 1.6.2.11


Submitted by eeman on Fri, 11/05/2010 Permalink

dont make 2 huntgroups.. 1 huntgroup can have 20 ring groups

huntgroup-name

ring group 1 - ring extensions 2025, 2026, and external cell number, timout 25

ring group 2 - ring extensions external cell number timeout 10

other actions - go to voicemail 2025 option 'u'

what the hell do you mean caller anouncing? thats not a huntgroup feature.

Submitted by DruRoland on Fri, 11/05/2010 Permalink

Oh hell.. I didn't even notice I could set multiple ring groups.. Thanks for making me feel foolish! :p

I misstated, what I'm referring to is the caller screening allowed on an extension.
I'm trying to use that feature in conjunction with the huntgroup. If it's not possible, it's not a big loss, but, since the customer requested it...

Submitted by eeman on Fri, 11/05/2010 Permalink

call screening is an argument of the Dial application that launches a Macro (the M option of dial) to run before connecting the calling party. The only way to do that with huntlists is to fill your huntlist screen up with custom commands and effectively write the whole thing. The underlying framework exists but it will require a fair amount of coding. You could probably at least recycle the macro for screening.

Submitted by DruRoland on Fri, 11/05/2010 Permalink

Ah, I was afraid of that. Ah well, if they want it that bad, I'll dig through voip-info and put something together.

Thanks so much for the help!

Submitted by moshe on Sun, 11/07/2010 Permalink

Or you could try follow me based hunt it could do all you need and I know it announce the caller not sure about screening