Are you saying that my other 4 scopes need teh option 43 and NOT the VIOIP VLAN?? Do i need to add 125 and 128 as well? If so they have never been there.
No, that is not what I am saying, I think I got too complicated, let me try to simplify a little with some examples...
VLAN 1 - Native data VLAN (10.0.0.0/24) Default untagged VLAN on end-user switch ports
VLAN 3 - Dedicated Public WiFi VLAN (172.16.0.0/24) Dedicated switch ports for dual SSID AP's
VLAN 6 - Voice VLAN (192.168.0.0/24) Allowed as tagged traffic only on all end-user switch ports, 5000 is at .2
When the phone is connected to LAN initially it will request DHCP in the untagged VLAN, a proper Option 43 in the scope of 10.0.0.0/24 (the native data VLAN) would look like this:
id:ipphone.mitel.com;sw_tftp=192.168.0.2;call_srv=192.168.0.2;vlan=6;l2p=6;dscp=46Now the phone will accept and then release this DHCP offer to the DHCP server because it got a valid string with vlan variable information, and it will start adding a VLAN6 tag with L2Priority set to 6 to all of it's packets and make a new DHCP request. Your IP HELPER settings and appropriate routing should present the request to your DHCP requesting an IP address from the 192.168.0.0/24 scope (Voice VLAN 6), it should respond with this as a proper Option 43:
id:ipphone.mitel.com;sw_tftp=192.168.0.2;call_srv=192.168.0.2The phone now knows it is in the correct VLAN since there is no vlan variable in Option 43, it will continue to use VLAN6 and L2Prio 6 and attempt to contact the server at 192.168.0.2, assuming all routing and provisioning is correct the MiNET link and all communication should come up to the phone.
The scope for VLAN 3 could contain an Option 43, if for some reason a phone would do it's initial request in that VLAN, and it would contain the same information as VLAN1's option 43, if a phone will never boot in that VLAN then there is no reason to have Option 43 defined in that scope.
You only need ONE type of optioning in DHCP for the Mitel phones, either 43, 125, or 128-132, not all of them. You potentially could use Option 43 in one VLAN, Option 125 in another, and Options 128-132 in a different one, but you should not use multiple types of optioning in the same scope.
Note that in older versions of software and firmware, the VLAN/L2P variables were checked against the phones current settings, and if they were the same the phone would ignore them, so for a long time techs made the Mitel provisioning DHCP options the same in all scopes, this changed in newer phone firmwares and system software releases.