<div dir="ltr">So there are two network cables going from your distribution closet to your desk. One cable to the phone and one cable to the PC? I want to run one cable, have the phone on the voice network and PC on the data network. If I have to configure the VLAN manually that is fine I just want to know if it will work this way. <br>
<br>
<div class="gmail_quote">On Fri, Jul 18, 2008 at 8:28 AM, Bill Simon <<a href="mailto:bills@psu.edu">bills@psu.edu</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Note I said logically separated not physically separated. Yes you run a cable to your PC and a cable to your phone. You can do the logical separation at the switch (configure port-based VLANs) or further downstream if you want a whole switch of just phones and another whole switch of just PCs... etc. We do not run separate core networks. Disadvantages?... if we want to connect from pc to the voice network it's routed (but this is to our advantage because then we have the ability to set up access lists at the router level). We can't use VT Advantage (not a concern) and we miss out on some silly click-to-dial stuff that no one in our organization seems to care much about. Rather, they want a rock-solid phone system and that's what they get.<br>
<br>I guess the definition of "converged network" is different for everyone though.<br><br>Voice Noob wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">Bill I don't think you situation is comparable to most. You are not using a converged network which is one of the big reasons to go with an IPT system. You have two physical networks one for voice and one for data.<br>
I want to have one physical and two logical networks like I can with Cisco phones and Cisco switches. The phone boots up and changes to the voice vlan and the phones are on the data vlan. I don't care to tell the customer that they must manually configure this but can they still use DHCP for all of the IP info and just manually set the voice vlan?<br>
ALso if I do this how do I set it up on the HP switch side? Is it a trunk or an access port with two vlans?<br><br></div>
<div class="Ih2E3d">On Fri, Jul 18, 2008 at 7:00 AM, Bill Simon <<a href="mailto:bills@psu.edu" target="_blank">bills@psu.edu</a> <mailto:<a href="mailto:bills@psu.edu" target="_blank">bills@psu.edu</a>>> wrote:<br>
<br> We use (have used but are phasing out) HP Procurve on the voice<br> network. No problem. But note: we have a logically-separated<br> voice network, do not use the phone's PC port (thus no need for<br> VLAN) and have had to deal with power insertion because our HP<br>
switches are not powered.<br><br> CDP is not needed. I don't understand what you mean about hard-code<br> the configuration. DHCP provides the options the phone needs to<br> contact Call Manager.<br><br> I was watching the other thread about Adtran and some of the stuff<br>
people said seems quite like FUD. Cisco appreciates this<br> scare-tactic marketing but the truth is that you can use any LAN<br> switch. Using Cisco gear will make your life easier though.<br></div></blockquote>
<br></blockquote></div><br></div>