Call Park does not work.

[james.techsavvy]

Hello All,

We have a problem with call parking in our CUCM environment. When trying to park a call, phone displays " No Park Number available ", call park numbers are configured though.

This is affecting multiple sites under the same cluster.

++James.

[kusatija · Accepted solution]

Hi James,

How many servers are there in the cluster?

So lets say an attendant pressed the Park softkey:

so basically when the attendant presses the park 
softkey the phone would look for the park range defined for the call manager
to which the phone(or the end point gateway etc) which made the call to the attendant.

So determine the Park range for the server to which the end point through which the call is coming in, and
add the partition associated to this range to the attendant phone.

You should not have any issues if you apply this logic.

HTH
Kunal

[David Hailey · Accepted solution]

To expand/clarify on what Kunal is saying, the call park number used is based on the range defined for the CUCM server to which the phone that invokes call park is registered.  For example, you have Pub and Sub and you have defined a call park range for the Pub.  Your phone is registered to the Sub and you invoke call park...this will fail.  You typically define a range for all potential call processing hosts (active or backup) in the cluster.

Hailey

Please rate helpful posts!

[james.techsavvy]

Thanks guys for the insight!

I verified the CCM group for the DP and the Park number range and they are configured with different groups

I am yet to get approval to change the group of the Park number range so we can check it...

Will update you once I check it.

Thanks again!

++James.

[james.techsavvy]

Guys,

The issue has been fixed. The call park range was assigned a CCM that was not a member of the CCM group for the DP and the phones.

I changed the Call manager to the primary server in the group and it started working.

Fanks,

++James.

[srsivara]

Hi James,

The call park behavior is explained in the following documentation defect :

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsl70911

The latest documents should explain how Call Park is handled in CallManager.

- Sriram