Avatar of digitalwav
Flag for United States of America asked on

Mitel Phones with HP Switches, NO VLANS and a 3rd Party VoIP Provider

I have a new position and my first priority is to figure out how everything is configured. I'm working on the phones right now.

I've discovered the following:
Mitel IP Phones from Broadview (model 5224 for the most part)
Dedicated T-1 for the phones (Fairly certain of this)
There are NO VLANs configured on any of the switches
The phones show up in the HP switches under the LLDP Remote Devices with 10.160.x.x addresses (not used on any of my LANS)
1 port on 1 switch is plugged into the router provided by Broadcom
The T-1 mentioned earlier has public addresses assigned to at least one interface, however there are TWO T-1 lines going into it. (I doubt they are bonded so we may actually have one internet and one private circuit in this router, as I don't have console access I have no idea how it's configured other than what it's plugged into)

I'm assuming that the phones are getting their information from an LLDP broadcast, picking up their private IP and going on their merry way.

First question- Here's what I don't get. Is LLDP used in place of a VLAN? I don't seem to have any access to the IP addresses the phones are getting and the PCs plugged into the phones operate as expected on my own LAN addresses.

I've always done this with a separate VLAN for the VoIP traffic but this seems to work with no need to mess with the switches and ports.

Second question and most imporant- I would like to extend the phones to be able to work on other routed subnets on my campus. Right now we have POTS lines in the remote areas. I have to assume this has to do with LLDP not crossing routers or VPNs? Correct? How can I get around this?

One area on campus uses an MPLS line and two routers. Data moves fine, phones obviously don't work. I'd love to be able to route this to some of our VPN'd locations too.

Any ideas or directions?

Internet ProtocolsVoice Over IPRouters

Avatar of undefined
Last Comment

8/22/2022 - Mon

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

I'm starting to get this now....the switches are handling the routing (via layer 2?) not the firewalls/routers in the traditional way. Is this correct?

We use all HP switches (Procurve 2500 series and a few (yuk) 1900 series) and SonicWalls for FW/VPN. I'm not certain how the MPLS is configured. I know we provided the routers and their config appears to be pretty normal- 192.168.200.x on our side and 172.16.16.x over the WAN side.

I'll have to call the VoIP provider. I was hoping to avoid them as their support seems to be geared towards "how do I forward my phone" as opposed to network engineering....

2500s are not layer 3 switches and hopefully the 1900s are not doing the routing as they are pretty terrible at it.

I'd bet that the SonicWalls are doing the routing if you say that the WAN side is 172 subnets.

The LAN side of the VoIP circuits are 10.160.x.x  As near as I can tell the 2500s are sending the phones to the respective ports. I can't see any other way for them to be getting IP addresses in that range. There is nothing set in my DHCP servers to direct them. The LLDP clearly indicates that the phones have the 10.160.x.x addresses and they also clearly identify the port on the switch that has the VoIP circuit plugged into it.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck