chrispopp Posted February 11, 2019 Report Share Posted February 11, 2019 Was testing creating a trunk between two systems. The main system has an extension created. On the second system, the extension was registered as a trunk. After a while, the trunk gets a 408 Timeout error. Seems the main pbx does not respond back. I then went to the Access tab, and it shows the registration as blocked 0.0.0.0/0. I remove it, and then it gets blocked again. I whitelisted the IP, and although it doesn't show up as blocked anymore, it still shows up as 408 error. Noticed this in the release notes: SBC: The new SBC algorithm could accidentally block trunk IP addresses. The PB now keeps a separate list for those addresses to avoid the problem. Only thing is that this is a fix in 62.0.1, and I was testing with 62.0.3. Quote Link to comment Share on other sites More sharing options...
Support Posted February 11, 2019 Report Share Posted February 11, 2019 Hi Christof, We are aware of this issue and are currently engaged with it. We will update this thread ASAP. We have 62.1 right now, if you'd like to give that a go. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 12, 2019 Report Share Posted February 12, 2019 It seems that this issue was found and fixed on the latest 62.1 build. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted February 25, 2019 Author Report Share Posted February 25, 2019 Tried it with the latest build. Same. I even swapped the trunk to an Asterisk server to test. After a few days, 408 again. So it doesn't seem to be a Vodia to Vodia issue, but a trunk issue instead on the actual PBX. Whitelisting the IP doesn't do any help either. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 25, 2019 Report Share Posted February 25, 2019 Hmm, did you also explicitly list the addresses for the trunk? In the access list you should see in the comment column the name of the trunk - that would be the indication that the PBX has added that address for the trunk. If you do a trunk-trunk you need to do that on both systems. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted February 25, 2019 Author Report Share Posted February 25, 2019 I did not use that before. But it's really curious that it does this, when I've tested it multiple times, and it always worked. I added it and I'll wait to see if it changes... Quote Link to comment Share on other sites More sharing options...
chrispopp Posted March 1, 2019 Author Report Share Posted March 1, 2019 I used it and now I got a 401 error now. Quote Link to comment Share on other sites More sharing options...
Vodia support Posted March 1, 2019 Report Share Posted March 1, 2019 If the PBX received the 401 auth from the trunk side, then you'll need to check the password on the trunk settings. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted March 1, 2019 Author Report Share Posted March 1, 2019 It was working for almost a week... 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.