Guys,
I am trying to make a hunt group automaticly camp on, i have a parralell hunt group set up with 3 members and a 200% camp, but it is presenting a anouncment when busy asking to call back or camp on, i would like it to directly camp if busy.
Thanks again!
Seb
Internal Hunt Group Automatic Camp-on
- tot3nkopf
- Alcatel Unleashed Certified Guru

- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: Internal Hunt Group Automatic Camp-on
Note that a hunt group is not a waiting queue.
However you can use a workaround:
- use an entity for distribution of the call: create an entity prefix and route the external calls to the entity prefix
- create an incoming greeting guide and assign it a waiting message. Route this incoming greeting guide at the end of a timeout to the entity prefix also
- in entity distribution on the 1st choice choose hunt group number, on second choice choose incoming greeting guide prefix (this has to be created also)
- set in hunt group only 100% camp
In this way:
Incoming call --> entity call --> entity distribution
if HG busy --> waiting guide is played --> at timeout the call is routed back to entity and checks HG availability, then if still busy plays busy message and so on
if not HG is rung
Note: this is not FIFO --> there is no guarantee that for several calls first call will be presented first when HG is available.
However you can use a workaround:
- use an entity for distribution of the call: create an entity prefix and route the external calls to the entity prefix
- create an incoming greeting guide and assign it a waiting message. Route this incoming greeting guide at the end of a timeout to the entity prefix also
- in entity distribution on the 1st choice choose hunt group number, on second choice choose incoming greeting guide prefix (this has to be created also)
- set in hunt group only 100% camp
In this way:
Incoming call --> entity call --> entity distribution
if HG busy --> waiting guide is played --> at timeout the call is routed back to entity and checks HG availability, then if still busy plays busy message and so on
if not HG is rung
Note: this is not FIFO --> there is no guarantee that for several calls first call will be presented first when HG is available.
- giovanni.attolini
- Member
- Posts: 276
- Joined: 16 Apr 2009 13:44
- Location: Veranopolis-RS-BRAZIL
- Contact:
Re: Internal Hunt Group Automatic Camp-on
Hello tot3nkopf,
Are you sure this work? I am trying here but when the HG is busy the external call receive busy tone. May be the Incoming Greeting Guide prefix can not be access from entiy table.
Are you sure this work? I am trying here but when the HG is busy the external call receive busy tone. May be the Incoming Greeting Guide prefix can not be access from entiy table.
Giovanni A. Attolini
https://www.facebook.com/gio.atto
"When you make a stupid question, wait for a stupid answer!"
https://www.facebook.com/gio.atto
"When you make a stupid question, wait for a stupid answer!"
- tot3nkopf
- Alcatel Unleashed Certified Guru

- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: Internal Hunt Group Automatic Camp-on
I did this in the past. Incoming greeting guide prefix can be configured in entity distribution. Ina second incoming greeting guide configure the distribution to the entity (this second incoming greeting guide can be very short --> 0.1 sec and routed to entity prefix).giovanni.attolini wrote: Are you sure this work? I am trying here but when the HG is busy the external call receive busy tone. May be the Incoming Greeting Guide prefix can not be access from entiy table.
- giovanni.attolini
- Member
- Posts: 276
- Joined: 16 Apr 2009 13:44
- Location: Veranopolis-RS-BRAZIL
- Contact:
Re: Internal Hunt Group Automatic Camp-on
Let me know if I am correct:
Incoming Greeting Guide = 0
Voice Guide Index 1
VG 601
Timer 100
Routing Directory No = in blank
Voice Guide Index 2
VG 601
Timer 1
Routing Directory No = Entity Access
On first VG index inside the incoming greeting guide I put the VG and timer to hear it, on second VG index I put any VG with 1s time and routing No to entity call. OK?
Incoming Greeting Guide = 0
Voice Guide Index 1
VG 601
Timer 100
Routing Directory No = in blank
Voice Guide Index 2
VG 601
Timer 1
Routing Directory No = Entity Access
On first VG index inside the incoming greeting guide I put the VG and timer to hear it, on second VG index I put any VG with 1s time and routing No to entity call. OK?
Giovanni A. Attolini
https://www.facebook.com/gio.atto
"When you make a stupid question, wait for a stupid answer!"
https://www.facebook.com/gio.atto
"When you make a stupid question, wait for a stupid answer!"
- tot3nkopf
- Alcatel Unleashed Certified Guru

- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: Internal Hunt Group Automatic Camp-on
Depending on your needs:
- case 1) you need first a message: you have reached....; and then a waiting message you can use 2 greeting guides
- case 2) or just one waiting guide.
Routing is done like this:
case 1) DID table --> inc greeting guide prefix 1 -->incoming greeting guide routed to entity -->in entity first distribution is the hunting group second the incoming greeting guide prefix 2 -->incoming greeting guide 2 routed back to entity prefix
case 2) DID table -->entity call prefix -->in entity first distribution is the hunting group second the incoming greeting guide prefix 2 -->incoming greeting guide 2 routed back to entity prefix
Hope now it makes more sense for you (routing to entity is always performed in the incoming greeting guide distribution).
Do not forget to disable camp on in hunt group.
- case 1) you need first a message: you have reached....; and then a waiting message you can use 2 greeting guides
- case 2) or just one waiting guide.
Routing is done like this:
case 1) DID table --> inc greeting guide prefix 1 -->incoming greeting guide routed to entity -->in entity first distribution is the hunting group second the incoming greeting guide prefix 2 -->incoming greeting guide 2 routed back to entity prefix
case 2) DID table -->entity call prefix -->in entity first distribution is the hunting group second the incoming greeting guide prefix 2 -->incoming greeting guide 2 routed back to entity prefix
Hope now it makes more sense for you (routing to entity is always performed in the incoming greeting guide distribution).
Do not forget to disable camp on in hunt group.
- giovanni.attolini
- Member
- Posts: 276
- Joined: 16 Apr 2009 13:44
- Location: Veranopolis-RS-BRAZIL
- Contact:
Re: Internal Hunt Group Automatic Camp-on
Ok, thanks tot3nkopf. I will try the case 2.
Giovanni A. Attolini
https://www.facebook.com/gio.atto
"When you make a stupid question, wait for a stupid answer!"
https://www.facebook.com/gio.atto
"When you make a stupid question, wait for a stupid answer!"
