line grp fwd settings for unity failover

Unanswered Question
Oct 20th, 2009
User Badges:

we have a unity prim/sec config. our vm01 line grp fwd busy is set to "try next member, then try next grp".

is this recommeded setting? today, we had a failover becasue a=of an all port busy condition.

i would think "try next member, do not try next grp" would be better since it will not activate a failover under a heavy traffic load.

is there any downside to it?

what are pros/cons of each?



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
testeven Tue, 10/20/2009 - 14:44
User Badges:
  • Cisco Employee,


The settings for the line group configuration are described on this doc:

If the ports on the Primary server are busy, you need to use the " Try Next Member, but Do Not Go to Next Group" option.

It will be different if the ports on the Primary are not available (i.e. unregistered for example), therefore, you will need to select

"Skip Remaining Members, and Go Directly to Next Group". Unity will do a failover when a call comes in on a secondary VM port.

So if you leave it the way it is, you will failover once again when all the primary ports are busy.



If you find this post helpful, please rate! :)

rvincent Tue, 10/20/2009 - 15:39
User Badges:


thanks for the info.

is there any downside to using the 'try next member, but do not go to next group" setting?


Tray Stoutmeyer Wed, 10/21/2009 - 06:33
User Badges:
  • Cisco Employee,

If you choose "do not go to next group" on the primary LG, failover won't work. It will never go to the secondary line group causing the failover to trigger. It will basically kill the functionality.


testeven Wed, 10/21/2009 - 07:21
User Badges:
  • Cisco Employee,

But you should use it when all the ports are busy, otherwise you will cause an unnecessary failove. This is docuemnted on the link above.




This Discussion