[cisco-voip] UCM linegroup hunting algorithm for voicemail ports?

[Lelio Fulgenzi]

We use top down. The final destination is a backup autoattendant/VM app that tells people that VM is unavailable. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Wes Sisk" <wsisk at cisco.com> 
To: "cisco-voip at puck-nether.net" <cisco-voip at puck.nether.net> 
Sent: Monday, August 31, 2009 11:40:09 AM GMT -05:00 US/Canada Eastern 
Subject: [cisco-voip] UCM linegroup hunting algorithm for voicemail ports? 

Wondering what call distribution algorithm most people use on the 
linegroups in UCM for Unity and Unity Connection ports. 

We recently found a few major accounts using "Longest Idle" hunting 
algorithm on the line groups. That algorithm ignores the configured busy 
treatment on the linegroup. This causes CM to send calls to the 
linegroup for failover Unity server when all members of the primarly 
linegroup are busy. Asterisks and fineprint on the page indicate this 
is designed behavior: 

Hunt Options: 
Busy** 
... 
Fields marked with a ** are required when the Distribution Algorithm is 
set to Top Down or Circular, and are not used when the Distribution 
Algorithm is set to Longest Idle or Broadcast. The No Answer setting is 
used for Longest Idle and Broadcast. 


I suspect the combination of "Longest Idle" as the default and this 
limitation lead to several undiagnosed unexpected Unity failovers. 

/Wes 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090831/1088a55b/attachment.html>