Late Saturday night only 3 phones not working, okay I can deal with that. What I notice is that the phones that stopped working were only the version phones and it appears that they stop working when their DHCP lease expires. Tuesday - 10 phones stop working. Life is great!!! LLDP is a discovery protocol and it sounds like the implementation of it on those HP switches might be incompatible with your Mitel phones.
We ran into something similar trying to use Mitel phones on Cisco switches. They simply refused to work in dual-port mode, where the cable goes to the phone and the computer daisy chains off the phone. In the end, we just used two separate ports.
Steve Friedl's Unixwiz.net Tech Tips
As for QoS, it's tertiary function is to ensure calls don't get dropped but the more important function is to ensure real-time applications like live voice and video don't experience lag or dropouts. If your network is designed properly and the bandwidth is there, QoS should only improve service to those QoS "protected" services, not make everything else run poorly.
Again, that's assuming you had enough bandwidth to start with. Just want to point out that the HP is an L3-capable switch. It'll boot up as L2 unless you enable it specifically.
That would be nice - unfortunately we didn't have a budget for that. Plus its only 25 phones total. I take it that hasn't helped? We built a whole separate physical network for the phones. Their own switches, their own cable drops to the desks.
We never have any networking issues with them, Considering that you have done this, I'm very interested in what you see as the remaining advantages over non VoIP based voice services? QoS works by slowing down the traffic with a lower priority to give the traffic with a higher priority more breathing room, I don't want traffic slowed down, and QoS to me is just another complexity and headache to deal with.
Thanks Phillip that makes more sense to me now. Sorry to hear of your bad experiences with the phones affecting devices connected to them, I've never experienced that kind of problem. QoS won't slow anything down, it just gives priority to voice forwarding those packets before something less important and as voice really is not even enough bandwidth to call background noise on Mbps link it doesn't result in anything slowing down. It really just protects you from someone totally saturating the link and affecting voice quality but I promise you it doesn't slow anything down in any measurable way, rather sends it in a different order of priority.
QoS won't slow anything down, it just gives priority to voice forwarding those packets before something less important.
To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Sunday - 5 Phones not working Monday morning - 7 Phones not working What I notice is that the phones that stopped working were only the version phones and it appears that they stop working when their DHCP lease expires.
HPFollowers Follow. Mitel 2, Followers Follow. Best Answer. Popular Topics in General Networking.Lately I had a new challenge with configuring MAB. These time a single switch port is shared by an IP phone and a workstation. The IP phone is used as a kind of switch. The backend switching network is build on Cisco Catalyst switches. The IP phones used in this situation are Mitel phones. The customer would like the MAC addresses of both devices verified against a central database.
The account name and the password are exactly the same and equal to the MAC address, like f22def. I made the account for the IP phone member of the voice group and the account of the workstation member of the data group. The configuration of IAS is straightforward. I added the switch as radius client and configured a radius policy for the data connections. This works without any problems. The screenshots below show the most important configuration of this policy.
I configured another policy, exactly the same, for the voice components. I disconnected the workstation and connected the IP phone to the network. This also works without any problems. The IP phone is authenticated and allowed access to the network. Next I connected the workstation to the IP phone and booted the workstation.
I noticed that the IP phone lost his power and checked the switch port status. The switch port went in err-disable state with the following message:. Multiple Domain Authentication MDA allows both a data device and a voice device, such as an IP phone Cisco or non-Ciscoto authenticate on the same switch port, which is divided into a data domain and a voice domain. This feature is configured with the authentication host-mode commands and is very useful when combining IEEE The following host-modes can be used:.Common realtor lock box codes
Single-host mode should be configured if only one data host is connected. Do not connect a voice device to authenticate on a single-host port. Voice device authorization fails if no voice VLAN is configured on the port. Multi-domain mode should be configured if data host is connected through an IP Phone to the port. Multi-domain mode should be configured if the voice device needs to be authenticated.
Multi-auth mode should be configured to allow up to eight devices behind a hub to obtain secured port access through individual authentication.
Only one voice device can be authenticated in this mode if a voice VLAN is configured. Multi-host mode also offers port access for multiple hosts behind a hub, but multi-host mode gives unrestricted port access to the devices after the first user gets authenticated. I tested the multi-host configuration and it did exactly as explained above.
Only one device is authenticated and all next device are allowed without authentication. In my situation I have to use multi-domain.Weedho jacayl
I added the configuration line authentication host-mode multi-domain to the interface configuration above. After this I had a new problem. Back to the drawing table and I found the solution in the radius configuration. I configured the radius attribute cisco-av-pair in order to tell the switch that the IP phone is allowed on the voice VLAN, see the picture.
The following steps are taken during the process:.Location: United States.The rate of dissolving ultimately depends on
Find business voice over IP VoIP phones ranging from entry-level phones to sophisticated IP phones and devices with cordless handsets, headsets, speakerphones and attendant consoles. With Mitel's Open Solutions portfolio - including open standards desktop phones, accessories, conference phones and mobility devices — you get the flexibility to choose the devices that best suit your needs and work with your third-party platforms.
Mitel SIP phones offer exceptional features and flexibility in an open-standard enterprise grade IP telephone. Need Remote Working Solutions? Questions or Comments? Learn Blog See All Posts.
Careers Find Jobs Internships. Resource Center See All Resources. Search Mitel. Blog Login Location: United States. Mitel offers a range of IP and digital phones, consoles, conference phones and peripherals tailored for executives to everyday employees for business of all sizes. Conference Phones.
Open Solutions Portfolio. Wireless Devices. Ready to talk to sales? Contact us. Find a Partner Email Us.Randomly one user's phone will reboot stalling at "Waiting for DHCP" and will stay there until I move the patch cable from their port on the switch to an open port, or I reboot the whole switch.
This has happened on three different switches here. In that previous post the wiring was blamed but it just happened on one of our newer lines. Thanks, everyone for your input on this, the problem I was having had seemingly disappeared but reappeared late last week.
I was working in the CLI when I noticed what was happening. The port security was being tripped and blocking the phone traffic but not the traffic on the ethernet pass-thru, they were also set like this in a pattern.
All three switches set the same, by the same company, likely using a template. I unlocked the port and set the port security to the same settings Classic Lock vs Limited Dynamic Lock as the ports not giving us a fit and so far everything seems to be good. Classic Lock—All learned MAC addresses on the port are locked, and the switch learns up to the maximum number of addresses allowed on the port defined by Max No.
The learned addresses are not subject to aging or relearning. After the limit is reached, the switch does not learn additional addresses. In this mode, the addresses are subject to aging and relearning. There are mitel experts that handle questions from users.
If you need even more help you can join the mitel usergroup. OK, so I saw where you said they were on the same switch. That is where I would start.
Mitel IP-Phones via LLDP-MED not join the VLAN
Do you have a spare that you can test with? Better yet, move those users to another switch in the stack. Print running config on that switch and compare to another. I know I'm stating the obvious, but DHCP could be on the phone system itself or a windows server The phone system is managed by a 3rd party, but should have plenty of DHCP addresses available. The phones are on their own vlan and get DHCP from the phone system server.
Do we know if voice traffic is being routed to the data VLAN and vice-versa? I don't really see a reason for this other than for management of the voice VLAN from the data VLAN by the admins and there are better ways to do that.
And IIRC even with static routes configured in a loop and they have to be so that traffic can get to and from both networks This is unlike Layer 2 where there is no TTL so a loop is catastrophic. But hey, who turns off spanning-tree? Bottom line is spanning-tree layer 2 can't block routing loops which are layer 3.
Need Remote Working Solutions?
This is networking Why would the switch lose it's VLAN settings? As long as the settings are saved, what else would cause this? My only observation here is the SG switch uses Smartports which I don't think work very well when trying to have voice and data VLAN's on a single interface.
I would disable the Smartport feature and do the config manually, assuming the Smartports are actually in use. Are they? One of the principles behind using the voice vlan settings on Cisco switches is it allows an access interface to connect to two VLAN's.
The catch is one VLAN is expecting untagged traffic and the other is expecting tagged traffic. Most IP phones have the ability to tag their own traffic whilst leaving PC data traffic passing through the phone un-tagged.
If this was all-Cisco then CDP takes care of that.Log In. Thank you for helping keep Tek-Tips Forums free from inappropriate posts.Qopenvpn arch
The Tek-Tips staff will check this out and take appropriate action. Click Here to join Tek-Tips and talk with other members! Already a Member? Join your peers on the Internet's largest technical computer professional community. It's easy to join and it's free. Register now while it's still free! Already a member? Close this window and log in.Digitalocean unable to resolve host
Join Tek-Tips Forums! Join Us! By joining you are opting in to receive e-mail. Promoting, selling, recruiting, coursework and thesis posting is forbidden. Students Click Here. Using Mitel phones with Know we have a customer wanting to use Does anyone have the setup for the Cisco switches in order to have the Any info appreciated. I'd say this is a question for Cisco branch of this forum.
You can find lots of examples on www. Hi Sponge, Setting up a cisco network for Setting up Basically a Mitel phone is a cisco phone as they both use the same protocol SEP. Thanks, I'll take this away and try. I should not be so "smart-ass" with my comments. I just hate how people think Cisco is so great. Just because they charge huge dollars and use that money on marketing, does not mean they have the best product.
It is no where near the quality of Mitel, Nortel or Avaya. MitelGuy, maybe not clear in my description. No doubt about Mitel IPT So do you guys think it's just a fluke that CISCO has sold more IP handsets that avaya, nortel or mitel the past few years and the number is rising?
And let's not talk about network gear. If you are trying to compare avaya, nortel or HP with the product and support that cisco provides, then this is not even worth discussing. Who's Mitel's preffered switch gear these days anyway? They've gone from extreme to HP and back a few times if I recall correctly. Don't mean to rattle any cages but you pay for what you get and that's the reason cisco is more expensive, not just because. People would not buy it if it was not worth the money.
Not to knock the rest of the products as they all work fine.Log In. I hate all Uppercase I don't want my groups to seem angry at me all the time! Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action. Click Here to join Tek-Tips and talk with other members! Already a Member? Join your peers on the Internet's largest technical computer professional community. It's easy to join and it's free. Register now while it's still free! Already a member? Close this window and log in. Join Tek-Tips Forums! Join Us!
By joining you are opting in to receive e-mail. Promoting, selling, recruiting, coursework and thesis posting is forbidden. Students Click Here. So we are going to be getting a Mitel solution with a ICP and and phones. I can't really find any solid documentation online regarding this. Thanks ahead of time. I would not rely on auto-qos designed for and by different manufacturer.
The typical solution is to use voice VLAN which is recognized by the phone in vendor specific options, so any other device will just ignore it.A customer recently purchased a Mitel phone system with IP phones, and though there was no VoIP external to our network, we still had to do a fair amount of work to get the phones to play well internally.
Mitel had no resources at all for how to do this, so I'm memorializing this to help the next guy. It's likely that this will be somewhat applicable to other phone vendors.
Most IP phones are designed to use Power over Ethernet PoEwhich means that power is supplied by the network switch in the computer room rather than by a power brick plugged into the wall near the phone itself. This helps keep the user's desk a lot neater by eliminating one of the power sources. In addition, rather than require a separate network cable for the phone alongside the cable for the user's computer, most IP phones have a tiny built-in network switch that rides a single network cable to the computer room and supplies a network connection to the PC plugged in behind it.
This saves the enterprise from an intrusive and potentially costly rewiring project. Surprisingly to me, at leastthe phones even support the notion of putting the phone on one VLAN and the PC behind it on another, allowing for a segregation of the network. Apparently this is a common feature. Selection Tip : the phones themselves don't need a speedy network connection, so Fast Ethernet megabit is plenty fast, but the device behind the phone might need more.
But considering that GigE phones and the GigE switches they plug into are both substantially more expensive than FastE versions, it may well be that your office users can live with FastE to their desktop. Ours could. This took some doing. As noted, Power over Ethernet goes a long way to making the user's desktop area neater than it otherwise would be, as it largely avoids a power brick aka "wall wart" among the other clutter.
But there are lots of options here, including quite a few ways to make a mistake. As one would expect, there are many ways to integrate these phones into a larger network, with the "easiest" being to configure them with a static IP on the same subnet as the rest of the network, as this avoids having to deal with DHCP or VLANs, but we really wanted to do it properly. Unfortunately, we found that Mitel had very few resources for us so we had to navigate this almost entirely on our own.
We used our internet firewall to route between the two subnets, though others may use a layer3 switch for this purpose. Though the phone traffic itself doesn't need to travel between the two networks, the phone-control application on the user's PC will need to talk to the phone system.
Instructions for Cisco devices look like:. This is not only convenient, but it provides tight integration with DNS which we care about. At this point, the DHCP server should be prepared to offer the special Mitel options to any Mitel phone that asks for an address, no matter which subnet it asks on.
When the DHCP server gets the packet, it knows that it wasn't broadcast - it's coming from the inside address of the firewall - but it uses the DHCP relay address inside the packet to select a scope and send the reply. It's a clever system that I nevertheless couldn't get to work, and since I had a NIC to spare, probably won't revisit it. But other environments probably should.
DHCP relay started to work when I insured that all phone switchports to be in trunk mode; it's not clear why this needs to be, but it made the difference for DHCP relay mode. These are the steps that the phones take to boot, and the fact that it requests a DHCP address twice was the final piece of the puzzle to allow us to understand this.
It was very, very frustrating trying to figure this out. This Tech Tips was created strictly to document on particular experience on one particular customer's network, but it seems likely that Mitel is not the only phone system that works this way.ShoreTel Mitel: IP480/IP485 - Unboxing and Setup of the latest voip phones for Mitel MiVoice Connect
As we learn of other configurations that work in a similar way, we'll document them here. Blogged here. Does this site look plain? This site uses advanced css techniques. Steve Friedl's Unixwiz. Click to enlarge.