Re: Voice Traffic

From: Larry Hadrava <larryh12203_at_gmail.com>
Date: Mon, 6 Sep 2010 11:47:42 -0400 (EDT)

Check out www.cisco.com/go/srnd
Go through the drill downs to Voice and you will see lots of great design and configuration best practices and examples.

Thanks
Larry Hadrava
CCIE #12203
Check Out MyBlog: http://ccie12203.wordpress.com/

----- Original Message -----
From: "Kazi Junaid" <junaidkazi76_at_gmail.com>
To: "Radioactive Frog" <pbhatkoti_at_gmail.com>
Cc: "Ryan West" <rwest_at_zyedge.com>, "Narbik Kocharians" <narbikk_at_gmail.com>, "karim jamali" <karim.jamali_at_gmail.com>, "Cisco certification" <ccielab_at_groupstudy.com>
Sent: Monday, September 6, 2010 11:18:35 AM GMT -05:00 US/Canada Eastern
Subject: Re: Voice Traffic

Hi
QOS is not going to be easy, I am aware of that.
Getting input from you experts will help. Can you share the IPTEL Document
link referring to QOS if available with you.

thanks
JK

On Mon, Sep 6, 2010 at 2:42 PM, Radioactive Frog <pbhatkoti_at_gmail.com>wrote:

> Kazi,
>
> it's not that easy as you're thinking in MPLS environment. Most voiper
> won't even think about the topology. There is an issue with call manager CAC
> in MPLS environment.
>
> In most cases MPLS is not hub-n-spoke.
> the bottom line is, You must use RSVP for QoS in MPLS environment.
>
> read why you need it on IPTEL design document and you shoudl be fine.
>
> re protocol matching, just use the NBAR as it's preferred method. The port
> mapping was the only method when NBAR was not out.
> All 12.4x codes have pretty decent NBAR.
>
> HTH
>
> -frog
>
>
> On Mon, Sep 6, 2010 at 6:08 PM, Kazi Junaid <junaidkazi76_at_gmail.com>wrote:
>
>> Thanks U all for the support.
>>
>>
>>
>> On Mon, Sep 6, 2010 at 10:56 AM, Ryan West <rwest_at_zyedge.com> wrote:
>>
>> > Kazi,
>> >
>> > As usual, I'm a little too terse in my reply. There are a couple of
>> > reasons you want to trust as close to the edge as possible and accept
>> the
>> > markings from the phone. Most likely, your gateway or MPLS router is an
>> > ISR, a software based router. Deeper packet inspection to determine RTP
>> > payload is going to use CPU resources and you'll most likely remark the
>> > packets to EF anyhow. The MPLS provider is going to use the DiffServ
>> > markings to classify your traffic (assuming you've paid for it) into the
>> EXP
>> > bits and set policy based on them.
>> >
>> > http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/nbarw_wp.htm
>> >
>> > -ryan
>> >
>> > > -----Original Message-----
>> > > From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On
>> > > Behalf Of Ryan West
>> > > Sent: Monday, September 06, 2010 3:33 AM
>> > >
>> > > match protocol rtp payload-type "0, 15"
>> > >
>> > > Most installations just trust the markings from the phone and match on
>> > the
>> > > DSCP value, but the above will work as well.
>> > >
>> > > -ryan
>> > >
>> > >
>> > > The Codec are G711 and G728. How do I mark only for these codecs.
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Mon Sep 06 2010 - 11:47:42 ART

This archive was generated by hypermail 2.2.0 : Fri Oct 01 2010 - 05:58:05 ART