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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows 2003 network

Status
Not open for further replies.

rflora

Technical User
Nov 26, 2003
80
CA
Not sure exactly where to post this. sorry everyone. We are planning to use VOIP in our office. Since the new voip phones will use the same network, i would like to somehow separate the voice packets and the data packets. I'm thinking subnetting or VLAN. And i'm not sure at all how subnetting will work, or how to configure things in that manner. I do have an idea bout VLAN's, and I know our switch supports. Other big reason I wanna do this is because of collision. If a collision occurs between computers on the network that should not affect the voip phones and vise versa. My question is how can i do this, or what is the best solution? Any help will be much appreciated. Thanks.
 
First question is what is doing DHCP for your client pc's? If the server is then what will be doing it for the phones? If the phones can receive an IP from a DHCP server then you may be fine, but changing the third ocet example (192.168.0.1 to 192.168.1.1)would prevent the ip conflick you could face. The key here is is there a DHCP Server.
 
Currently the DHCP is setup on the Domain controller, and all the clients authenticate with the same domain as well.
 
Sorry missed to included that the current DHCP will also service the phones. And thanks so much for replying to my post. I really appreciate it.
 
Unless your using true hubs you shouldn't have to worry about collisions. All the VOIP installs I've been involved with I have only seen one where they didn't run on the same line as the PC. I'm not sure why they did it. Reasons you want to use the same network include cost (of course)but also the phone and PC work together for a ton of things; video conference, direct dial from Outlook contacts, etc. Seems some really big benefits are lost when you seperate them. A single phone conversation consumes less than 64k of bandwidth, not much at all.



(yay! shameless advertising. my side business)
 
VLAN's are certainly the way to go...talk to your VoIP provider and see what they say. I'm sure they'll say VLAN and Layer 3 switches are the way to go. Also, you should consider PoE switches so you don't have to have a seperate power adapter at every phone.
 
Our whole network is switched, we dont' have any hubs at all. thank god! If I have the phone on a different subnet i know I would have to have to two RJ45 sockets for each user, one for data and one for voice, correct? and between the data and voice network, i would have to put a router ..? If i'm correct about this, the cost will definitelly be higher and the work for me! How bout VLAN's would that prevent collisions from happening and data flowing better ?
 
All the VLANs are going to do is breakup broadcast domains into smaller broadcast domains. Overall it's a good idea once the size of your network starts to grow. How many people/PCs in your office?

(yay! shameless advertising. my side business)
 
Currently we have about 20 workstation and 4 servers. In a month or so we are going to be adding another maximum 10 workstations at a new location. We will have a site-site vpn and about 30 voip phones all together. What would you recommed for this size? I know it's a fairly small network and shuldnt have data flow prob or collision.
 
So if you have only 20 clients and using switches then you shoulf be fine and have no ip conflicts. As for your remote location use a Cisco 871 VPN routes and let that do DHCP for that office. I currently run a large company using VPN for 4 out of 5 stores and in the process of switching to the Cisco 871 router...Good luck!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top