[cisco-voip] Call Park Partition

[Lelio Fulgenzi]

I am pretty sure that it selects a park number in a circular format. It goes through the entire list of available park numbers before starting at the top of the list again.

It am also pretty sure that it selects the park number from a range of park numbers assigned to the subscriber on which the calling party is registered to. We had a problem where users couldn't park calls from callers which were registered to a subscriber which had no park ranges assigned. When I added those ranges, everything worked again.

  ----- Original Message ----- 
  From: King, Jesse 
  To: Lelio Fulgenzi ; cisco-voip at puck.nether.net 
  Sent: Wednesday, March 09, 2005 11:39 AM
  Subject: RE: [cisco-voip] Call Park Partition


  Makes sense. I agree with the none partition...

  Can anyone explain how CM chooses a park number? Does it search through the CSS of the DN, and grab the first available park number in the CSS list? An example would be if I have a CSS with 4 partitions - Part 1, Part 2, Part 3, Part 4, and 2 call park ranges in Part 2 and Part 4.  If my css is ordered Part 1,2,3,4, would it always grab a park number in Part 2 vs Part 4? 

  I experimented and got mixed results...





------------------------------------------------------------------------------
  From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
  Sent: Wednesday, March 09, 2005 11:15 AM
  To: cisco-voip at puck.nether.net
  Subject: Re: [cisco-voip] Call Park Partition


  Speaking from experience, I would do my best to not put any numbers in the <none> partition. There is no way to restrict access to these numbers other than putting in specific block patterns to match. It's not so much a usage restriction, but technical. For example, if you want to create a ringdown phone to go to the PSTN, you'll have to block all numbers in the none partition, or it won't act much like a pstn line. There are others.

  We've create a large range of park numbers in one partition registered to several servers without many problems. We were running 3.3.3sr4 when we did it, and are now running 3.3.4sr2. We will be upgrading to 4.1.2sr1 at the end of April.

    ----- Original Message ----- 
    From: King, Jesse 
    To: cisco-voip at puck.nether.net 
    Sent: Wednesday, March 09, 2005 11:06 AM
    Subject: [cisco-voip] Call Park Partition


    In an early version of CM 3, I had a call park range setup without a partition and ran into problems. I can't remember what they were, but I believe it was a bug.

    I am running 4.1(2), now and am revisiting call park, because the ranges are getting out of hand (two for each partition - one for each CM server).

    Can anyone tell me a good reason not to have one big call park range (less than 100) in the none partition or my internal_dn partition? other than trying to restrict usage?

    Thanks.

    Jess


----------------------------------------------------------------------------


    _______________________________________________
    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/20050309/51c6632b/attachment.html