Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mitel VoIP - Lan Requirements & Subnet Question

Status
Not open for further replies.

EllisD

IS-IT--Management
Mar 9, 2004
3
GB
All,

I am a network & telecoms engineer (Avaya & Cisco!!) who has been asked to implement some Mitel 5220 VoIP handsets into our office (site 1). These handsets needs to connect back to a Mitel 3300 switch at a remote site (site 2).

We have ip routing between sites 1 and sites 2, obviously they are on different IP subnets. We have QOS between sites and sufficient bandwith.

I have been led to believe that it would not be possible to implement the solution above as I have been told that the IP handsets have to be in the same VLAN as the 3300 !!!???!

Surely this can't be correct? (I have full control of DHCP at site 1).

Would someone please be able to tell me the exact process, in detail, that an IP handset goes through from connection to a PoE switch through to registration with the 3300.

Even better, point me towards the official Mitel document that describes this in detail....

Many Thanks in advance,

Ellis Dixon
 
Does the Mitel IP Telephone need to be on the same VLAN?:
--> No, as long as there is routing between the VLAN the phone is on and the VLAN the controller is on, the phone will communicate with the telephone. This is really no different then how our friends at Avaya and Crisco work.

Documentation and DHCP Scope Options:
--> Since you have 5220 IP phones, you will need to use scope options 128-130 with 131 and 132. These are all covered within the online help file of the 3300 (HELP is located at the top of the 3300 GUI on the right-hand side).

--> If you can program a Call Manager this will be a walk in the park for you, Mitel is very simplistic.
 
You can Statically assign the phone or use DHCP.

I will assume DHCP

On your DHCP server you will need to add customised scope options 128,129,130 (optionally 132 and 133)

128 - IP Address (3300 controller)
129 - IP Address (3300 controller)
130 - ASCII MITEL IP PHONE (case sensitive)

132 - long VLAN for IP Phone
133 - long Priority on Vlan


The phone will do a DHCP discovery
On delivery of the above options the phone will search for the 3300 controller on the given address and register with same.

If the phone is on a differnet subnet than the 3300 you will need to include a Gateway in the Scope (option 3)

If the phone gets VLAN Info via option 132,133 it will release the first address delivered and do a DHCP discovery on the specified VLAN.

In scenarios where I have done this, I use the IP Helper command to allow DHCP discovery over to the 3300 subnet and have multiple subnets setup on the 3300 for each site.

The 3300 is limited to 10 Subnets (last I checked) so this is limited if your enterprise is larger.

Statically assigning the phone works much the same and is probably prefered if you are doing just 1 or 2 phones.

good luck





*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Kwbmitel - thank you, that's exactly the kind of info I was looking for. One more question:

You say that "In scenarios where I have done this, I use the IP Helper command to allow DHCP discovery over to the 3300 subnet and have multiple subnets setup on the 3300 for each site.

I guess in this scenario you are using the DCHP server built into the 3300 for the voice VLAN?

I had not intended to do this, I will instead be using a Windows DHCP server that will have scopes in the phones default VLAN and in the phones Voice VLAN. I assume that as long as the correct scope options options (128,129,130,132 & 133) are present in both scopes then this will not be an issue.

I would like to avoid using the IP HELPER across these WAN links if possible....




 
You assume correctly, I typically use the 3300 for DHCP on the Voice VLAN if possible.

It is equally valid to use the Network DHCP server for both.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top