Good day,
I’m having some difficulties programming the DHCP server options on a Routerboard RB751G (version v6.0rc14). I want to use these routerboards to hand out DHCP settings to Mitel IP handsets for hosted PBX installations where there is no Mitel controller / IP PBX (usually used to handle DHCP) on site.
In the Mitel Controller one would normally have to specify the following DHCP options to get everything to work as it should:
Option ID = 3
Name = Router
Value = 172.72.72.254
Format = IP Address
Scope = Global
Vendor ID =
Option ID = 125
Name = Mitel
Value = id:ipphone.mitel.com;sw_tftp=10.0.1.240;call_srv=10.0.1.240;vlan=300;l2p=6v6;dscp=46v46s26
Format = ASCII String
Scope = Global
Vendor ID = 1027
Option ID = 128
Name = TFTP Server
Value = 10.0.1.240
Format = IP Address
Scope = Global
Vendor ID =
Option ID = 129
Name = Call Server
Value = 10.0.1.240
Format = IP Address
Scope = Global
Vendor ID =
Option ID = 130
Name = IP Phone Identifier
Value = MITEL IP PHONE
Format = ASCII String
Scope = Global
Vendor ID =
Option ID = 134
Name = DSCP
Value = 46
Format = Numeric
Scope = Global
Vendor ID =
I have tried various setting to get this to work without any success. Here is an example from my current config:
[admin@test] /ip dhcp-server option> print
NAME CODE VALUE RAW-VALUE
0 TFTP Server 128 ‘10.0.1.240’ 0a0001f0
1 Call Server 129 ‘10.0.1.240’ 0a0001f0
2 IP Phone Identifier 130 ‘MITEL IP PHONE’ 4d4954454c2049502050484…
3 DSCP 134 ‘46’ 3436
4 Router 3 ‘192.168.55.253’ 3139322e3136382e35352e3…
5 Mitel 125 'id:ipphone.mitel.c… 69643a697070686f6e652e6…
[admin@RWS-HOME] /ip dhcp-server option>
I have also linked all these options under ‘Networks’ and can see the values being passed to the IP phone on startup in the routerboard log. It seems like the format or RAW-VALUE is incorrect as the phone does not receive ‘10.0.1.240’ as the TFTP server.
Your help would be greatly appreciated!
Thanks in advance!
I have added the next server and have changed the DSCP option 134 as per you previous posting but unfortunately still no luck
When I do a DHCP trace after the phone has boot up it shows the following (which is obviously wrong):
TFTP Server: 52.46.57.52 (This should be 10.0.1.240)
ICP Server 1: 49.48.46.48 (This should be 10.0.1.240)
ICP Server 2: 46.49.46.50 (Think this should be empty!)
Mitel ID: MITEL IP PHONE (This is correct)
DSCP 1: 0
DSCP 2: 46 (Correct)
DSCP 3: 24 (Think it is correct)
DSCP 4: -1 (Not sure what this should be)
VENDOR SPEC1: id:ipphone.mitel.com (This is correct)
Hihihihih greate…thanks for the wirechark dump.
What i can see… is the ip adress is in wrong format … lol
If you convert the hex to dec… you will se that you need to take back the old format of the ip adress.
so
add name="TFTP Server" code=128 value=0x0a0001f0
Sorry for my laght… but then i saw the hex ip adress converted to decimal ip string like the info on the phone…i cant hold my self.
TFTP Server: 52.46.57.52 (This should be 10.0.1.240)
Best luck… and wirechark are greate… to analyse.. whats wrong..
Thanks so much for your help. I have made the change as requested and now the DHCP trace reflects as follow:
TFTP Server: 48.46.48.49 - this was 52.46.57.52 before the change to 0x0a0001f0 (This should be 10.0.1.240)
ICP Server 1: 49.48.46.48 (This should be 10.0.1.240)
ICP Server 2: 46.49.46.50 (Think this should be empty!)
Mitel ID: MITEL IP PHONE (This is correct)
DSCP 1: 0
DSCP 2: 46 (Correct)
DSCP 3: 24 (Think it is correct)
DSCP 4: -1 (Not sure what this should be)
VENDOR SPEC1: id:ipphone.mitel.com (This is correct)
The value has changed, but the format has to be still wrong - any advice?
Formerly user-defined or site-specific options declared public and tentatively unavailable by RFC protocol. Mitel-specific parameters assigned to options in this range have been reassigned in 3300 ICP, Release 7.0 to Options 43 and 125.
Note: Legacy options will remain in the list following an upgrade to Release 7.0 to provide backward compatibility with IP sets that have yet to be upgraded with firmware that supports the new options 60/43 and 124/125. No support will be provided for multiple l2p and dscp values.
And for the last line…
Have you tried to remove the spacees in the 125 string.
Here is a working configuration from a linux server with the Internet System Consortium’s (ISC) open-source DHCP Server. Maybe this will give you a hint of how to configure RouterOS DHCP Server.
Big thanks to everyone for the assistance. As per the previous post Mitel now uses option 125 mainly and for the IP consoles and some DECT and outdated firmware phones it still requires options 128 and 129. Unfortunately I could not get option 125 to work using the above described methods, but if any else is having the same issue, here is what I had to do to get it to work:
1.) Option 128 and 129 has to be in HEX as follow (This is for 10.0.1.240)
ip dhcp-server option add name=“TFTP Server” code=128 value=0x0a0001f0
ip dhcp-server option add name=“Call Server” code=129 value=0x0a0001f0
2.) Option 134 has to be in HEX as follow
ip dhcp-server option add name=“DSCP” code=134 value=0x2E
3.) Option 125 has to be in HEX as follow
ip dhcp-server option add name= “Mitel” code=125 value=0x000004033C69643A697070686F6E652E6D6974656C2E636F6D3B73775F746674703D31302E302E312E3234303B63616C6C5F7372763D31302E302E312E3234303B
Mitel has a tool called “DHCP option 125 config helper for windows” that I had to use in order to get the HEX correctly. You simply put in all the mitel server detail and copy the HEX converted format to clipboard (remember to prefix this string with “0x” to indicate to routerOS that it is a HEX string.
Once again thanks for everyone’s assistance and I hope this thread can be of some help to others
It’s not easy with dhcp options, i have learned a lot of this on my routers.
On the internet, iptv and voip solution at home.
Like with sub options on the 43.
