config 3500yl ToIP AASTRA with 3 VLANS

[cenk sasmaztin]

for example

http://www.voiplink.com/Aastra_57i_IP_Phone_Four_Lines_Two_Ethernet_p/aastra-57i.htm

this phone support 802.1q vlan tag ing
you can connect taging port this phone and if you attach pc this phone


but this phone don't support 802.1q do not connect taging port this phone this phone must connect on ip phone vlan untag port
and don't use pc same port

http://www.voiplink.com/Aastra_9112i_IP_Phone_One_Line_p/aastra-9112i.htm

[Harry92]

aastra phone are SIP 53i and support 802.1q.

The client want that DHCP server give the vlan ID at this phones because there is 200 phones to deploy...

thanks

[Harry92]

There is a pc (untagged in vlan data )connect to phones

thanks for your links

[Harry92]

if my config is true, i think that there is a pb on DHCP server?

It's not me who configure the server, and the administrator of server said me ; the pb is because of untagged or tagged on your switch..

[cenk sasmaztin]

dhcp server don't give vlan id on client

for give dynamic vlan id on ip phone
you can use 802.1x &dynamic vlan config

when connect on ip phone on your network switch this port turn vlan 5 member(with radius server) for ip phone therefore your ip phone support 802.1x protocol

if don't use 802.1x on your network you must manuel config each ip phone

[cenk sasmaztin]

dhcp server connect must be untag port on vlan 3
IPBX device connect must be untag port on vlan 4

ip phone device connect must be taging port on vlan 5

you must define vlan id each ip phone device manually

[Harry92]

Ok,
but my client said me it's possible of deliver vlan ID by DHCP without to use 802.1X

[cenk sasmaztin]

802.1x is authentication protocol for security
we can use radius server (Microsoft IAS)
radius server remote active directory rule give vlan id on switch port

if your device support 802.1x protocol you can give dynamic vlan your network device

please see this demo

http://s1.dosya.tc/802.1x_dynamicvlan.rar.html

[Harry92]

Ok thanks
I try Monday

[Mark Wibaux]

Assigning a VLAN to an IP phone via DHCP depends purely on the phone supporting it. Not all IP phones do.
For example with an Avaya phone you need to setup 2 DHCP scopes on your server.
Each port connecting to your phones needs to be "untagged" in one VLAN and "tagged" in the voice VLAN.

The first scope is in the "untagged" VLAN range, when the phone first boots it starts up without VLAN tagging enabled which means that its DHCP request goes out on the ports untagged VLAN. The DHCP server responds with an IP address from that scope. The response contains additional DHCP options (other than Gateway, DNS etc), in the case of Avaya phones you setup a custom option 176 which contains a string that tells the phone what is the default VLAN and what is the voice VLAN (option for Avaya phones looks like this "L2Q=1,L2QVLAN=7" where VLAN 7 is the voice VLAN).
The phone reads this string and reconfigures itself for the Voice VLAN and then reissues a new DHCP request on this VLAN. The DHCP server then responds with an IP address from its other scope. In the case of Avaya phones this has a new option 176 string that completes the setup of the phone.
You need to check and see if your phones actually support VLAN configuration via DHCP and if they do what are the DHCP options you need to setup to achieve this.