<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
..MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>To use CUPC, you must have CUPS.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Voice Noob<br>
<b>Sent:</b> Monday, December 10, 2007 5:59 PM<br>
<b>To:</b> Justin Steinberg<br>
<b>Cc:</b> Wolfe, Robert; cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] CUCM6 - Click to Dial<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Do you have to use Presense
server for CUPC or can you use just CCM 6.0?<o:p></o:p></p>
<div>
<p class=MsoNormal>On Dec 10, 2007 4:54 PM, Justin Steinberg <<a
href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>Cisco Unified Personal Communicator has a nice hook into
Outlook for<br>
click to dial. CUPC can operate in Deskphone/CTI or Softphone mode. <o:p></o:p></p>
<div>
<p class=MsoNormal><br>
On Dec 10, 2007 5:22 PM, Wolfe, Robert <<a href="mailto:rwolfe@burwood.com">rwolfe@burwood.com</a>>
wrote:<br>
> Hello all,<br>
><br>
> Does anyone know of an application other than LiteScape that offers
Click-to-Dial functionality in Communications Manager 6.0? We queried
Citrix on their Application Gateway, but it seems that they are six months out
in terms of a final release.<br>
><br>
> The functionality that we are looking for is primarily click to dial from
Outlook and IE. We have demoed the TSP solution for the client, but that
is obviously not the most elegant way to do things. <br>
><br>
> Any info greatly appreciated!<br>
><br>
> Best,<br>
><br>
> -rob<br>
><br>
> Rob Wolfe|Consultant | burwood group, inc.<o:p></o:p></p>
</div>
<p class=MsoNormal>> rwolfe@<nospam><a href="http://burwood.com/"
target="_blank"> burwood.com</a> | Work: 312 327 4634| Cell: 312
5930605| Fax: 312 327 4601<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal>><br>
> -----Original Message-----<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">
cisco-voip-bounces@puck.nether.net</a>] On Behalf Of <a
href="mailto:cisco-voip-request@puck.nether.net">cisco-voip-request@puck.nether.net</a><br>
> Sent: Monday, December 10, 2007 4:02 PM<br>
> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: cisco-voip Digest, Vol 58, Issue 51<br>
><br>
> Send cisco-voip mailing list submissions to<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a
href="mailto:cisco-voip-request@puck.nether.net">cisco-voip-request@puck.nether.net</a><br>
><br>
> You can reach the person managing the list at <br>
> <a
href="mailto:cisco-voip-owner@puck.nether.net">cisco-voip-owner@puck.nether.net</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of cisco-voip digest..." <br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: CallManager LAN QOS Question (<a
href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a>)<br>
> 2. Re: CallManager LAN QOS Question
[bcc][faked-from][html-rem] <br>
> (<a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a>)<br>
> 3. Re: CallManager LAN QOS Question [bcc][faked-from][html-rem]<br>
> (TianLun Song)<br>
><br>
><br>
> ---------------------------------------------------------------------- <br>
><br>
> Message: 1<br>
> Date: Mon, 10 Dec 2007 15:24:42 -0600<br>
> From: <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a><br>
> Subject: Re: [cisco-voip] CallManager LAN QOS Question <br>
> To: "Linsemier, Matthew" <<a
href="mailto:MLinsemier@apcapital.com">MLinsemier@apcapital.com</a>><br>
> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Message-ID: <br>
> <<a
href="mailto:OF81C4696B.7664E968-ON852573AD.0073B06E-862573AD.0075B457@assurant.com">OF81C4696B.7664E968-ON852573AD.0073B06E-862573AD.0075B457@assurant.com</a>><br>
><br>
> Content-Type: text/plain; charset="us-ascii" <br>
><br>
> Ahh good catch. I'm seeing different results between sniffer
products. An<br>
> older version of Ethereal is showing me the DiffServ field and the bits<br>
> are correct and in both directions. I'm guessing that my distributed
<br>
> sniffer either needs an option enabled or a module paid for.<br>
><br>
> I have one more question so that I better understand.<br>
><br>
> <auto qos voip trust> adds <mls qos trust cos> to the
interface. Should I <br>
> change this to <mls qos trust dscp> on all Call Manager interfaces,
router<br>
> interfaces and trunks?<br>
> Would I ever configure dscp on a cisco or avaya ip phone interface?<br>
><br>
> Thanks for the help. I've been sniffing this almost all afternoon. <br>
><br>
> Steve Siltman<br>
> Assurant Corporate Technology<br>
> Work: 651-361-4752<br>
> Cell: 651-336-5563<br>
> <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a><br>
><br>
> <br>
><br>
> "Linsemier, Matthew" <<a
href="mailto:MLinsemier@apcapital.com">MLinsemier@apcapital.com</a>><br>
> 12/10/2007 01:55 PM<br>
><br>
> To<br>
> <<a href="mailto:steve.siltman@assurant.com"> steve.siltman@assurant.com</a>>,
<<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
> cc<br>
><br>
> Subject<br>
> RE: [cisco-voip] CallManager LAN QOS Question<br>
><br>
> <br>
><br>
><br>
><br>
><br>
> Are you just sniffing COS? Are the DSCP values correct that
CallManager<br>
> is sending out? RTP should be marked as DSCP EF and all SCCP,H.323,
and<br>
> SIP should be marked as DSCP C3. What are your DSCP -> COS
mappings on <br>
> your switch?<br>
><br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net
</a>] On Behalf Of<br>
> <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a><br>
> Sent: Monday, December 10, 2007 2:20 PM<br>
> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a><br>
> Subject: [cisco-voip] CallManager LAN QOS Question<br>
><br>
><br>
> Hi All.<br>
><br>
> I implemented QOS on the LAN this weekend in our shop. I configured
6<br>
> closets running a slew of 3750's and four 6500 CAT switches (with a few <br>
> 6x48 blades). I have one issue so far. I'm sniffing one of
the Call<br>
> Manager interfaces on the switch and all packets coming into the<br>
> CallManager seem to have the correct COS assigned. All of the
packets <br>
> sourced by CallManager are COS = 0. This makes it look like
CallManager<br>
> is changing these packets to 0. Did I miss something on CallManager
that<br>
> I need to enable? The clusterwide parameters (System - QOS) under <br>
> Service Parameters is set to Normal Priority, EF, AF41 and CS3.<br>
><br>
> Running CallManager 4.1.3sr5d<br>
><br>
> Thanks,<br>
><br>
> Steve Siltman<br>
> Assurant Corporate Technology<br>
> Work: 651-361-4752 <br>
> Cell: 651-336-5563<br>
> <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a><br>
><br>
><br>
> **************************************************************************************
<br>
> This e-mail message and all attachments transmitted with it may contain
legally privileged and/or confidential information intended solely for the use
of the addressee(s). If the reader of this message is not the intended
recipient, you are hereby notified that any reading, dissemination,
distribution, copying, forwarding or other use of this message or its
attachments is strictly prohibited. If you have received this message in error,
please notify the sender immediately and delete this message and all copies and
backups thereof. <br>
><br>
> Thank you.<br>
>
**************************************************************************************<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <a
href="https://puck.nether.net/pipermail/cisco-voip/attachments/20071210/d38b652d/attachment-0001.html"
target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20071210/d38b652d/attachment-0001.html</a>
<br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Mon, 10 Dec 2007 15:29:46 -0600<br>
> From: <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a><br>
> Subject: Re: [cisco-voip] CallManager LAN QOS Question <br>
> [bcc][faked-from][html-rem]<br>
> To: "Avner Izhar" <<a href="mailto:aizhar@ccbootcamp.com">aizhar@ccbootcamp.com</a>><br>
> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net
</a><br>
> Message-ID:<br>
> <<a
href="mailto:OF219F0FC7.E68C51D5-ON852573AD.0075A24E-862573AD.00762B14@assurant.com">OF219F0FC7.E68C51D5-ON852573AD.0075A24E-862573AD.00762B14@assurant.com</a>><br>
><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> Doesn't the COS bits make up the first 3 bits of the DSCP? I should
see<br>
> both if the sniffer lets me. :(<br>
> It is setup as an access port. <br>
><br>
> Thanks,<br>
><br>
> Steve Siltman<br>
> Assurant Corporate Technology<br>
> Work: 651-361-4752<br>
> Cell: 651-336-5563<br>
> <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com </a><br>
><br>
><br>
><br>
> "Avner Izhar" <<a href="mailto:aizhar@ccbootcamp.com">aizhar@ccbootcamp.com</a>><br>
> 12/10/2007 03:17 PM<br>
><br>
> To<br>
> "Linsemier, Matthew" < <a
href="mailto:MLinsemier@apcapital.com">MLinsemier@apcapital.com</a>>,<br>
> <<a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a>>,
<<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net </a>><br>
> cc<br>
><br>
> Subject<br>
> RE: [cisco-voip] CallManager LAN QOS Question [bcc][faked-from][html-rem]<br>
><br>
><br>
><br>
><br>
><br>
><br>
> Hi,<br>
><br>
> Call Manager is doing DSCP based marking and not COS based, unless we talk
<br>
> about different things and mean the same, it is acting as it should.<br>
><br>
> Have you configured trunk toward the Call Manager? It should be an access<br>
> port.<br>
><br>
> HTH,<br>
> ------------------------------------------- <br>
> thanks,<br>
> Avner Izhar<br>
> CCIE#15999 (Voice), CCVP, CCSI# 31623<br>
> Technical Instructor<br>
> CCBOOTCAMP - A Cisco Sponsored Organization (SO)<br>
> Email: <a href="mailto:aizhar@ccbootcamp.com">aizhar@ccbootcamp.com</a><br>
> Toll Free: 877-654-2243<br>
> Direct: +1-702-968-5100 = Outside the USA<br>
> FAX: +1-702-446-8012<br>
> YES! We take Cisco Learning Credits!<br>
> Training And Remote Racks: <a href="http://www.ccbootcamp.com/"
target="_blank">http://www.ccbootcamp.com</a><br>
><br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">
cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Linsemier,<br>
> Matthew<br>
> Sent: Monday, December 10, 2007 11:56<br>
> To: <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a>;
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: Re: [cisco-voip] CallManager LAN QOS Question<br>
> [bcc][faked-from][html-rem]<br>
><br>
> Are you just sniffing COS? Are the DSCP values correct that
CallManager<br>
> is sending out? RTP should be marked as DSCP EF and all SCCP,H.323,
and<br>
> SIP should be marked as DSCP C3. What are your DSCP -> COS
mappings on<br>
> your switch?<br>
><br>
><br>
><br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of<br>
> <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com </a><br>
> Sent: Monday, December 10, 2007 2:20 PM<br>
> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: [cisco-voip] CallManager LAN QOS Question<br>
><br>
><br>
> <br>
><br>
> Hi All.<br>
><br>
> I implemented QOS on the LAN this weekend in our shop. I configured
6<br>
> closets running a slew of 3750's and four 6500 CAT switches (with a few<br>
> 6x48 blades). I have one issue so far. I'm sniffing one of
the Call <br>
> Manager interfaces on the switch and all packets coming into the<br>
> CallManager seem to have the correct COS assigned. All of the
packets<br>
> sourced by CallManager are COS = 0. This makes it look like
CallManager <br>
> is changing these packets to 0. Did I miss something on CallManager<br>
> that I need to enable? The clusterwide parameters (System - QOS)
under<br>
> Service Parameters is set to Normal Priority, EF, AF41 and CS3. <br>
><br>
> Running CallManager 4.1.3sr5d<br>
><br>
> Thanks,<br>
><br>
> Steve Siltman<br>
> Assurant Corporate Technology<br>
> Work: 651-361-4752<br>
> Cell: 651-336-5563<br>
> <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a><br>
><br>
><br>
><br>
><br>
>
**************************************************************************************<br>
> This e-mail message and all attachments transmitted with it may contain
legally privileged and/or confidential information intended solely for the use
of the addressee(s). If the reader of this message is not the intended
recipient, you are hereby notified that any reading, dissemination, distribution,
copying, forwarding or other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please notify the
sender immediately and delete this message and all copies and backups thereof. <br>
><br>
> Thank you.<br>
>
**************************************************************************************<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <a
href="https://puck.nether.net/pipermail/cisco-voip/attachments/20071210/abc89978/attachment-0001.html"
target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20071210/abc89978/attachment-0001.html</a>
<br>
><br>
> ------------------------------<br>
><br>
> Message: 3<br>
> Date: Mon, 10 Dec 2007 17:02:04 -0500<br>
> From: "TianLun Song" <<a href="mailto:stl911@gmail.com">stl911@gmail.com</a>>
<br>
> Subject: Re: [cisco-voip] CallManager LAN QOS Question<br>
> [bcc][faked-from][html-rem]<br>
> To: <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a><br>
> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Message-ID:<br>
> <<a
href="mailto:22adde7f0712101402n2f11dc95r8896d1c6f6a93f4a@mail.gmail.com">22adde7f0712101402n2f11dc95r8896d1c6f6a93f4a@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1" <br>
><br>
> I think you mean TOS bit instead of COS<br>
><br>
> On Dec 10, 2007 4:29 PM, <<a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a>>
wrote:<br>
><br>
> ><br>
> > Doesn't the COS bits make up the first 3 bits of the DSCP? I
should see <br>
> > both if the sniffer lets me. :(<br>
> > It is setup as an access port.<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Steve Siltman<br>
> > Assurant Corporate Technology<br>
> > Work: 651-361-4752 <br>
> > Cell: 651-336-5563<br>
> > <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a><br>
> ><br>
> ><br>
> > *"Avner Izhar" <<a
href="mailto:aizhar@ccbootcamp.com"> aizhar@ccbootcamp.com</a>>*<br>
> ><br>
> > 12/10/2007 03:17 PM<br>
> > To<br>
> > "Linsemier, Matthew" <<a
href="mailto:MLinsemier@apcapital.com">MLinsemier@apcapital.com</a>>, < <br>
> > <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a>>,
<<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>>
cc<br>
> > Subject<br>
> > RE: [cisco-voip] CallManager LAN QOS Question [bcc][faked-from][html-rem]
<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Hi,<br>
> ><br>
> > Call Manager is doing DSCP based marking and not COS based, unless we
talk<br>
> > about different things and mean the same, it is acting as it should. <br>
> ><br>
> > Have you configured trunk toward the Call Manager? It should be an
access<br>
> > port.<br>
> ><br>
> > HTH,<br>
> > -------------------------------------------<br>
> > thanks, <br>
> > Avner Izhar<br>
> > CCIE#15999 (Voice), CCVP, CCSI# 31623<br>
> > Technical Instructor<br>
> > CCBOOTCAMP - A Cisco Sponsored Organization (SO)<br>
> > Email: <a href="mailto:aizhar@ccbootcamp.com">aizhar@ccbootcamp.com</a><br>
> > Toll Free: 877-654-2243<br>
> > Direct: +1-702-968-5100 = Outside the USA<br>
> > FAX: +1-702-446-8012<br>
> > YES! We take Cisco Learning Credits!<br>
> > Training And Remote Racks: <a href="http://www.ccbootcamp.com/"
target="_blank">http://www.ccbootcamp.com</a><br>
> ><br>
> ><br>
> ><br>
> > -----Original Message-----<br>
> > From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[mailto:<br>
> > <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Linsemier, Matthew<br>
> > Sent: Monday, December 10, 2007 11:56 <br>
> > To: <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a>;
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> > Subject: Re: [cisco-voip] CallManager LAN QOS Question <br>
> > [bcc][faked-from][html-rem]<br>
> ><br>
> > Are you just sniffing COS? Are the DSCP values correct that
CallManager<br>
> > is sending out? RTP should be marked as DSCP EF and all
SCCP,H.323 , and<br>
> > SIP should be marked as DSCP C3. What are your DSCP -> COS
mappings on<br>
> > your switch?<br>
> ><br>
> ><br>
> ><br>
> > From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> > [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of<br>
> > <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a><br>
> > Sent: Monday, December 10, 2007 2:20 PM<br>
> > To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> > Subject: [cisco-voip] CallManager LAN QOS Question <br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Hi All.<br>
> ><br>
> > I implemented QOS on the LAN this weekend in our shop. I
configured 6<br>
> > closets running a slew of 3750's and four 6500 CAT switches (with a
few <br>
> > 6x48 blades). I have one issue so far. I'm sniffing one
of the Call<br>
> > Manager interfaces on the switch and all packets coming into the<br>
> > CallManager seem to have the correct COS assigned. All of the
packets <br>
> > sourced by CallManager are COS = 0. This makes it look like
CallManager<br>
> > is changing these packets to 0. Did I miss something on
CallManager<br>
> > that I need to enable? The clusterwide parameters (System -
QOS) under <br>
> > Service Parameters is set to Normal Priority, EF, AF41 and CS3.<br>
> ><br>
> > Running CallManager 4.1.3sr5d<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Steve Siltman<br>
> > Assurant Corporate Technology <br>
> > Work: 651-361-4752<br>
> > Cell: 651-336-5563<br>
> > <a href="mailto:steve.siltman@assurant.com">steve.siltman@assurant.com</a><br>
> ><br>
> ><br>
> ><br>
> > ------------------------------ <br>
> > This e-mail message and all attachments transmitted with it may
contain<br>
> > legally privileged and/or confidential information intended solely
for the<br>
> > use of the addressee(s). If the reader of this message is not the
intended <br>
> > recipient, you are hereby notified that any reading, dissemination,<br>
> > distribution, copying, forwarding or other use of this message or its<br>
> > attachments is strictly prohibited. If you have received this message
in <br>
> > error, please notify the sender immediately and delete this message
and all<br>
> > copies and backups thereof.<br>
> ><br>
> > Thank you.<br>
> > ------------------------------<br>
> > <br>
> ><br>
> > _______________________________________________<br>
> > cisco-voip mailing list<br>
> > <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> ><br>
><br>
><br>
><br>
> --<br>
> TianLun Song<br>
> CCVP, CCNP, M.Eng<br>
> Cell:1-416-829-3630<br>
> -------------- next part -------------- <br>
> An HTML attachment was scrubbed...<br>
> URL: <a
href="https://puck.nether.net/pipermail/cisco-voip/attachments/20071210/c41841c7/attachment.html"
target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20071210/c41841c7/attachment.html
</a><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net </a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
> End of cisco-voip Digest, Vol 58, Issue 51<br>
> ****************************************** <br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>