Zero Configuration not working with Sangoma P315 and VLAN on Netgear

Sangoma Hardware Phones
1

Running V17.

  1. Zero config works fine if only using the default VLAN 1.
  2. When creating a Voice VLAN on Netgear Switch, Zero Config fails.
  3. Tried different VLAN discovery options in the template for items 4 and 5 with no change.
  4. If voice VLAN switch it turned on in the Netgear switch, the phone gets DHCP from the Voice VLAN but is not communicating on the LAN, i.e. cannot ping it and it does not see my FreePBX server on that subnet.
  5. If voice VLAN switch is turned off on the Netgear switch, the phone gets DHCP from the Default VLAN 1 but never reboots to the proper VLAN to reach the server.
  6. The only way I can get this to work is to manually go into the phone and hard code the Voice VLAN ID. Then the phone sees the server and loads the config. correctly.

I don’t see any settings to try and make this work. Am I missing something?

2

Can’t speak to Netgear brand switches specifically, but our Cisco switches require the server port to be flagged as the voice VLAN ID for both data & voice VLANs in order to work. (Disclaimer: it’s been a very long time since I provisioned any Sangoma brand phone and I’m going by memory; vast majority of those we bought are sitting in a box upstairs.)

3

Thanks for providing that. I am reaching out to Netgear support to see if they have any thoughts on this. This is my first foray into using FreePBX and so I picked up some of those phones to play around with to get familiar with the configuration and interface.

4

The one thing I don’t see listed here is that you went into the phone provisioning template and set the proper VLAN ID on the phone. It sounds like the Voice VLAN is expecting tagged traffic from the device. If the phone doesn’t have the VLAN ID programmed into it then it will default to VLAN ID 1.

If adding the VLAN ID manually into the phone fixes all the problems then it really sounds like you don’t have the provisioning template setup correctly with the proper VLAN ID.

5

Hi. Yes, I did see that in the template and tried different options with the same result. Now I am wondering if it’s trying to connect over the WAN port in this VLAN case which was not the case when I was doing this over a flat network. I am going to forward the relevant ports and see if that makes a difference.