What would cause a PBX or SIP phone to not register on the network when using Netgear Switches?

6,742

Inside the settings of the Netgear switch is a section called Voice VLAN. It defaults to VLAN2 and is Enabled by default.

Now, even though you're not tagging any ports with VLAN2, the switch is still trying to put all voice devices on VLAN2. This is why it's not getting connectivity on voice devices.

When a computer is connected through the phone, the Voice VLAN is still trying to send the phone to VLAN2 while sending the computer to VLAN1.

Disabling the Voice VLAN solves the issue and allows all traffic to function as expected.

Voice VLAN Config

Share:
6,742
Chase Florell
Author by

Chase Florell

I'm a developer in BC Canada and one of the owners of Flo Media Group Inc. I work primarily in C# .NET, Xamarin, HTML5 and Javascript, and I'm also very passionate about DevOps, and have been known to sling my fair share of PowerShell. When I'm not coding, I'm enjoying time with my wonderful wife and children, riding my motorcycle, camping in the summer months, snowboarding in the winter, or maybe just a round at the Golf Course. I Blog Here, and I'm also on Linkedin Contact Me

Updated on September 18, 2022

Comments

  • Chase Florell
    Chase Florell over 1 year

    We have 3 different types of switches in our network.

    1. All of our IP Phones are running on HP 2520-24 PoE switches.
    2. Our primary backbone is "supposed to be" running on Netgear GS748T switches.
    3. Our OLD switches are Dell PowerConnect 2848. These need to be removed.

    I've drawn two diagrams (below).

    1. The first one is what we want, but doesn't seem to work.
    2. The second one what we have now, it's working but not desireable.

    network layout


    My question is quite basic. What is in the Netgear GS748T switches that would

    1. Block my SIP phones from getting IP address when the DHCP server is connected directly to it?
    2. Prevent my PBX from accessing the network?

    FYI: If I PING the pbx when it's connected to the DELL server, it responds appropriately, but if I PING it when connected to the Netgear, it times out. The PBX has a static IP set.

    All computers (which are on the exact same network) are connected just fine (including receiving IP addresses via DHCP).

    Here are some screenshots of the switch config. This is the switch that the VoIP server is connected to.

    enter image description here

    enter image description here

    enter image description here

    The Dell switch is set as unmanaged, and the Netgear connected to the DHCP server is also basically unmanaged (other than having a static IP).

    NOTE: we have not configured LAG's (yet) and there is only a single line between switches.
    NOTE: the VoIP connection is shown as "offline" because when the screenshot was taken, the PBX was connected to the DELL switch. It shows as "online" when the PBX is connected to the Netgear switch.

    • Admin
      Admin over 11 years
      Well the port config screenshot shows interface g1 as being down, so I would look at that first. Start with the physical layer (cabling) and work your way up the OSI layers from there.
    • Admin
      Admin over 11 years
      sorry, it's "down" because I need my VoIP system online, so EVERYTHING is plugged into the DELL switch when the screenshots were taken.
    • Admin
      Admin over 11 years
      Currently the dell is directly above the netgear, and when I move the PBX from port 1 (dell) to port 1 (netgear), I lose connectivity. I use the same cabling in both situations.
    • Admin
      Admin over 11 years
      Are you allowing enough time for ARP caches to expire?
    • Admin
      Admin over 11 years
      probably not when it comes to moving the PBX over to the Netgear switch, but definitely when we plugged the DHCP server into the Netgear. The reason I say that is because we left it overnight, and our phones still didn't have IP's in the morning.
    • Admin
      Admin over 11 years
      Also, since were just swapping switches, and the ARP table is on the Router, why does expiration matter (honest question)? I'm pretty convinced this is a Netgear issue, since other switches don't carry these same issues.
    • Admin
      Admin over 11 years
      Every TCP host has an ARP table. The workstations, servers, phones and switches all have an ARP table. Seeing as you left everything overnight, it probably isn't an ARP cache issue.
    • Admin
      Admin over 11 years
      I've updated the diagram to reflect the fact that user PC's are connected to the network through the telephones, and they are ALWAYS connected regardless of the switches.
    • Admin
      Admin over 11 years
      Are there VLAN's configured that need to be set up on the new switch. I could see that as the cause if everything but the phones are in the default VLAN 1 and the phones are in another VLAN.
    • Admin
      Admin over 11 years
      Where are you pinging the PBX from? Can the PBX ping the Netgear switch?
    • Admin
      Admin over 11 years
      There are no VLAN's configured on our system. We're using the default VLAN1 for everything.
  • Chase Florell
    Chase Florell over 11 years
    I'm not well versed in VLAN's, how does it work when the Workstations are connected to the network through the Telephones?
  • Olivier Dulac
    Olivier Dulac over 11 years
    There is a good chance that by default they are in separate VLAN. But this changes depending on your phone types (and on their config, usually on the PBX server that send them their config, if they can connect to it). You should ask a local voip person to have a look, difficult remotely ^^
  • Chase Florell
    Chase Florell over 11 years
    I've looked in the PBX config, and the switch config, and everything is set to use the default VLAN (1). Also, as I specified above, if I plug into a different switch, everything comes online... it's only being blocked when connected to the Netgear switches.
  • the-wabbit
    the-wabbit over 11 years
    Now this is what I would call a crappy factory default - because it simply creates a configuration you never seen with other brands and would never expect in that way. And where there is one, more are to come. Thank you Netgear for providing another vivid example for why not to consider using your products.