DHCP subnet with two different IP phones

Mike Diggins mike.diggins at mcmaster.ca
Mon Sep 29 01:08:00 UTC 2014


Hello,

I have ISC DHCP V4 configured for my Nortel IP Phones. Soon we are 
adding Avaya 96xx series phones which require a different DHCP 
configuration and I could use some assistance how to best handle that. 
Both types of phones will share the same network and address range.

My current configuration:

option space Nortel;
option Nortel.data code 128 = string;

class "ipphones" {
   match if substring(option vendor-class-identifier,0,14) = 
4e:6f:72:74:65:6c:2d:69:32:30:30:34:2d:41;
}

shared-network Voice1 {
   subnet 172.25.5.0 netmask 255.255.255.0 {
     option routers 172.25.5.5;
     option broadcast-address 172.25.5.255;
     option subnet-mask 255.255.255.0;
     allow unknown-clients;
     default-lease-time 86400;
     max-lease-time 86400;
     pool {
       vendor-option-space Nortel;
       option Nortel.data 
"Nortel-i2004-A,172.25.10.203:4100,1,5;172.25.10.203:4100,1,5;172.25.47.22:5000.";
       range 172.25.5.128 172.25.5.254;
       allow members of "ipphones";
     }
   }
}

I want to add the following new class and options for the 96xx series 
phones but I'm not sure how best to merge the two? Do I add the Avaya 
option statement into the subnet pool declaration above or move the 
Nortel option statement out of the pool declaration and into the class 
"iphones". I want DHCP to respond with only the correct option matched 
to the phone.

option space AVAYA_PHONE;
     option AVAYA_PHONE.242 code 242 = text; #Used by 96xx and newer 
hardware

class "avaya-phones" {
     match if substring (option vendor-class-identifier, 0, 13) = 
"ccp.avaya.com" ;
     option AVAYA_PHONE.242 
"MCIPADD=172.25.43.18,172.25.43.19,MCPORT=1719,TLSSRVR=172.25.43.80,HTTPSRVR=172.25.43.80,DIR=sip,TLSDIR=sip,HTTPDIR=sip"
}


-Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20140928/305f2ae9/attachment.html>


More information about the dhcp-users mailing list