<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Anything is possible with sufficient motivation. Currently I am not
aware of any planned changes.<br>
<br>
/Wes<br>
<br>
On Thursday, October 08, 2009 4:37:07 PM, Tim Frazee
<a class="moz-txt-link-rfc2396E" href="mailto:tfrazee@gmail.com"><tfrazee@gmail.com></a> wrote:<br>
<blockquote
cite="mid:30ce418a0910081337g3316f8abs866d9362046ddfec@mail.gmail.com"
type="cite">I agree.<br>
<br>
but, one nice thing about the round robin approach was if you kept
re-parking the call, it kept the same park slot. sounds like that was
just a side-effect of how the code was.<br>
<br>
so, is it safe to say that in CUCM 7.x and future that park slot
allocation will be top down instead of round robin? It would be nice to
have a toggle for this? (hell, theres toggles for everything else... :)<br>
<br>
<div class="gmail_quote">On Thu, Oct 8, 2009 at 9:31 AM, Wes Sisk <span
dir="ltr"><<a moz-do-not-send="true" href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">we've seen a few cases about
this. there was nothing in the original
feature design that required the selection order. When In Memory
Database (IMDB) was implemented in CM7.x (woo hooo! less dependence on
informix realtime access) the change in selection order was a
byproduct. As there was no previous requirement for selection order it
was hard(impossible) to call this "breakage".<br>
<br>
/Wes
<div>
<div class="h5"><br>
<br>
On Thursday, October 08, 2009 9:17:26 AM, Tim Frazee
<a moz-do-not-send="true" href="mailto:tfrazee@gmail.com"
target="_blank"><tfrazee@gmail.com></a> wrote:<br>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">Group,<br>
<br>
I am running 7.1.2.31900 PUB/SUB setup and I noticed a difference in
park behavior that I'm ok with, but curious as to why its different and
how to change if I wanted to.<br>
<br>
As far as I can remember, when you parked a call and your park range
was (for example) 702X, it would use a round-robin method of number
allocation. It would always choose the next number in the range
regardless of the state of the previous park numbers.<br>
<br>
Now the behaviour is top down. It chooses the first number in the range
if its available. If I repark a call, it gets a different park slot
than it had before This is different than I remember the all of
Callmanager versions operation.<br>
</div>
</div>
<pre><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a>
<a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</blockquote>
<br>
</body>
</html>