1
Mitel MiVoice Business/MCD/3300 / Re: Mitel QOS with Cisco Switches
« on: January 28, 2013, 09:00:05 AM »
I have a similar setup - however my 100mbps is not on mpls.
On the port where 3300 is connected i have:
***************************************
interface GigabitEthernet0/45
description MN3300 Controller
switchport trunk encapsulation dot1q
switchport voice vlan 30
priority-queue out
mls qos cos 5
mls qos trust cos
spanning-tree portfast
!
***************************************
Also on the same switch i create the dscp-qos map and enable qos
***************************************
mls qos map cos-dscp 0 8 16 26 32 46 48 56
mls qos
***************************************
Now for port (voice and data I do)
interface GigabitEthernet0/26
switchport access vlan 10
switchport trunk encapsulation dot1q
switchport mode access
switchport voice vlan 30
priority-queue out
mls qos trust cos
spanning-tree portfast
!
****************************************
For the trunk ports add this statement on top of your trunk config:
priority-queue out
mls qos trust cos
The trunk port between the switches across locations is the same config as for switches between sites - however you must ensure Telus honour the dscp-qos settings you are sending across.
Now here is a little tip I can offer regarding Telus - Blame it on them - You should not have voice problems on a 100MPBS link unless you are always saturating it however being MPLS I would say you should not be experiencing any voice issues at all. In my opinion dealing with carriers they implemented they have to fix - they have cisco and mitel resources they can consult to ensure your QoS is working across sites - Even if i knew cause/fix i would dump the problem on them:
" Hey - you like to take my hard earned dollar every month for this connection - now that i have a problem you should do everything you can to fix it "
Good luck!
On the port where 3300 is connected i have:
***************************************
interface GigabitEthernet0/45
description MN3300 Controller
switchport trunk encapsulation dot1q
switchport voice vlan 30
priority-queue out
mls qos cos 5
mls qos trust cos
spanning-tree portfast
!
***************************************
Also on the same switch i create the dscp-qos map and enable qos
***************************************
mls qos map cos-dscp 0 8 16 26 32 46 48 56
mls qos
***************************************
Now for port (voice and data I do)
interface GigabitEthernet0/26
switchport access vlan 10
switchport trunk encapsulation dot1q
switchport mode access
switchport voice vlan 30
priority-queue out
mls qos trust cos
spanning-tree portfast
!
****************************************
For the trunk ports add this statement on top of your trunk config:
priority-queue out
mls qos trust cos
The trunk port between the switches across locations is the same config as for switches between sites - however you must ensure Telus honour the dscp-qos settings you are sending across.
Now here is a little tip I can offer regarding Telus - Blame it on them - You should not have voice problems on a 100MPBS link unless you are always saturating it however being MPLS I would say you should not be experiencing any voice issues at all. In my opinion dealing with carriers they implemented they have to fix - they have cisco and mitel resources they can consult to ensure your QoS is working across sites - Even if i knew cause/fix i would dump the problem on them:
" Hey - you like to take my hard earned dollar every month for this connection - now that i have a problem you should do everything you can to fix it "
Good luck!