Hi Javcia, Thanks for posting here. Base on my knowledge this is a Vendor Specific DHCP option , so are we using windows DHCP server to co-work with other devices? VOIP maybe? Technically we can add Vendor Specific DHCP option by using command netsh dhcp server scope ipaddress set optionvalue 125 <code> to set the value. Thanks. Tiger LiTiger Li TechNet Community Support

Hi Javcia, Thanks for update. May I know what VOIP devices are we going to deploy ? At this moment , I think wed better to consult with the support service of that VIOP device in order to get the code for corresponding OS . After that we can set vivso into Windows DHCP service. Thanks. Tiger LiTiger Li TechNet Community Support

Hi Javcia, Thanks for posting here. Base on my knowledge this is a Vendor Specific DHCP option , so are we using windows DHCP server to co-work with other devices? VOIP maybe? Technically we can add Vendor Specific DHCP option by using command netsh dhcp server scope ipaddress set optionvalue 125 <code> to set the value. Thanks. Tiger LiTiger Li TechNet Community Support

Hi Tiger Li, Thank you for replay. The device that i`m using supports data and VOIP. So i need to define enterprise number: 25167, the length of the following data: 16, the sub-option code: 1, the length of the suboption content: 14 in option 125. This is example of linux, but i need to do on server 2008: The example below demonstrates how to return option 125 for the widely used ISC DHCP server. Option 125 is defined using option vivso (vendor-identifying vendor-specific-options). Vivso is a string, with hex byte definitions (\xNN notation) where needed. It contains: The Genexis enterprise ID in the first four bytes (decimal 25167, string "\x00\x00\x62\x4f"). The length of the following data (here decimal 16 or "\x10") . The sub-option code (always decimal 1 or string "\x01" for GAPS). The length of the suboption content (here decimal 14 or "\x0e"). The GAPS ascii string as defined in Appendix A. # Create a test network that gives IP addresses in the range 192.168.10.100 # to 192.168.10.200 subnet 192.168.10.0 netmask 255.255.255.0 { range 192.168.10.100 192.168.10.200; option domain-name-servers 192.168.10.2; # The next line ensures that the location of the GAPS server is communicated to the # DRG700 and Hybrid CPE's (and not any other devices). The location is the # IP address of the GAPS server in your test network. If substring (option vendor-class-identifier, 0, 6) = "drgos-" { option vivso "\x00\x00\x62\x4f\x10\x01\x0es=192.168.10.1"; } default-lease-time 86400; max-lease-time 259200; } Thank You

Maybe some one can help me? i need some information how to set up DHCP option 125 on server 2008 R2 x64. I can`t find any info about it. Thank You

Hi Javcia, Thanks for update. May I know what VOIP devices are we going to deploy ? At this moment , I think wed better to consult with the support service of that VIOP device in order to get the code for corresponding OS . After that we can set vivso into Windows DHCP service. Thanks. Tiger LiTiger Li TechNet Community Support