How come my DNs under the hunt-pilot is not working ??

Unanswered Question
Jul 6th, 2009


I have a main line (76519999) which I have configured to a hunt-pilot number 4999, to hunt sequential to a list of DNs (9940 - 9949). Under my DNs, i have 'call-forward busy 804' and 'call-forward noan 804 timeout 15'. 804 is my (AA) autoattendant. The strange things is;

76519999 (main line) ----> 4999 (hunt-pilot) -----> DNs (9940 - 9949)

When I dial to any of the DNs (9940 - 9949), the AA pickup after certain rings. But when i dial to 4999 it does hunt the first DN which is 9940 it will just keep ringing without the AA. How come this happen ?? Need helps !!

My environment is Cisco 2851/CME 7.0

Best regards,

Lawrence Chew

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Steven Smith Mon, 07/06/2009 - 08:26

It is hunting sequentially through the phones.  Probably will take awhile to get to the final DN. 

Also, do you have a final setup on the hunt group?  The call forward on the phones isn't enough.  You need to have the final setup on the hunt group.

For CME questions, you should use the netpro forums.  This community is specifically for the UC500.

wfchew2007 Mon, 07/06/2009 - 09:03

Hi Steven,

Please assist on the hunt-group. Since UC/CME is almost the same, so i post it anyway for more viewers.

Best regards,

Lawrence Chew

Steven Smith Mon, 07/06/2009 - 09:09

I don't mind assisting on this one, but there are some differences and I don't wan't users to get confused, so it would be better to have this in the netpro forum.  As I said in my other post, do you have a final setup on the huntgroup?  Could you post your config without the passwords here?

wfchew2007 Mon, 07/06/2009 - 17:32

Hi Steven,

Hereby attached is the working configuration.

As mentioned earlier, when dial to the hunt-pilot no. 4999 it will start hunt the first number in the list (9940 - 9949) which it rings and keep ringing until timeout, without entering to AA (804). My AA configuration is under the CUE. The strange thing is, when i dial to 9940 it rings for 5 and later entering to AA.

Best regards,

Lawrence Chew

Steven Smith Tue, 07/07/2009 - 07:16

Under the ephone-hunt, you need the final command.

Something like this.

ephone-hunt 1 sequential
pilot 4999
list 9940, 9941, 9942, 9943, 9944, 9945, 9946, 9947, 9948, 9949

final 804

The final is used to determine where the huntgroup should go after it finishes the huntgroup.  The call forwards on the ephones do not direct this.

wfchew2007 Tue, 07/07/2009 - 07:32


Question, in each of the DN (9940 - 9949) there is such setting;

ephone-dn  141
number 9940
label OMD Reception-1
name OMD Reception-1
call-forward busy 804
call-forward noan 804 timeout 15
transfer-mode blind

Don't think so it will keep hunting till 9949 as each DN setting has a 'call-forward' if busy and no answer. And based on the setting it should forward to 804 which is the AA. How come this is not doing so? Strangely.

Best regards,

Lawrence Chew

Steven Smith Tue, 07/07/2009 - 07:36

This is working as designed.  You could have ephone-dns forwarded to different numbers and want the hunt group to forward to somewhere else.

Again, the ephone-dn call forwarding doesn't take effect when the call comes in through the hunt group.  You need the final command in the hunt group for this to work.

wfchew2007 Tue, 07/07/2009 - 07:44


So if the call-forward in the ephones are not usable while i am having hunting, how can i divert call if this DN is not answer or busy? I observed the hunting doesn't go to the next in list. Please also advise a method so that i could integrate with AA.

Best regards,

Lawrence Chew

wfchew2007 Tue, 07/07/2009 - 09:17


Seem like the setting under the DNs are not working while in hunting, maybe i could replace the list (9940 - 9949) with (AA) 804 for 10 entries in the hunt.

ephone-hunt 1 sequential
pilot 4999
list 804, 804, 804, 804, 804, 804, 804, 804, 804, 804

The timeout may not work in my environment as, the AA suppose to attend to the caller when busy or no answer. Not until the end of the hunting which could be too long for the caller.

So if there are incoming, it will goes into the first 804 and subsequent will go thru the list which is also 804. When assistant option is pressed during AA, then it will be diverted to receptionist for further process. This could be the workaround for now on.

In my CUE, i have already defined of 24 session for the AA. I think this is sufficient to handle during peak.

Best regards,

Lawrence Chew

Steven Smith Tue, 07/07/2009 - 09:47

You wouldn't need a hunt group at all for call to go to AA.  CUE can handle several AA calls all at once.

If you would like to learn more about how hunt-groups work and how to configure them, read this link.

You might want a blast group that rings everyone at once and then goes to AA after a timeout.

wfchew2007 Wed, 07/08/2009 - 06:55

Hi Steven,

Thank you so far your efforts in this matter. I really appreciate it !!

Could you send me a link or document on how to setup call handling directly into AA? I am going back to my customer tomorrow on this matter. Thanks a lot !!:)

Best regards,

Lawrence Chew

Steven Smith Wed, 07/08/2009 - 08:52

Which dial peer are you expecting to use for the AA calls?

I see that you have some translation profiles in as.  Here is an idea of how you can make this work.

voice translation-rule 1000
rule 1 /5551212/ /840/

voice translation-profile AA_Profile
translate called 1000

dial-peer voice 1000 pots
translation-profile incoming AA_Profile
codec g711ulaw
incoming called-number 5551212

port 0/0/1:15

In this example, 5551212 gets translated to 840, which is your AA.

More info on translations can be found here.

wfchew2007 Wed, 07/08/2009 - 09:07

Hi Steven,

The main line 9999 is translated to 4999, which is the hunt-pilot. The AA is 804. What is 2001 in your example?

Best regards,

Lawrence Chew

Steven Smith Wed, 07/08/2009 - 09:10

I have updated this to be correct.  2001 was not correct.  Sorry for the confusion.


This Discussion