IP Touch 4028 - AVA : NOT working on Windows 2008 DHCP
Posted: 21 Aug 2014 05:50
In my firm, I configured a DHCP linux server for our ip touch 4028. Each switch port (where a ip touch is connected) is tagged in the VLAN Voice associated. Each ip touch doesn't use "Use VLAN" Option. AVA is used with the DHCP linux server with this configuration (here VLAN 231):
It works perfectly! 
Now the problem...
I want to change our DHCP server for VOIP. We wants to use Windows Server 2008 R2 - DHCP.
So, I'm trying to configure Windows DHCP with the same vendor-class and options 66, 67 and 43. But nothing works... 2/5 network setup... bad tftp1 address.. reset... etc.
Everything only works without AVA, without new vendor-class, and with options associated to general class. But in that case, we need to force VLAN on ip touch (we don't want to force VLAN, we want just plug the phone)
Please, there is someone here to help me to enter the good configuration for Windows DHCP? (In fact, just a good adaptation from my linux configuration).
Code: Select all
subnet 192.168.231.0 netmask 255.255.255.0 {
option routers 192.168.231.1;
option broadcast-address 192.168.231.255;
if substring (option vendor-class-identifier , 0 , 16) = "alcatel.noe.0" {
option vendor-encapsulated-options 3a:02:00:e7:ff;
}
next-server 192.168.118.4;
Now the problem...
I want to change our DHCP server for VOIP. We wants to use Windows Server 2008 R2 - DHCP.
So, I'm trying to configure Windows DHCP with the same vendor-class and options 66, 67 and 43. But nothing works... 2/5 network setup... bad tftp1 address.. reset... etc.
Everything only works without AVA, without new vendor-class, and with options associated to general class. But in that case, we need to force VLAN on ip touch (we don't want to force VLAN, we want just plug the phone)
Please, there is someone here to help me to enter the good configuration for Windows DHCP? (In fact, just a good adaptation from my linux configuration).