>I think you need to keep the port a trunk port w/ a native vlan of 10.... sipx > should be plugged into a vlan 210 port and the phones should tag voice > packets > on vlan 210. If you need to access the phone network from the data network, > something has to route, whether it be the switches or the firewall/router.
>From the sounds of things, I'm going to guess you only have one network interface on your sipXecs server. If that is the case, you will need to do a couple of things. Depending on how your switches configure their vlans, you will either need the port on the switch that connects to your sipXecs server to be in multiple vlans or you will need to make the switch port a trunk port. You will then need to create a vlan interface on the sipXecs server for your voice vlan and also for your data vlan, so traffic for each vlan can be properly tagged for each set of traffic. There are many howto's on the internet on Linux Vlan interface configuration. Here's one http://www.n-tek.de/?q=node/15. If you are using just one nic and your switch port is only set to your voice vlan, routing won't help, b/c there will be no connection to the data vlan. <---- assumes one interface and the either your data or your voice ip is an alias as opposed to a vlan interface. The other alternative would be to use two network interface cards and put your voice on one nic and your data on the other, then each switch port would just get the right vlan respectively and you will not need to get the server to vlan tag at all. Matt P. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
