[cisco-voip] Call Park Monitoring

[Frazee, Timothy]

There was something that I have been thinking about for a while now that
might help with your problem.

 

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.

 

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.

 

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.

 

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.

 

 

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Voice Noob
Sent: Friday, February 22, 2008 2:46 PM
To: Jeff Mottishaw
Cc: cisco-voip at puck.nether.net; Vince Loschiavo
Subject: Re: [cisco-voip] Call Park Monitoring

 

Looks like you "should" have kept CME. They are two diffrent systems
aimed at two diffrent markets.

 

Directed call park is something that has been added to 6.x but I have
not implemented it. 

On Fri, Feb 22, 2008 at 2:41 PM, Jeff Mottishaw <mottie at gmail.com>
wrote:

Yes I agree that she "should" be using the Attendant Console; however,
she wants full functionality on her phone without having to worry
about her computer, so that's what I need to implement.


On Fri, Feb 22, 2008 at 12:35 PM, Vince Loschiavo
<VLoschiavo at data-corporation.com> wrote:
> hmmm....
>
> You are talking about "Directed call park"...
>
> 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.
>
>
> ____________________________________________________________
> Vincent Loschiavo
> Cisco Practice Director
> Datacorp
> 18503 Pines Blvd
> Suite 213
> Pembroke Pines, FL, 33029
>
> "Cisco Advanced Unified Communications Partner"
> Cell Phone:       786-282-1164
> Office Phone:    954-671-5669
> Office Main:      305-594-6933
> ____________________________________________________________
>
>
>
>
>
>
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jeff Mottishaw
> Sent: Friday, February 22, 2008 3:25 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] Call Park Monitoring
>
> 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.
>
> 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.
>
> 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.
>
> Thanks in advance.
>
> jeff
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 



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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080223/5e5aa8af/attachment.html