You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When performing a reload after the res_parking.conf file has been touched, I notice that BLFs on some phones stop working for a bit - Turns out, Asterisk is deactivating watchers in the middle of a reload of res_parking.
The desired behavior would be for the subscriptions to be kept, if at all possible, so users don't have to wait for the next SUBSCRIBE cycle.
Steps to reproduce: Set up a parking lot configuration, subscribe a phone or two to some of the lots, then perform a core reload after touching res_parking.
But it's strange, the CLI doesn't show that error when I've got debug set to 5 for the core.
I do see a bunch of these, which may be inconsequential: [Feb 27 21:24:05] DEBUG[35886]: pbx.c:8224 __ast_context_destroy: Couldn't delete ctx vm-4b3bf86c-1c5a-492c-a793-ebdce8c65971-check/pbx_config; refc=1; tmp.root=0x7fef75f6dd70 [Feb 27 21:24:05] DEBUG[35886]: pbx.c:8113 __ast_context_destroy: Investigate ctx vm-4ad689b2-f509-4d77-9aab-9919f4c885ce-check pbx_config
Severity
Major
Versions
20.6.0
Components/Modules
res_parking
Operating Environment
Debian 12 x64
Frequency of Occurrence
Constant
Issue Description
When performing a reload after the res_parking.conf file has been touched, I notice that BLFs on some phones stop working for a bit - Turns out, Asterisk is deactivating watchers in the middle of a reload of res_parking.
The desired behavior would be for the subscriptions to be kept, if at all possible, so users don't have to wait for the next SUBSCRIBE cycle.
Steps to reproduce: Set up a parking lot configuration, subscribe a phone or two to some of the lots, then perform a core reload after touching res_parking.
Relevant log output
Asterisk Issue Guidelines
The text was updated successfully, but these errors were encountered: