[cisco-voip] Call Park Issue
Ryan Ratliff
rratliff at cisco.com
Fri Dec 17 10:57:54 EST 2010
Once the new behavior was out there it was the new default. Changing the default value of this parameter would change the behavior for someone that installed new on 7.x and then upgraded to add this parameter.
-Ryan
On Dec 16, 2010, at 9:33 PM, Lelio Fulgenzi wrote:
thanks for this everyone, we would have run into issues with this one. will put it on the list to check after the migration.
however, i always understood that if a new service parameter was ever added, it's default would be the one that made the less impact or not change behaviour. why would this parameter not be true by default?
Use All Call Park Numbers Once Before Reusing:This parameter determines whether all available call park numbers in the range must be used at least once before any call park number can be reused. For example, if this parameter is set to False and you have configured 10 call park numbers in a partition, all 10 numbers must have held a parked call (even if the call at any or all of the numbers has already been retrieved or reverted) before Unified CM will reuse a number in the call park range.
Valid values specify True (a call park number will not be reused for a new parked call until all other available call park numbers have been used) or False (a call park number can be reused as soon as the parked call has been picked up or reverts back to the parking party).
This is a required field.
Default: False
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
From: "Ryan Ratliff" <rratliff at cisco.com>
To: "Jason Aarons (US)" <jason.aarons at us.didata.com>
Cc: "Cisco VoIPoE List" <cisco-voip at puck.nether.net>
Sent: Thursday, December 16, 2010 8:06:09 PM
Subject: Re: [cisco-voip] Call Park Issue
My bug in fact, CSCtc77181. There is a service parameter to control the behavior but even with it set to true (non default) it isn't 100% exactly like what 6.x and earlier did.
Don't have a CUCM in front of me to verify but I think if you look for Park with the advanced parameters enabled you'll find it.
-Ryan
On Dec 16, 2010, at 5:41 PM, Jason Aarons (US) wrote:
CallManager 7 release notes discusses the Call Park algorithm changes to always re-use the lowest available number, which I think it bad. 4x always incremented the CallPark number with each park. I suspect your seeing this.
There is a bug id, I'd like to see a service parameter where you could set behavior. If you could change the behavior you would know, otherwise you can only attempt to reproduce the problem then gather traces when it occurs.
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mike King
Sent: Thursday, December 16, 2010 5:10 PM
To: Cisco VoIPoE List
Subject: [cisco-voip] Call Park Issue
I seem to have in an issue with Call Park. I've had several users reporting the following scenario:
Caller A receives call. Caller A parks call (get's park number of
1120) and yells down hall to Caller B to pickup on 1120 Caller B dials 1120 and Get's Caller C's Call. Caller A's call is gone.
The first few time's I've attributed it to Caller A's caller hung up, and Caller C parked the call there.
But it's happening too regularly (of course not every single time, otherwise it would be easy to fix) to continue discounting. Also I've personally witnessed the above scenario, and it all happened in about 10 seconds. I don't think the caller would have hung up, and another call been parked in that amount of time.
We usually only have 1 or 2 calls parked at once.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101217/8327d503/attachment.html>
More information about the cisco-voip
mailing list