<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>We use top down. The final destination is a backup autoattendant/VM app that tells people that VM is unavailable.<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Wes Sisk" <wsisk@cisco.com><br>To: "cisco-voip@puck-nether.net" <cisco-voip@puck.nether.net><br>Sent: Monday, August 31, 2009 11:40:09 AM GMT -05:00 US/Canada Eastern<br>Subject: [cisco-voip] UCM linegroup hunting algorithm for voicemail ports?<br><br>Wondering what call distribution algorithm most people use on the <br>linegroups in UCM for Unity and Unity Connection ports.<br><br>We recently found a few major accounts using "Longest Idle" hunting <br>algorithm on the line groups. That algorithm ignores the configured busy <br>treatment on the linegroup. This causes CM to send calls to the <br>linegroup for failover Unity server when all members of the primarly <br>linegroup are busy. Asterisks and fineprint on the page indicate this <br>is designed behavior:<br><br>Hunt Options:<br>Busy**<br>...<br>Fields marked with a ** are required when the Distribution Algorithm is <br>set to Top Down or Circular, and are not used when the Distribution <br>Algorithm is set to Longest Idle or Broadcast. The No Answer setting is <br>used for Longest Idle and Broadcast.<br><br><br>I suspect the combination of "Longest Idle" as the default and this <br>limitation lead to several undiagnosed unexpected Unity failovers.<br><br>/Wes<br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>