<div>or better yet. look into the phone proxy service to secure your CM's better. I hear that the ASA has this service built in.... but I have not seen it yet.</div>
<div> </div>
<div>Scott<br><br></div>
<div class="gmail_quote">On Fri, Apr 25, 2008 at 7:37 AM, Matthew Saskin <<a href="mailto:matt@saskin.net">matt@saskin.net</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">What device is handling NAT? The problem is not IP communicator specific.<br><br>Unless things have changed recently, you've basically got to have a<br>
Cisco device (router or ASA) of specific code release or higher to<br>properly handle NAT for cisco IP phones.<br><br>-matt<br>
<div>
<div></div>
<div class="Wj3C7c"><br>Baddorf, Becky wrote:<br>> We are using NAT to get to our client servers. IP communicator does not<br>> function with NAT in our environment. Does anyone else use IP Comm with<br>> NAT?<br>
><br>> Thanks!<br>><br>> Becky Baddorf<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><br></div>
</div></blockquote></div><br>