Line Group member can't receive call in on-hook status

Unanswered Question
Feb 19th, 2007

CM is running 4.1(3)SR4b, a hunt pilot have a line group that have 15 members.

Several members of the line group cannot receive on-net / off-net call enen the phones are onhook. Replaced phone did not solve the issue.

I find out the "forward max. hops to DN " is 12 in service parameters. Does it means the line group can only hold 12 members. Can I change this figure to 15 to solve this issue?

Your reply will be appreciated.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
rob.huffman Mon, 02/19/2007 - 08:51

Hi Michael,

This is probably the issue you are running into. You should bump up the "Forward Maximum Hop Count" to at least 15. Have a look;

Setting the Hop Count

You can specify the number of times Cisco CallManager forwards a call before generating an error tone. The default setting is 12, but you should set it to a number larger than the number of extensions in the largest hunt group.

To configure the hop count perform the following steps:


Step 1 Select Service > Service Parameters menu from Cisco CallManager.

Step 2 Click the name of your Cisco CallManager system.

Step 3 Select the ForwardMaximumHopCount service parameter.

Step 4 Enter the maximum number of hops required in the Value field.

***Use in conjunction with this timer;

Maximum Hunt Timer

Enter a value (in seconds) that specifies the maximum time for hunting. Valid values specify 1 to 3600. The default value specifies 1800 seconds (30 minutes).

This timer cancels if either a hunt member answers the call or if the hunt list gets exhausted before the timer expires. If you do not specify a value for this timer, hunting continues until a hunt member answers or hunting exhausts. If neither event takes place, hunting continues for 30 minutes, after which the call gets taken for final treatment.

***Note: If hunting exceeds the number of hops that the Forward Maximum Hop Count service parameter specifies, hunting expires before the 30-minute maximum hunt timer value and the caller receives a reorder tone.

From this doc;

Hope this helps!


daljeetsingh1_2 Mon, 02/19/2007 - 08:54


when u click on the parameter u will see..

This parameter specifies the maximum number of times that a single internal or Q.SIG call can be diverted. Both internal and Q.SIG call diversions are counted equivalently. Cisco CallManager terminates the call if the number of hops specified in this parameter is exceeded and the final destination is not available (for example, busy or not registered). Cisco CallManager allows the call to ring until the T301 Timer expires if the number of hops specified in this parameter is exceeded and the final destination is available but not answering.

This is a required field

Which i dont think is for this parameter. As i never did this way. You can increase the parameter as it will not going to break anything..

How many memebers are recieving the calls? is it really specific 12? than we can tweek the setting and see..


This Discussion