PBXact Ignoring phones on a specific subnet and therefore they cannot register

FreePBX Endpoints
1

I have verified that it is not a network issue, the phones are on the right subnet (10.200.0.xx) with DNS settings and everything.

On the PBX server, I can see the incoming message from the phone in sngrep, but the PBX simply never responds.

Turned off intrusion detection (fail2ban), no change. Turned off the firewall, no change. Phone on all my other subnets work just fine. Verified that this subnet is on the local trusted side of things in fail2ban and the firewall. Still nothing.

The phones are yelling into the void it would seem.

Sangoma support seems to be equally baffled.

Anyone seen this before? Any suggestions on what to look for here?

2

Did you open a support case? If so, please share the case number so I can take a look.

Thanks!

3

Not one specific to this issue, but there is a general one for our new deployment, which we are working up to, and the drop dead date is the 21st.

I’ll PM you the case number I do have.

1 Like
4

For the record, and thanks to @slobera for the help. Essentially Sangoma’s customer support VPN uses the same subnet as my phones (10.200.xx.yy) and therefore when the tunnel was up, Sangoma’s routes trampled on mine and the PBXs response to the phone was going out the wrong end and into the void.

Once we disconnected the tunnel and verified the routes were cleaned up, the phones started registering without issue.

5

Thanks for the feedback @Lutiana
Glad it’s working now!

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.