8811 call Park featire

[miket]

I am using an 8811 and when I place a call on park , the Parked call stays on the 8811 (phone). I can pick the call using the parked extension so it looks like the feature works however I have never seen the Parked call stay on the Phone that parked it. CUCM is version 10.5.

Any thoughyts 

[Rob Huffman · Accepted solution]

Hi Mike,

It sounds like this bug/enhancement;

Change the way 88xx series phone park a call

CSCuy32083

Symptom:
When park feature is used on 88xx series phone, the call will be displaying on the phone and it will consume 1 max call parameter.

Each Call Park will utilize one logical line, but also uses one of the 5 available buttons.

The 79XX type phones do NOT have this limitation. when Call Park is initiated the Park is placed back to the server, disappear from the phone display and does not occupy the max lines.

This is working as design for the 88xx devices.

This is an enhancement request to have the 88xx devices to work as the 79xx when parking a call.

Conditions:
88xx series phone using call park feature

[Jitender Bhandari]

+5 Rob 

Also see 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCux68138/?reffering_site=dumpcr

JB

[miket]

Thank You for taking time to reply...

[Jitender Bhandari]

Happy to help

[miket]

Thanks Rob.. I was just going thru the release notes to see if it was an bug or working as designed.

Thanks for answering so fast.

Mike

[Aaron Fracht-Monroe]

Hello, the bugs CSCux68138 was recently listed as resolved, but we still see the issue with CUCM 12.5(1), & 8800 firmware 12.5(1).  Has anyone been able to confirm if this is actually fixed and parked calls no longer consume the slot on the phone?

[Aaron Fracht-Monroe]

Hello @Jitender Bhandari , 

I see this bug (CSCuy32083) has been marked as resolved/closed as resolved with the 12.8.1.1.438 firmware. I've just tested the scenario out again with the new firmware on CUCM 12.5.1.11900 and we see the same results as we've seen since CUCM 11.x w/ 8800 series phones.

Is there a setting or feature that needs to be enabled in the new firmware to resolve the issue?