NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
VoIP Phone has a connection, but phone does not work
Hi All, I'm upgrading to new switches and trying to get voip and data vlans working so users can plug computers into backs of phones. Working with a GS752TPv2. Data is vlan 1 (default). Voi...
For anyone who stumbles on this, I found my mistake.
The phone has only 1 IP address. When I tried to split off VLAN 20 to go out port 47, I wouldn't work because port 47 connected to the gateway at a different subnet than the phone was on (our current setup has phones and computers on completely separate networks). I wanted to let people plug data in through the phones so it had to be on the data LAN.
Once I changed my firewall rules to allow the plethora of ports used by my phone company to talk to my data lan as well as my phone lan, it worked!
I now have auto-voip set up. I'm still baffled about how this works with Phone VLAN, or if it even does. I think the auto-voip sees phone traffic and priorizes it appropriately. Not sure how to test I have it set up right other than plug a bunch of phones in and get them all on a conference call while transfering data through the switch. I did this with two deskphones, a polycom style speaker phone, and my cell phone dialed in, and it sounded fine.
Fingers crossed for my deployment next month.
Thanks,
Jeff
- Data works fine. I plug into the back of the phone and I can get to my LAN.
- Voice is another story. The phone boots. I get a screen. But no dial tones and cannot call it, also buttons do not work. (Yes, I tested the phone in my old switch and it works.) Below is more detail on my setup
- VLAN 20 is on ports 1-46, tagged.
- VLAN 20 is on port 47, untagged.
- VLAN 1 is on all ports, untagged, except port 47; it's not on there at all.
- Port PVID is 20 on port 47, 1 on all others.
- Voice VLAN Config set to VLAN 20 for ports 1-46.
- Auto-VoIP enabled on ports 1-46, and port 47: protocol-based, class 7.
- VLAN 20 Routing is set to an address I set aside in my voice network.
I'm really curious why the port 47 is Untagged on VLAN 20 and assign to PVID 20. Is this your uplink? If this is your uplink, it should be Tagged and assigned as PVID 1. I'm only assuming that this is your uplink and this is why only the data traffic is passing thru because only Untagged traffic is assigned.
Regards,
John
NETGEAR Community Team
Hi John,
I don't want data (vlan 1) going out port 47 at all. Only phone traffic should use that. Data goes out a LAG on SFP 51-52. I tried vlan 20 tagged on port 47 as well but no dice.
Is that not the way to do that?
Thanks,
Jeff
For anyone who stumbles on this, I found my mistake.
The phone has only 1 IP address. When I tried to split off VLAN 20 to go out port 47, I wouldn't work because port 47 connected to the gateway at a different subnet than the phone was on (our current setup has phones and computers on completely separate networks). I wanted to let people plug data in through the phones so it had to be on the data LAN.
Once I changed my firewall rules to allow the plethora of ports used by my phone company to talk to my data lan as well as my phone lan, it worked!
I now have auto-voip set up. I'm still baffled about how this works with Phone VLAN, or if it even does. I think the auto-voip sees phone traffic and priorizes it appropriately. Not sure how to test I have it set up right other than plug a bunch of phones in and get them all on a conference call while transfering data through the switch. I did this with two deskphones, a polycom style speaker phone, and my cell phone dialed in, and it sounded fine.
Fingers crossed for my deployment next month.
Thanks,
Jeff
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
