Question:  I have an Eclipse Median frame running ECS 5.1.3, on one panel the user is complaining of a crosspoint routed to his panel that he cannot disable.  How do I resolve the "ghost" crosspoint in ECS?

Answer:  Look in ECS in the following places to determine if an unwanted crosspoint (source to destination) exists in the system.  First determine what the source signal identity or port is.  Second, determine the destination port of the spurious source signal. This will allow us to determine how to proceed with resolving the issue. 
In ECS go to the diagnostic menu and open the crosspoint map screenThis screen provides a real time crosspoint map which shows the user all active talk, listen, forced listens, blocked listens and auto listens currently active within the Eclipse frame.  The left hand side of the screen shows inputs (sources) the top row shows outputs (destinations). By using the port names (numbers) for the source and destination the user can track and see any active crosspoints in the system. The user can right button mouse click on a crosspoint between a input & output and toggle it on/off or select to KILL the active crosspoint.
In ECS go to Configuration > local advanced > forced listen tab to determine if a forced crosspoint was made from the source to destination.  A red dot indicates an enabled forced listen.
Open the Party-Line screen in ECS and verify that no panels are listed as permanent members of any party-line.  If a panel is listed as a permanent member then it has no way to disable the party-line audio to that panel.
Open the hardware > card & ports screen (Matrix hardware) highlight the port receiving the "ghost" audio.In the advance settings (on the right side of the screen). Check that there are no un-wanted settings like secondary actions, vox actions, eavesdropping (set true) or auto listen (set true)
After checking the above options and no obvious crosspoint can be found in the system perform a Clear-frame data download (Black Reset) to the frame, this will dump out any spurious crosspoints on the frame as all active listens, active talks will be reset to their inactive state after the reset is completed at the frame and the CPU cards are back online. Select Apply changes > options > select Clear frame data check box
Another possible cause of a forced crosspoint can be hardware related, that is a panel with a broken lever key or non-working led for the talk or listen activation.