Problem with hi priority chanel

Products PMP
1

Hello!

I am using Canopy 5.4 Ghz point-to-multipoint link. I want to use hi priority chanel for VoIP trafic, but Im not sure if it is working. Right now Im testing this configuration in lab. I have enabled this hi priority chanel, set hi priority CIR to 200 kbps, DiffServ codepoints are default. I use seperate Vlans for ordinary trafic and VoIP, everything works, but in my AP Statistics=>Data VC VC:255 shows all 0, and only VC:018 is changing. Is there some special configuration to make VoIP traffic go trough Hi priority chanel? Please give some advice.

thanks,
Rudolfs

2

Are you tagging your VoIp traffic as it comes in to the radio? Either through DSCP, CoS/ToS or VLANs?

3

I`m using Vlans. One Vlan ir for Data and Canopy management, and the other one is for VoIP only.

4

I have tested, but tagging the packets on the ip phone/ata.
I dont think canopy platform recognize specific vlan for voip

5

I also use priority channel by tagging VOIP packets using DiffServe.
I configured DiffServe codepoint on my ATA & Ip phones and on my core router (packet incoming from VOIP server).
“Data VC Statistics” page shows both traffic correctly.

6

Can anyone give me detailed configuration on your configuration. What is your setings in difserve and Vlan tabs on your AP and SM. Maby my Canopy configuration is the reason why canopy isn`t recognising VoIP trafic.

7

I did NOT use vlan tagging.

I configured on the SM:
QoS -> Hi Priority Channel -> Enabled
Hi Priority Uplink CIR : 80 kbps
Hi Priority Downlink CIR : 80 kbps

On the ATA / IP PHONE I configured:
SIP QoS (Diff-Serv): 46

On the SM the codepoint 46 has default priority=4, which is enough to use hi-priority channel (0-3 low, 4-7 high).
(you can of course choose any other code, but check the priority)

On the core router you should also tag the incoming packets from voip server (based on ip policy or layer7 filter) with codepoint 46. This way, the traffic going to the SM will be prioritized as well.
The same should be done on any switch/router on the path, since they should be able to classify such traffic.