bayden10 Posted February 25, 2022 Report Share Posted February 25, 2022 Hi, PBX Ver. 68.0.10 (Debian64), within UI deleted all extensions & tenants (approx 6) that had trunks. This PBX now has no tenants or extensions. PBX was rebooted and DNS cache was flushed at CLI and PBX reload DNS. It is visible that the trunks are still active and attempting to connect to Peer from Provider within logs. [1] 12:05:22.366 Adding DNS server 8.8.8.8 to the dns server listⓘ [1] 12:05:22.419 Starting up version 68.0.10ⓘ [1] 12:05:22.480 Working Directory is /usr/local/pbxⓘ [5] 12:05:23.075 Starting threadsⓘ [5] 12:05:23.078 Set scheduling priority to 1ⓘ [5] 12:05:23.078 Set process affinity to 1ⓘ [4] 12:05:23.089 Join multicast group on address 0.0.0.0ⓘ [5] 12:05:23.362 Registration on trunk 50 (Provider9) failed with code 403. Retry in 60 secondsⓘ [2] 12:05:23.362 Trunk status Provider9 (50) changed to "403 Forbidden" (Registration failed, retry after 60 seconds)ⓘ [5] 12:05:23.363 Registration on trunk 51 (Provider9) failed with code 403. Retry in 60 secondsⓘ [2] 12:05:23.363 Trunk status Provider9 (51) changed to "403 Forbidden" (Registration failed, retry after 60 seconds)ⓘ [5] 12:06:23.435 Registration on trunk 50 (Provider9) failed with code 403. Retry in 60 secondsⓘ [5] 12:06:23.437 Registration on trunk 51 (Provider9) failed with code 403. Retry in 60 secondsⓘ 2 trunks still exist here /usr/local/pbx/trunks/ 50.xml, 51.xml I tried to manually delete them but they keep returning after 1min. Any idea where this would be cached and how this can be resolved? Quote Link to comment Share on other sites More sharing options...
bayden10 Posted March 6, 2022 Author Report Share Posted March 6, 2022 After destroying the PBX and creating new was the only resolve. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 7, 2022 Report Share Posted March 7, 2022 There must be something else. We tested deleting the trunk itself and also deleting the whole tenant and it all looked alright. If the XML still exists, then the trunk were really not deleted. Maybe there is a permission problem, e.g. the tenant administrator does not have the permission? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.