<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>There
was something that I have been thinking about for a while now that might help
with your problem.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>CUCM
6.x has a new feature that will let you have a SPEED DIAL BLF. This is great as
it matches features on old key systems that people depend on. Its always been a
source of frustration for me during implementation.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Lets
say your park range is 10 digits wide. (160X) Could you setup 10 speed dials on
a sidecar that would be to each number in this range, then configure presence
groups to monitor the status of the directory numbers.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>While
that work? I don’t know as I kinda think that CUCM wants to monitor the
physical state of the end device and since the park numbers are all software it
might not.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>That’s
the closest thing I can think of that would solve your issue. If it doesn’t
then I best thing I can think of is fully waying the end-user experience of
moving from CME to CUCM. It’s quite a change.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Voice Noob<br>
<b>Sent:</b> Friday, February 22, 2008 2:46 PM<br>
<b>To:</b> Jeff Mottishaw<br>
<b>Cc:</b> cisco-voip@puck.nether.net; Vince Loschiavo<br>
<b>Subject:</b> Re: [cisco-voip] Call Park Monitoring<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>Looks like you "should" have kept CME. They are
two diffrent systems aimed at two diffrent markets.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Directed call park is something
that has been added to 6.x but I have not implemented it. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>On Fri, Feb 22, 2008 at 2:41 PM, Jeff Mottishaw <<a
href="mailto:mottie@gmail.com">mottie@gmail.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>Yes I agree that she "should" be using the
Attendant Console; however,<br>
she wants full functionality on her phone without having to worry<br>
about her computer, so that's what I need to implement.<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
On Fri, Feb 22, 2008 at 12:35 PM, Vince Loschiavo<br>
<<a href="mailto:VLoschiavo@data-corporation.com">VLoschiavo@data-corporation.com</a>>
wrote:<br>
> hmmm....<br>
><br>
> You are talking about "Directed call park"...<br>
><br>
> Not sure how to set that up in CCM6.x, but the proper way to monitor
parked calls or any call for that matter (for the receptionist or power users)
is through the Attendant Console.<br>
><br>
><br>
> ____________________________________________________________<br>
> Vincent Loschiavo<br>
> Cisco Practice Director<br>
> Datacorp<br>
> 18503 Pines Blvd<br>
> Suite 213<br>
> Pembroke Pines, FL, 33029<br>
><br>
> "Cisco Advanced Unified Communications Partner"<br>
> Cell Phone: 786-282-1164<br>
> Office Phone: 954-671-5669<br>
> Office Main: 305-594-6933<br>
> ____________________________________________________________<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Jeff Mottishaw<br>
> Sent: Friday, February 22, 2008 3:25 PM<br>
> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: [cisco-voip] Call Park Monitoring<br>
><br>
> We have just migrated from CME to UCM6.0 and I need some configuration
assistance. In CME we used the "park-slot" option, which allowed the
receptionist to monitor parked calls on her 7960/7914 and see where calls are
being parked.<br>
><br>
> Can someone please help me duplicate this functionality in UCM6? In the
release notes for CallManager I found the info below, which appears to tell me
that it is a possibility.<br>
><br>
> The Call Park feature allows users to park a call to a specific park slot.
Users now also can have a busy-lamp-field (BLF) and speed-dial button that
tells them whether or not the park slot is available. The feature is easily
invoked by performing a transfer to the park slot.<br>
><br>
> Thanks in advance.<br>
><br>
> jeff<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<DIV><P><HR>
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
</P></DIV>
</body>
</html>