<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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.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">I thought Cisco was saying that the CIPC version 7.0 was going to work with the ASA phone proxy.<o:p></o:p></p>
<p class="MsoNormal">has anyone gotten this working.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have a functional ASA phone proxy with hard phones working but can't seem to get my CIPC to register with the ASA phone proxy.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The CIPC registers and works fine when using the cisco VPN client<o:p></o:p></p>
<p class="MsoNormal">I change the TFTP server to the proper "outside" address on the ASA and it just goes thur the config loop<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">ASA 8.0(4)27<o:p></o:p></p>
<p class="MsoNormal">CUCM 7.0.1<o:p></o:p></p>
<p class="MsoNormal">Windows XP <o:p></o:p></p>
<p class="MsoNormal">CIPC 7.0.2.0<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">________________________________________<o:p></o:p></p>
<p class="MsoNormal">Brian Van Benschoten <o:p></o:p></p>
<p class="MsoNormal">Practice Leader - Unified Communications<o:p></o:p></p>
<p class="MsoNormal">Consulting Engineer - CCIE # 5421<o:p></o:p></p>
<p class="MsoNormal">Inacom Information Systems<o:p></o:p></p>
<p class="MsoNormal">3001 West Beltline Highway<o:p></o:p></p>
<p class="MsoNormal">Madison, WI 53713 USA<o:p></o:p></p>
<p class="MsoNormal">608-661-7780 (IP Phone)<o:p></o:p></p>
<p class="MsoNormal">608-661-7701 (FAX)<o:p></o:p></p>
<p class="MsoNormal">608-661-7777 (Customer Service)<o:p></o:p></p>
<p class="MsoNormal">brian.vanbenschoten@inacom.com<o:p></o:p></p>
<p class="MsoNormal">http://www.inacom.com<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Check out Inacom's vision for technology training at www.inacom.com/evolution<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Voted #1 IT Consulting Firm & #1 IT Training Company <o:p>
</o:p></b></p>
<p class="MsoNormal"><b>2007 & 2008 </b><b><span style="font-size:8.0pt">-InBusiness Magazine Executive Register</span></b><b><o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1">Important Notice: This email message and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee, you
should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Please note that any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of Inacom. Inacom specifically disclaims liability for any damage caused by any virus transmitted by this email.<br>
</font>
</body>
</html>