5550 console and DHCP option 125 1

[brewski6666]

Cluster of three Mitel 3300 version MiVB 8.0, on each of the three sites there is a 5550 console, DHCP is provided by the 3300. we plan to migrate the three sites on a Mivoice Express in the cloud and my concern is about the console 5550 since the 3300 will be removed and I do not have a DHCP server on site. I need your expertise and suggestions on how to run the 5550 in this case.
Does the 5550 need absolutely the DHCP option 125 to work?
Can a local PFSence firewall (Linux based) provide DHCP option 125 to the 5550 console?

 

[jpruder]

I used the public domain e-smith smeserver to do dhcp before Mitel had it going on MSL, both are very similar and based on Centos. I defined 125 as hex and used the dhcp tool to create the string. I would think you could do something simial PFSense. I have also done the same thing on Sonicwall's, creating that string requires a bit more typing, but doable. I don't know how much bandwidth you will have, but you might think about hosting the tftp firmware locally
.

 

[Billz66]

Strongly suggest removing the 5550 and migrating to My Voice Business consoles


If I never did anything I'd never done before , I'd never do anything.....

 

[brewski6666]

Thanks Billz66 for the advice, I made the same recommendation for the client but ($$$) he preferred to postpone.
Thank you jpruder for the information, I am not very familiar with the creation of the option 125 on Linux, do you have a link for a documentation that explains how to do it?.
Has anyone ever managed to configure option 125 on a PFSense ?.

 

[Billz66]

you might be able to use something like this ( was used long time ago when we did dhcp on linux server)

Option 43 is normally able to be used as an alternative for 125

#custom options
option IP-phone-TFTP-Server-IP-Address code 128 = ip-address;
option IP-phone-TFTP-Server-IP-Address 192.168.243.244;
option RTC-IP-Address code 129 = ip-address;
option RTC-IP-Address 192.168.243.244;
option IP-phone-DHCP-Server code 130 = string;
option IP-phone-DHCP-Server ""MITEL IP PHONE"";
option Phone-Analyser code 131 = ip-address;
option Phone-Analyser 192.168.247.195;
option mitel-option code 43 = string;
option mitel-option = ""id:ipphone.mitel.com;sw_tftp=192.168.243.244;call_srv=192.168.243.244;vlan=2;l2p=6;dscp=46;ipa_srv=192.168.247.195"";


this is the DHCP conf file from a mitel MSL server which might also give some tips (was configured from web interface)

from dhcpd.conf in \etc
#------------------------------------------------------------
# !!DO NOT MODIFY THIS FILE!!
#
# Manual changes will be lost when this file is regenerated.
#
# Copyright (C) 1999-2010 Mitel Networks Corporation
#------------------------------------------------------------


authoritative;
ddns-update-style none;
allow bootp;

class "vendor-class-60"
{
match option vendor-class-identifier;
}

# vivso option space
# - vendor: Mitel
option vendor.eid-1027 code 1027 = text;

option domain-name "company.com";
option domain-name-servers 192.168.90.90;
option domain-name-servers 8.8.8.8;

# 125: vendor[1027] Mitel
option vendor.eid-1027 "id:ipphone.mitel.com;call_srv=172,16,10,2;l2p=6s3m4v6;dscp=46s24m34v46;sw_tftp=172.16.10.2";
# option 43
if option vendor-class-identifier = "ipphone.mitel.com\000" {
option vendor-encapsulated-options "id:ipphone.mitel.com; call_srv=172.16.10.2; l2p=6s3m4v6; dscp=46s24m34v46; sw_tftp=172.16.10.2";
}


subnet 172.16.10.0 netmask 255.255.255.0
{
option broadcast-address 172.10.10.255;
allow bootp;
default-lease-time 86400;
max-lease-time 604800;



option subnet-mask 255.255.255.0;
# default local range
pool {

range 172.16.10.65 172.16.10.250;

}

option routers 172.16.10.254;
option routers 172.16.10.254;



}



If I never did anything I'd never done before , I'd never do anything.....

 

[brewski6666]

Thanks again Billz (you deserve a star for this contribution).
will be onsite next week for testing and will update.