-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Channel Teardown Error Leaves Stuck Traffic Channels in Now Playing #1508
Comments
#1506 resolves source that was causing channel teardown issues. However, there still needs to be a way to manually teardown a hung traffic channel. |
I'm on 5.0.3 and had this happen again today. I had this error in my log but I have no idea when this happened so I don't know if it's related or not, sorry.
|
In 0.5.0 and 0.5.2 I can clear hungup calls (STATUS has black background) by closing that Channel and restarting it. P25, Windows. |
I am still getting this issue in 0.6.0 beta 5 on a p25 phase 2 trunked system I have all logs saved from the most recent time this happended and can provide any helpful info. I am able to resolve it by restarting the channel under the playlist editor. I have at points had it happen with multiple channels leading to 2 or 3 (6 total time slots) frequencies being left in teardown. |
Issue resolved with #1802. If this issue is still happening with version 0.6.1 or later, there is a new menu option (File >> Reports >> Create Diagnostic that will capture the information I need to diagnose what's causing your channels to be stuck in TEARDOWN state. Please create a new issue and attach that report to the issue. |
When an error occurs during shutdown of a traffic channel, that channel remains in the Now Playing table and the user has no options (other than restart) to clean out the traffic channel.
Add right-click context menu item to allow the user to remove the offending entry. More than likely the traffic channel backing the table row no longer exists, but at least the UI cleanup can happen.
The text was updated successfully, but these errors were encountered: