Preview Tool

Cisco Bug: CSCun40512 - Cannot view and retrieve parked calls

Last Modified

Nov 27, 2020

Products (1)

  • Cisco Unified Attendant Consoles

Known Affected Releases


Description (partial)

After a call is parked in CUAC 10, call disappears from the GUI and can only be retrieved after the Park timeout timer is met. 

After further analysis traces confirm that the CUACS application is not getting a required LINE_CALLSTATE event from TSP and as a result the application is unable to show the parked call in Parked Calls area. This is tied to an overlap in call park device ranges across partitions (those assigned to operator and others, entire CUCM).

Issue appears if there is an overlap in the call park DNs/range across partitions. This spans outside of the CSS associated with operator devices due to operators having the ability to view all park devices. 

- Create 2 or more partitions with overlapping park ranges
- Create a CSS with the partition from above that falls last alphabetically. (For instance if you created SiteA and SiteB, specify SiteB in the CSS being created)
- Specify the CSS from above as the CSS of your operator device

Reproducing Issue
- Login to application and park any call.

After which, you'll recreate the issue every time you attempt a call park. Further confirmation, if you go back into your CSS Partitions and eliminate the overlap the issue dissipates. 

You may notice that if you were to have associated the alphabetically 1st partition to the CSS that the issue does not appear. This is because the subscription of the park devices is based on an alphabetical ordering, but will only subscribe 1 device (the reason this is a defect).

Related Community Discussions

CU Attendant Console Standard 12 Call Park
Had a question about a newly deployed CUAC.  When they park the call, it is disappearing from the console and the only way they can see which slots it's parked on is to go to the phone.  Is that by design?
Latest activity: Aug 03, 2018
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.