Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: NSP

SP QoS Service Class

 

 

Cisco nsp RSS feed   Index | Next | Previous | View Threaded


travis.marlow at everestgt

Nov 12, 2009, 7:22 AM

Post #1 of 2 (370 views)
Permalink
SP QoS Service Class

I'm trying to plan for a QoS implementation for an Internet Access provider.
I just finished reading RFC 4594 and it recommends VoIP signalling traffic
be marked CS5. Every other reference I have seen always has it at AF31 or
CS3. Is anyone else using the RFC recommendation? Would any SP be willing to
share a general configuration for service classes they have defined.

Sorry for the duplicate, I sent from the wrong email address before.

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


jason at pins

Nov 12, 2009, 12:39 PM

Post #2 of 2 (334 views)
Permalink
Re: SP QoS Service Class [In reply to]

Travis,

This map has worked pretty well for us. The idea behind splitting out
RTP from signaling is if signaling doesn't get through, the call will
drop. I welcome constructive criticism. :)

class-map match-any Core_Voice_Signaling
match access-group name Core_Voice_Signaling
class-map match-any Core_Voice_RTP
match access-group name Core_Voice_RTP
!
policy-map voice
class Core_Voice_Signaling
bandwidth percent 5
class Core_Voice_RTP
priority percent 70
class class-default
fair-queue
random-detect dscp-based
!
ip access-list extended Core_Voice_RTP
remark DSCP 24 = TOS 3
permit udp any any dscp cs3
remark DSCP ef
permit udp any any dscp ef
ip access-list extended Core_Voice_Signaling
remark MGCP Signaling
permit udp any any eq 2727
permit udp any eq 2727 any
permit udp any any eq 2427
permit udp any eq 2427 any
remark Samsung Signaling
permit udp any any eq 6000
permit udp any eq 6000 any
permit tcp any any eq 6100
permit tcp any eq 6100 any
remark Cisco Skinny Signaling
permit udp any any eq 2000
permit udp any eq 2000 any
permit tcp any any eq 2000
permit tcp any eq 2000 any
remark Allworx Signaling
permit udp any any eq 2088
permit udp any eq 2088 any
permit tcp any any eq 8081
permit tcp any eq 8081 any
remark ADIX Signaling
permit tcp any any eq 50000
permit tcp any eq 50000 any
remark SIP Signalling
permit udp any any eq 5060
permit udp any eq 5060 any
permit udp any any eq 5061
permit udp any eq 5061 any
permit tcp any any eq 5060
permit tcp any eq 5060 any
permit tcp any any eq 5061
permit tcp any eq 5061 any
!

-Jason

Travis Marlow wrote:
> I'm trying to plan for a QoS implementation for an Internet Access provider.
> I just finished reading RFC 4594 and it recommends VoIP signalling traffic
> be marked CS5. Every other reference I have seen always has it at AF31 or
> CS3. Is anyone else using the RFC recommendation? Would any SP be willing to
> share a general configuration for service classes they have defined.
>
> Sorry for the duplicate, I sent from the wrong email address before.
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Cisco nsp RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.