That was the clue I needed guys. I hooked up the sniifer and determined that it was actually going to our voice gateway voice vlan ip address. It was permitted as part of the VPN tunnel, but the traffic was unable to get back to it from the remote site. I check the remote site router and found that it was trying to NAT traffic to that VLAN because of the order of the access-list statements. Fixed that, and now everything is beautiful. <br>
<br>Thanks again guys!<br><br><div class="gmail_quote">On Tue, Mar 3, 2009 at 2:10 PM, <span dir="ltr"><<a href="mailto:A.L.M.Buxey@lboro.ac.uk">A.L.M.Buxey@lboro.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
hi,<br>
<br>
this is a common issue - when you are doing voicemail, your handset<br>
is talking direct to the call manager - therefore you can listen, make<br>
changes, etc etc.<br>
<br>
however, when you make a call, as soon as the other end picks up, the two<br>
handsets pass traffic directly to each other - if one of them cannot<br>
send their packets then the conversation is one sided...you can hear<br>
the other end 100% perfect..but they dont hear you...because the traffic<br>
aint getting through. Ensure that your routing and VPN are correct<br>
and that any ACLs will allow the IP range of each end to talk to each other<br>
<br>
alan<br>
</blockquote></div><br>