9200 "network-policy profile" needed for auto VoIP Qos on uplinks?

[train00wreck]

Hello, I am trying to help a new client resolve their VoIP issues of phones cutting in/out. The phones are Yealink phones and are connected to Catalyst 9200 switches, which then uplink to 2 core 1300 switches. Right now I have configured a separate VLAN for the phones because there was none before. I then put a network-policy profile of "voice vlan 228 cos 6", then under each interface that contains a phone i have "network-profile 1" and "auto qos voip trust". The phones automatically put DSCP 46 on their traffic. I can see the VoIP traffic going into the highest 2 queues when i do a "show platform hardware fed switch active qos queue interface <phoneinterface>", but I am wondering whether the uplink port that goes to the core switches needs the same profile and auto qos settings. At the moment the voice issues are persisting so I think it may be necessary. Any guidance would be appreciated.

[M02@rt37 · Accepted solution]

Hello @train00wreck 

You must ensure end to end qos consistency. So, enable dscp trust on the uplink ports from the c9200 to the core and on the coresponding core ports so that DSCP 46 markings from the Yealink phones are preserved across the network...

Voice vlan and network-policy profiles stay only on access ports, not uplinks. And if EF is being remarked or dropped, the audio will sufer, so verify dscp 46 is seen on all hops and confirm WAN or internet edges also prioritize EF trafic, since uplink or WAN congestion, not access-layer config, usually cause the voice dropouts !!

[Joseph W. Doherty]

I believe a 9k port will, by default, trust DSCP markings and use different queues.  However, by default, the uplink port might not be providing EF PQ treatment.

That aside, as M02@rt37 already noted, QoS is recommended end-to-end, so what happens at the 1300s, and beyond?

[train00wreck]

Hello all thanks for the replies. Yes, enabling auto qos on the uplinks appears to have resolved the issue. No phone problems have been noticed since then. Apparently the switch is using Auto QOS version 4.0, according the config file lines that get automatically added. Thanks again!