cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2088
Views
0
Helpful
4
Replies

QoS for softphone

leepeiwai
Level 1
Level 1

Hi,

We will like to prioritize voice traffic for all softphones.

The PBX is hosted at vendor's site, so we connect the softphone to an external IP of the PBX.

I have scripted something below but not sure how to apply to interfaces as softphones are installed on user computers.

Softphones and PCs are on same subnet.

ip access-list extended QoS-ACL-01

permit ip 0.0.0.0 0.0.1.255 9.9.29.1

class-map match-all QoS-CM-01

match access-group name QoS-ACL-01

!

policy-map QoS-PM-01

class QoS-CM-01

  set dscp ef

!

interface ???

service-policy input QoS-PM-01

Do I have to apply "service-policy input QoS-PM-01" to all interfaces?

Cheers,

Hannah

4 Replies 4

Joseph W. Doherty
Hall of Fame
Hall of Fame

Disclaimer

The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.

Liability Disclaimer

In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.

Posting

You might, if the softphone is incapable of marking packets itself.

Other possible options might be to mark on egress uplink and/or mark in ingress vlan.

Hi Tomas,

9.9.29.1 is the PBX host, traffic destined to 9.9.29.1 is only for VOICE.

What is voice RTP?

What if I just implement on uplink?

Cheers

Tomas Fidler
Level 1
Level 1

If you implement this policy as input policy, then it should be implemented on all interfaces (subinterfaces in case of VLAN) from where "policied" traffic is expected to arrive.

Looking on your ACL, there is a little bug... the rule should be more like this:

   permit ip 192.168.0.0 0.0.1.255 host 9.9.29.1

Be aware, this rule will mark all traffic to host 9.9.29.1 as EF, even other then VOICE packets... you can try to use NBAR to recognize just voice traffic and mark just voice RTP packets as EF.

I have applied "service-policy input QoS-PM-01" to the uplink interface and notice there is no packet matching to the policy.

But I do have packets matching the ACL for destination host 9.9.29.1.

Can someone explain what is going on?

Router887#sho policy-map int fastethernet0

FastEthernet0

  Service-policy input: QoS-PM-Voice

    Class-map: QoS-CM-Voice (match-all)

      0 packets, 0 bytes

      5 minute offered rate 0 bps, drop rate 0 bps

      Match: access-group name QoS-ACL-Voice

      QoS Set

        dscp ef

          Packets marked 0

    Class-map: class-default (match-any)

      0 packets, 0 bytes

      5 minute offered rate 0 bps, drop rate 0 bps

      Match: any

Router887#sho policy-map int dialer0

Dialer0

  Service-policy input: QoS-PM-Voice

    Class-map: QoS-CM-Voice (match-all)

      0 packets, 0 bytes

      5 minute offered rate 0 bps, drop rate 0 bps

      Match: access-group name QoS-ACL-Voice

      QoS Set

        dscp ef

          Packets marked 0

    Class-map: class-default (match-any)

      457476 packets, 422425397 bytes

      5 minute offered rate 435000 bps, drop rate 0 bps

      Match: any

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: