Mitel voice and signaling ports 1

[macehkm]

Greetings,

I am in the process of configuring qos on cisco switches with mitel phones. We have Mitel 3300 ip controllers. I am not sure what ports to use to classify voice and signaling for qos?


5061 TCP/UDP SIP-TLS
6800 TCP MiNet Server (at 3300)
6801 TCP Secure MiNet (SSL) (at 3300)
6802 TCP Secure MiNet (AES) (at 3300)
6900 to 6999 TCP MiNet Client (see Note 1)
7011 TCP Data Services access
7050 TCP SDS
8000 TCP MiTAI
8001 TCP MiTAI (SSL)
50000to 50511 UDP Phone Media (post release 8.0) RTP even ports (see Note 2)
50511 UDP Phone voice channel 2
15373 TCP ACD real-time events
15374 TCP IP PMS (Release 6.0)
20001 UDP TFTP
50000 to 50255 UDP Voice Gateway (post-release 6.0)
16320 to 32767 TCP/UDP DECT voice and signaling

 

[danramirez]

Do you need all that for QoS?

I thought you did QoS by the L2 Priority and DSCP Values.

http://www.hatkana.com

http://www.wtelecom.com

 

[Mitelmatt]

I agree with Dan. Set your qos on matching dscp value at layer 3 and cos for layer 2

 

[LoopyLou]

Network QoS settings in a Cisco Environment
A number of higher-end Cisco switches have the capability to monitor both Layer 2 and Layer
3 QoS settings at ingress. They can also modify either of these settings based on the other
setting, as well as changing values, if necessary. Good understanding of these settings is
needed if correct operation is to result throughout the network. To simplify the installation and
use some pre-packaged commands, such as auto-qos, a COS value of 5 is recommended
throughout the network. Other values, such as 6, can still be used, but will require additional
tuning of the configuration at different ports.
In order to make the QoS settings work, the following points need to be considered:
• QoS must be enabled for the entire switch.
• The default COS and DSCP settings of the switch may not be those needed for voice.
• Settings that are needed include:
- Change mapping COS 5 to DSCP of 46 (Expedited Forwarding (EF) setting).
- Ensure that COS 5 is mapped to the EF queue.
- Enable the EF queue.
- Trust incoming ports based on COS value for endpoints, phones, 3300 ICP and voice
servers.
- PC phones may require DSCP remapping as well as DSCP to COS conversion.
- Enable CDP.
• Auto-qos trust will change a number of these settings.
• Some additional tuning may be needed to the settings to get full operation.
Starting in Release 8.0, the 3300 can apply different LAN QoS policies to voice packets,
signaling packets and other packets. Prior to Release 8.0 the 3300 applied the same LAN QoS
policies to all packets. The LAN Policy (QoS) form in ESM is used for setting the LAN QoS
policy values.
In a Cisco based environment the recommended settings are:
• Voice Packets: DSCP: 46, 802.1p:5
• Signaling Packets: DSCP: 26, 802.1p:3
• Other Packets: DSCP:0 802.1p:0

Port Settings
The 3300 ICP is basically a voice server. The network port should be set accordingly, and is
required to provide the following functions:
• Adding 802.1 Q-Tagging and priority (COS) to incoming data (ingress)
• Remove 802.1 Q-Tagging and priority (COS) to outgoing data (egress)
• Provide access to a single fixed VLAN
A typical port configuration example for the 3300 ICP is shown:
Switch# configure terminal
Switch(config)# interface fastethernet0/1
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 2
Switch(config-if)# mls qos trust cos
Switch(config-if)# mls qos cos 5
Switch(config-if)# wrr-queue cos-map 4 5
Switch(config-if)# priority-queue out
Switch(config-if)# spanning-tree portfast
Switch(config-if)# end
Switch#

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[macehkm]

Thanks for the responses.
Currently we use a access-list to identify the traffic. I was hoping to get more granular with it and include the port
for example: access-list 100 permit ip 173.129.0.0 0.0.255.255 any range 16384 32767

CURRNT CONFIG:
I currently cos 6 to dscp 46

class-map match-all VVLAN-PHONE
match access-group 100
class-map match-all SIGNALING_CLASS
match access-group name ACL-SIGNALING


policy-map phone-pc-policy
class VVLAN-PHONE
set dscp ef
class SIGNALING_CLASS
set dscp cs3

access-list 100 permit ip 173.129.0.0 0.0.255.255 any

int range f0/1 - 23
description port access vlan office
switchport access vlan 82
switchport mode access
switchport voice vlan 29
mls qos trust dscp
spanning-tree portfast
spanning-tree bpdufilter enable
srr-queue bandwidth share 10 20 60 10
priority-queue out
service-policy input phone-pc-policy

From the mitel guide listed ports. I wasn't sure on which to use.

5061 TCP/UDP SIP-TLS
6800 TCP MiNet Server (at 3300)
6801 TCP Secure MiNet (SSL) (at 3300)
6802 TCP Secure MiNet (AES) (at 3300)
6900 to 6999 TCP MiNet Client (see Note 1)
7011 TCP Data Services access
7050 TCP SDS
8000 TCP MiTAI
8001 TCP MiTAI (SSL)
50000to 50511 UDP Phone Media (post release 8.0) RTP even ports (see Note 2)
50511 UDP Phone voice channel 2
15373 TCP ACD real-time events
15374 TCP IP PMS (Release 6.0)
20001 UDP TFTP
50000 to 50255 UDP Voice Gateway (post-release 6.0)
16320 to 32767 TCP/UDP DECT voice and signaling

 

[LoopyLou]

Have seen other Cisco deployments where they want to introduce access control lists. Since it can delay can effect voice quality, can you explain to me why it is you want to "get more granular with it"? Just curious.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[macehkm]

MQC offers scalability and flexibility in configuring QoS to classify application classes by using match statements or an extended access-list to match the exact value or range of Layer-4 known ports that each application uses to communicate on the network. This does not cause latency.

 

[LoopyLou]

Some of the ports depend on what applications you have in use. For example ACD real time are only used in ACD deployments and would go from the 3300 to a server setup with ACD monitoring software. PMS is used for hotels to check guests in and out and goes from the 3300 to a server with the PMS. In both these cases the packets travel from the voice network where the 3300 is to the data network where the servers are. Minet is used by the phones for call setup, teardown and in call features. These messages go from the phones IP to the 3300. TFTP is used to download to the phones from the TFTP server which is the 3300 in most cases. Mitai is used for application access to the phones and controller. UDP is typically voice packets ( RTP ). DECT is for wireless DECT handsets, SIP for SIP devices or trunks. The SIP devices can be phones or SIP trunks to a SIP trunk provider or to a third party server running an application ( such as an Exchange server acting as a voicemail ).

Without knowing what you have its hard to say what you need. If you don't have certain features you shouldn't have to worry about those ports. Just be careful not to block something you need.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.