ProCurve 2610 not showing any tags for Avaya phone's signaling packets

[Vince-Whirlwind · Accepted solution]

Yes, 802.1p is not useful for this issue.

Just to clarify: 802.1p tells the *switch* which switch buffer to put each *frame* in when it is *switching* them.

As long as you don't have any switch interfaces running at 80%+, and consequently dropping frames, then .1p isn't doing anything for you.

Your concern is Layer3 QoS, which is how the *packets* are *routed*. And this is only important on the contended infrastructure belonging to the WAN provider.

Your packet captures seem to be indicating you have everything tagged correctly. Sound like something somewhere is (correctly) not agreeing with your DSCP marking "46" being applied to signalling packets.

Ultimately, the cause of your issues is the failure of your WAN provider to offer the standard class-of-service split for traffic that I would expect them to.