Core Issue
The issue is that when a call is parked by an IP phone, once the call retrieval timer expires, it is received by a different member on the hunt list. This is because when the call comes to hunt pilot 5001, the final called party for the call becomes 5001. Now, when another IP phone answers the call and parks it, the park feature records 5001as the number to which the call is reverted when the retrieval timer expires. This behavior is normal for a Route Plan > Route/Hunt > Hunt Group/List configuration of the Attendant Console (AC). This configuration causes the parked call to reach the next available member in the hunt list or group, and explains the behavior observed in the environment.
Resolution
The Parked Calls window in the AC application only works correctly with a pure AC configuration (such as Service > Cisco CallManager Attendant Console > Pilot/Hunt Group). A pure AC configuration supports broadcast hunting, correct park monitoring and retrieval of parked calls to the member/attendant who placed the call on park. To resolve this issue, a pure AC configuration is required. For more information on Parked Calls Window, refer to: Parked Calls Window.
Problem Type
Call control software (CallManager, CallManager Express, ICS7750, SRST, SS7 call agents)
Voice applications (CRS, PA, CCM Plugins, CER, CCC, MeetingPlace, etc.)
Call Control
CallManager
CallManager Features
Supplementary services (Transfer, hold,forward, park, pickup, conference, callback, call waiting)
Failure Type
Bad operational behavior
Nothing displays: Not displayed, generated, created, etc.
CallManager Versions
CallManager 4.0
CallManager 4.1
Supplementary Services
Call park
User Interfaces
Graphical user interface (GUI)
Voice Applications
CallManager attendant console
