• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 801
  • Last Modified:

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?

Thanks!
0
digitalwav
Asked:
digitalwav
  • 2
  • 2
1 Solution
 
convergintCommented:
LLDP-MED can be used to assign a VLAN but since you say there are no VLANs configured it looks like the phones are either statically assigned or are preconfigured to only accept DHCP from the Mitel PBX offsite.

If you do want to configure them with LLDP assigning them VLANs this is the link to the article: http://h17007.www1.hp.com/docs/interoperability/mitel/4aa2-1398eee.pdf

As for the second part of your question, it doesn't seem like there is a gateway configured on the phones to route outside it's subnet.  Or if there is a gateway configured, there are no routes setup by your provider to route where you need them to.

MPLS can be setup by the provider two ways, either they provide a layer 2 configuration where you need to provide your own layer 3 switches and program all the routing.  Or in a layer 3 configuration where they do the routing on their end and you need to tell them what to route and where.  

You really need to speak with your ISP/PBX provider's technical support and determine exactly what they have configured for you.

Our setup is similar except we do not use an offsite phone provider.  I configured our HP switches to have a dedicated voice VLAN with DHCP ip helper addresses, ports are tagged for this VLAN.  Then we have DHCP running on a server that hands out the addresses and the VOIP configuration to the phones.  We have layer 3 HP switches that handle the routing between our MPLS sites as our provider is a layer 2 provider.  To give you a simple breakdown, our setup is like this:

VLAN 2 Subnet (site1/site2): Corporate 192.168.2.x and 192.168.12.x
VLAN 3 Subnet (site1/site2): VOIP 192.168.3.x and 192.168.13.x
VLAN 10 MPLS Subnet for routing: 10.10.10.x

Gateways configured on switches for each VLAN.
Site 1, VLAN 2-192.168.2.1, VLAN 3-192.168.3.1, VLAN 10-10.10.10.1
Site 2, VLAN 2-192.168.12.1, VLAN 3-192.168.13.1, VLAN 10-10.10.10.2
MPLS connections plug into VLAN 10 of each switch.

Site 1 switch will have a manual route for 192.168.12.x and 192.168.13.x via gateway 10.10.10.2
Site 2 switch will have a manual route for 192.168.2.x and 192.168.3.x via gateway 10.10.10.1

Each device on their VLAN gets from the DHCP server the respective gateway.
0
 
digitalwavIT Infrastructure ManagerAuthor Commented:
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....
0
 
convergintCommented:
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.
0
 
digitalwavIT Infrastructure ManagerAuthor Commented:
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.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now