We are looking at NEC IP phones (either an IPS or SV7000MPS) for one of our sites. Our network folks are a little apprehensive about the idea. They think that the IP phones should be on their own separate network. I say why bother with IP if that is the case. I told them the IP phones have a pass through for a network connection for a PC and they felt that they would lose management capabilities to the desktop PC using Cisco NAC. Any one have any thoughts or ideas regarding this?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
NEC IP phones and Cisco NAC 1
- Thread starter grh959
- Start date
- Thread starter
- #2
Usually you would setup the network switchport to be a trunk or multi-vlan access port and have the phone tag it's frames w/ the voice vlan. This way the data and voice traffic is separate. If you have unmanaged network switches though, you would be in for a world of hurt.
- Thread starter
- #5
-
1
- #6
Though we have done many IP installs, we prefer the simple approach i.e. physical separation between voice and data. Not doing the separation, gives you the benefit of a lower cost on cabling but a higher cost in support. Few people have a thorough understanding of VLANs, QoS and troubleshooting VOIP issues. Your approach is correct -- If we must do a physical separation, then why do IP altogether?
That has been CTVI's position though we are approaching a turning point. In a white paper posted by one of our techs, you will see that we argue strongly against VOIP within an local network i.e. one building and only recommend VOIP for networking phone systems or small remote and home offices.
The reason that we are approaching a turning point is due to the fact that applications are becoming available. One such example, is the convergence of the of cell phone and phone via 802.11 wireless technology. Now you can have your pbx station calls come to you via your wireless lan chip over your mobile phone while you are in an area that has wireless lan i.e. your home etc.
Bottom line, the immediate conditions do not justify VOIP with in a local area network. The cost savings of the cabling will be quickly wiped out with the long term cost of supporting VOIP and phone traffic on the same network.
Long term, VOIP will rule and some people argue that they would like to be ready now.
If you want to do VOIP over the same LAN,
1. You must have managed switches. The Cisco switch is excellent.
2. You should have a VLAN set up with the phones tagged and the PCs untagged. The ports in the switch will be trunk ports.
I am not familiar with the term Cisco NAC. Please describe or point me in the right direction.
That has been CTVI's position though we are approaching a turning point. In a white paper posted by one of our techs, you will see that we argue strongly against VOIP within an local network i.e. one building and only recommend VOIP for networking phone systems or small remote and home offices.
The reason that we are approaching a turning point is due to the fact that applications are becoming available. One such example, is the convergence of the of cell phone and phone via 802.11 wireless technology. Now you can have your pbx station calls come to you via your wireless lan chip over your mobile phone while you are in an area that has wireless lan i.e. your home etc.
Bottom line, the immediate conditions do not justify VOIP with in a local area network. The cost savings of the cabling will be quickly wiped out with the long term cost of supporting VOIP and phone traffic on the same network.
Long term, VOIP will rule and some people argue that they would like to be ready now.
If you want to do VOIP over the same LAN,
1. You must have managed switches. The Cisco switch is excellent.
2. You should have a VLAN set up with the phones tagged and the PCs untagged. The ports in the switch will be trunk ports.
I am not familiar with the term Cisco NAC. Please describe or point me in the right direction.
- Thread starter
- #7
Thank you CTVI, I knew you would have a ton of knowledge on this.
Cisco NAC (Network Admission Control) is something my network people are concerneed about.PLease see this link
I am passing this very valuable info on to my network people and look at the white paper you have mentioned.
Cisco NAC (Network Admission Control) is something my network people are concerneed about.PLease see this link
I am passing this very valuable info on to my network people and look at the white paper you have mentioned.
OzzieGeorge
Programmer
Even if you are going voip for the reasons stated it is probably wise to have seperate networks in order to future proof your data network.
If at some future time your network takes a quantum leap in speed the usual consequence is a faster switch gets installed and a faster NIC in your computer. However if you have a common network your phone sits between your switch and the NIC so in order to boost the speed you would also have to change the phone. Adding considerably to any upgrade costs.
If at some future time your network takes a quantum leap in speed the usual consequence is a faster switch gets installed and a faster NIC in your computer. However if you have a common network your phone sits between your switch and the NIC so in order to boost the speed you would also have to change the phone. Adding considerably to any upgrade costs.
I had a brief look at teh Cisco NAC and also had one of our sales reps double check with NEC and it seems that there should be no issue or conflict with NEC or the setup you desire i.e. using one port on the phone for the pc.
- Status