betski

from mitel sys admin. system config > IP Network Config > DHCP > DHCP Options > Add ID 125- the text should look something similar to the below-change 'ip mitel' to your mitel controller ip address.

id:ipphone.mitel.com;sw_tftp=ip mitel;call_srv=ip mitel;dscp=44

opaljoe

Thanks for the reply but I am trying to add option 125 to Mitel Standard Linux not the 3300 controller.

Cheers
Joe

acejavelin

My question is why use MSL as your DHCP server??? It is NOT as robust as the one in the 3300 and the documentation for the MSL recommends not using it either. The one in the 3300 is easily configurable and very reliable.

I do not think you could easily add option 125 to it anyway, that is a binary or hex encoded string, not plain text. To do it in MSL you would need to use the old Option 128-134 format provided you could figure out how to add it

__________________
Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost.

This is Telephony’s First Law of Equivalent Exchange.

opaljoe

I have 500 users. 100 of them are to be recorded via a 3rd party recorder connecting to Mitel's SRC. I have 2 subnets, 1 for the 400 not to be recorded and 1 for the 100 that need to be recorded. I need a DHCP server to run on both subnets. The subnet for 400 is using the 3300 and the subnet for 100 will use the DHCP server on the SRC/MSL.

acejavelin

OK, makes sense to me. Try this...

In the main admin screen go to Configuration/DHCP and follow these directions from the MSL Installation and Maintenance Guide:

---------------------------------------
To enable DHCP:

1. On the DHCP Service tab, click Edit.
2. Click Enable DHCP Service to enable the internal DHCP server. Note: Do not enable this server if a DHCP server already exists on the network.
3. Click Allow BootP to allow network clients to obtain IP addresses using the Bootstrap Protocol.

DHCP Configuration

To add a subnet:
1. On the Subnets tab, click Add subnet.
2. In the Name field, enter the name to apply to this subnet.
3. In the Subnet IP address, enter the IP address
4. In the Subnet Mask field, enter the mask to apply to this IP address.
5. (Optional) In the Router field, enter the IP address of the router used to access the subnet.
6. Click Save.

To remove a subnet:

1. On the Subnets tab, click the Remove link associated with the subnet you want to remove.
2. Click Save.

To add a subnet range:

If you have enabled DHCP and added a subnet, you must provide a subnet range.
1. On the Subnets tab, click Add range.
2. In the Range start field, enter the IP address at which to start the range of IP addresses available for assignment.
3. In the Range end field, enter the IP address at which to end the range.
4. In the Lease time field, enter the number of seconds to hold DHCP leases or accept the default setting.
5. Click Save.

To add a Static Host:

1. On the Static Hosts tab, click Add Host.
2. In the Hostname field, enter a name for the static host. (For example, host.mitel.com)
3. In the Host IP field, enter the static IP address of the host.
4. In the MAC address field, enter the MAC address of the host.
5. In the Client ID field, select a type and enter a corresponding value.
6. Click Save.

To add DHCP Options:

1. In the Scope field, select the scope to which to apply this option. (Global, Subnet, Range, or Host)
2. Select the option type for this option (Standard, Vendor, or Site-local).
3. Do one of the following:
For Standard options, select an option number from the list.
For Vendor options, select a vendor option from the list.
For Site-local options, enter an option number between 224 and 254. Click Next and then enter Name, Format, and value for the new option.
4. Click Save.

To view the state of all dynamic leases:

On the Lease View tab, click Refresh to see the most recent version of the list.
---------------------------------------

Just a few notes, Option 125 is a Binary Option, you cannot simply enter the text string in ASCII, but you CAN use options 128-134 in plain text instead of option 125 (the phones will look for and use a valid option 125 first, then look for 130, if that has a valid string it will look for options 128, 129, 132, 133, 134) enter them like so:

Option 128
Name: TFTP Server
Value: <IP Address of 3300>
Format: IP Address
Scope: Global (or as appropriate)

Option 129
Name: Call Server
Value: <IP Address of 3300>
Format: IP Address
Scope: Global (or as appropriate)

Option 130
Name: IP Phone Identifier
Value: MITEL IP PHONE
Format: ASCII String
Scope: Global (or as appropriate)

Option 132
Name: 802.1Q VLAN ID
Value: <VLAN ID>
Format: Numeric
Scope: Global (or as appropriate)

Option 133
Name: 802.1p Priority
Value: 6 (or as appropriate for your situation)
Format: Numeric
Scope: Global (or as appropriate)

Option 134
Name: DSCP
Value: 46 (or as appropriate for your situation)
Format: Numeric
Scope: Global (or as appropriate)

Only options 128-130 are truly required, but this is what is needed for VLAN or DSCP QoS.

Hope this helps, I do NOT have access to a MSL server at this moment, but these options work in other DHCP servers that do not support binary format option 125, so it should work in MSL too...

__________________
Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost.

This is Telephony’s First Law of Equivalent Exchange.

acejavelin

Note also this from the MAS server release notes (A similar MSL-based server):

"DHCP: Typically NOT enabled, if there is a DCHP server in your network such as the Mitel 3300 ICP. IP Phone support is no longer supported on the MAS server. Therefore, DHCP cannot be provided to your voice VLAN (phones)."

If this is the case, you may need a seperate Windows 2003 Server or similar server to hand out DHCP in this subnet.

Of course, you could always manually put these phones in Teleworker mode and point it to the LAN IP address of the 3300 and just use a "stupid" DHCP server... Not a real labor saver, but it works.

__________________
Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost.

This is Telephony’s First Law of Equivalent Exchange.

opaljoe

Decided to put a windows machine on the subnet running DHCP server. I'd spent enough time trying to get it to work and needed to get it sorted.

Thanks for the replies
Joe

acejavelin

No problem, glad you found a solution. I did play with a MSL server a little bit over the weekend and could not find a way to easily add the options required anyways.

__________________
Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost.

This is Telephony’s First Law of Equivalent Exchange.

Northeaster

You can set up the Mitel 3300 DHCP server, with different scopes, so that, for example, it hands out the DHCP option 3 (172.16.1.1) to one subnet 172.16.1.0, while also handing out the same DHCP option # 3 (wit ha different value, ie 192.168.1.1) to a different subnet.

The DHCP server will hand out the proper Option 3 info, based on the gateway address of the incoming request. So, for example, the people in the 192.168.1.0 subnet will get option 3 (router address) 192.168.1.1, whereas people in subnet 172.16.1.0 will get option 3 (router address) 172.16.1.1.

So, you could also have more than one option 125, that gives different info to each subnet (ie, you may use the same RTC/ICP address for all phones, but split the TFTP server load, by giving one subnet a different TFTP server address than another subnet).

Under DHCP options, just add a new option 125, with the proper info for the other subnet.