The park numbers window works fine in AC for us using the same number in different partitions; at least by my definition of 'work'. If a user parks a call it displays in the AC park window and can be retrieved. The user cannot retreive calls parked by other AC users but that's a function of the CSS on the phone.
<br><br>All of our devices register to the same CTI and CCM server so maybe that's why it works for us. <br><br>In hindsight it probably wasn't the best decision to set it up this way. We plan on implementing a 3rd party console app at some point and the ones I looked at will require unique park ranges at each site so I will probably have to change it eventually.
<br><br><br><div><span class="gmail_quote">On 10/17/06, <b class="gmail_sendername">Wes Sisk</b> <<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">Same numbers in different partitions will work for park/retrieval depending on your CSS. There are some call flows with devices registered to different nodes in a cluster where you will encounter problems. For CTI monitoring of park numbers (Attendant Console, IVR scripting, etc) same park number in different partitions definitely will not work. CTI does not include partition support until
CM5.x and even then I have not seen any CTI clients coded to handle the new support.<div><br></div><div>/Wes</div><div><span class="e" id="q_10e59346ceb98e40_1"><div><br><div><div>On Oct 17, 2006, at 9:20 PM, Kris Seraphine wrote:
</div><br>Strange, it sounds like you were trying to do exactly what I'm doing. I'm not having any problems using the same park number range (in different partititions) at each of 40 + sites. <br><br><div><span class="gmail_quote">
On 10/15/06, <b class="gmail_sendername">Robert Kulagowski</b> <<a href="mailto:bob@smalltime.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">bob@smalltime.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
For anyone that's still interested, it appears that the root cause was<br>that we had configured 16[0-4] on the primary and 16[5-9] on the<br>secondary call manager for each one of our sites (but in different<br>partitions), thinking that we could make our documentation / training
<br>simpler. So every site had a "160" as their first call park number.<br><br>That doesn't work. When I changed our test site to 15[0-4], it started<br>working, so that gave me the clue on where to look further. Now I have
<br>to go back and re-look at how to allocate our park numbers.<br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
cisco-voip@puck.nether.net</a> <br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
<br></blockquote></div><br><br clear="all"><br>-- <br>kris seraphine<div style="margin: 0px;">_______________________________________________</div><div style="margin: 0px;">cisco-voip mailing list</div><div style="margin: 0px;">
<a href="mailto:cisco-voip@puck.nether.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cisco-voip@puck.nether.net</a></div><div style="margin: 0px;"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
https://puck.nether.net/mailman/listinfo/cisco-voip</a></div> </div><br></div></span></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>kris seraphine