Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: magnus on January 07, 2021, 02:29:12 PM
-
my customer has been rebuilding their infrastucture and switching from HP switches to Meraki switches.
Release level: 8.0 SP2
Active software load: 14.0.2.26
Inactive software load: 13.1.0.36
System relink: No relink has been applied.
Call Control relink: No relink has been applied.
Platform: MXe
512MB of RAM
If we plug a phone into the meraki switch it does not connect. But if we move that phone to the existing HP switches it connects immediately.
This is what the dhcp options are configured to and the IT guy tells me that is how the meraki is configured t match.
ID Name Value Format Scope Vendor ID ID
3 Router 10.10.1.254 IP Address Global 3
6 DNS Server 10.10.1.254 IP Address Global 6
125 Mitel id:ipphone.mitel.com;sw_tftp=10.10.0.2;call_srv=10.10.0.2;vlan=10;l2p=6;dscp=46 ASCII String Global 1027 125
128 TFTP 10.10.0.2 IP Address Global 128
129 RTC 10.10.0.2 IP Address Global 129
130 MITEL IP PHONE MITEL IP PHONE ASCII String Global 130
134 Diff Service Code Point 46 Numeric Global
Can someone tell me what we are missing to make the phones work on the new switches?
-
Need to provide more detail on the failure. Do the phones not get DHCP, or just fail to connect to the MiVB?
-
They do not get dhcp
-
What kind of phones, 53xx or 69xx?
The phones are in the same subnet? Dhcp relay ?
Hp use lldp, and cisco Cdp.
Basically, you need only option 3 and 125
-
Meraki switches do not support "auto voice vlan" so essentially you need to make a custom option in the default VLAN's DHCP scope for Option 125, this will tell the phones to "jump" VLANs to the voice VLAN, or to make it easier, use option 43 using the same string as option 125 (but it doesn't need to be an encapsulated option, it can be plain text).
This is typically why we don't use Meraki switches in any voice deployment network, no CDP/LLDP auto VLANing. Cisco small business series (for example) handles this 10 times better than a Meraki MS switch.
-
I think that option 125 won't work as ascii as it doesn't have the vendor code or string length values that and encapsulated value would I agree to use 43 on the default vlan in your case
-
I think that option 125 won't work as ascii as it doesn't have the vendor code or string length values that and encapsulated value would I agree to use 43 on the default vlan in your case
That is what I meant, to use option 43 so as not to worry about those things, but I guess it wasn't very clear.
-
That is what I meant, to use option 43 so as not to worry about those things, but I guess it wasn't very clear.
On the same page my friend, just thought I'd add what I saw