Jabber and Meida Interface Service - Switch port

Question

Hi All,
here is from Cisco:
Before Cisco Jabber for Windows sends audio media or video media, it checks for Cisco Media Services Interface .
• If the service exists on the computer , Cisco Jabber for Windows provides flow information to Cisco Media Services Interface . The service then signals the network so that routers classify the flow and provide priority to the Cisco Jabber for Windows traffic.
• If the service does not exist, Cisco Jabber for Windows does not use it and sends audio media and video media as normal.
My Question is : what does normal means?
1- we can identify ports for Jabber in CUCM, then create ACL and apply QoS.in that Case what " Normal Traffic " means?
2- for MSI, do we need to configure anything on the switch port to work peoperly?
3- How switch knows which Qos to apply based on what MSI saying? still needs an ACL, if yes, what s apoint of using MSI dfor Qos?
Thanks,
Hamed

Answer 1

This would be EF for voice, AF41 for video/voice, and CS3 for SIP signal. Two things typically cause this to get treated as best effort:
The Windows PC is not allowing the application to set DSCP markings. Group or local security policy can be used to allow this
The switch is not trusting the data VLAN. Most SRND material suggests using a policer to limit the amount of EF/AF41/CS3 traffic from the data VLAN and to remark the violation traffic to best effort.
You'll want to start with the MediaNet Deployment Guide. There is a lot going on to make this work.
The MSI tells the switch what application and ports are being used. The switch then sets the DSCP marking on that traffic.
Please remember to rate helpful responses and identify helpful or correct answers.