<!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">
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<br>
<br>
On Thursday, October 08, 2009 9:17:26 AM, Tim Frazee
<a class="moz-txt-link-rfc2396E" href="mailto:tfrazee@gmail.com"><tfrazee@gmail.com></a> wrote:<br>
<blockquote
cite="mid:30ce418a0910080617l185b9852r1bd9e95c0e294c41@mail.gmail.com"
type="cite">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>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>