> Yo Cambium, you need to add DSCP 12 (Assured Forwarding) in addition to > DSCP 46 (Expedited Forwarding) to the default VoIP priority > configuration.
That would be a mistake and the wrong thing to do. > We're finding more devices sending SIP packets as AF and > RTP as EF. When a device is mis-configured, why should the burden of dealing with that mis-configurtion as a default fall on another device There is plenty of flexibility to override the wrong setup of a device, if that is they way you want to correct it in your radios... (Which by all standards would be the wrong way to fix it...but more power to you). Two wrongs don't make a right.. Regards. Faisal Imtiaz Snappy Internet & Telecom 7266 SW 48 Street Miami, FL 33155 Tel: 305 663 5518 x 232 Help-desk: (305)663-5518 Option 2 or Email: [email protected] ----- Original Message ----- > From: "George Skorup" <[email protected]> > To: [email protected] > Sent: Saturday, June 6, 2015 10:27:05 PM > Subject: [AFMUG] ePMP VoIP QoS > > Yo Cambium, you need to add DSCP 12 (Assured Forwarding) in addition to > DSCP 46 (Expedited Forwarding) to the default VoIP priority > configuration. We're finding more devices sending SIP packets as AF and > RTP as EF. AF isn't prioritized and out-of-band signaling (prompts, etc) > are sent as SIP messages so sometimes these are getting dropped, not to > mention registrations, invites, etc. And more devices are stupid (mostly > Grandstream), they only let you set ONE priority value for the entire > device. These are coming default as DSCP12/AF. I've tried to get > everyone to change this to 46, but they don't remember. > > Or just apply the whole Canopy DiffServ table. We've never had to change > any of those code points. Turn HP on, it just works. >
