Jump to content

Trunk gets automatically blocked with Timeout 408


Recommended Posts

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 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.

Link to comment
Share on other sites

  • 2 weeks later...

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.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...