<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>I'd check the IP address they acquire when they use a VPN and then check the routing between the core voice VLAN and the subnet the VPN clients acquire as they connect.<br></span></div><div><br></div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> "Madziarczyk, Jonathan" <jmad@cityofevanston.org><br><b><span style="font-weight: bold;">To:</span></b> cisco-voip@puck.nether.net<br><b><span style="font-weight: bold;">Sent:</span></b> Thursday, September 15, 2011 9:36 AM<br><b><span style="font-weight: bold;">Subject:</span></b> [cisco-voip] IP Communicator 1way audio?<br></font><br><meta
http-equiv="x-dns-prefetch-control" content="off"><div id="yiv1959442323"><style><!--
#yiv1959442323
_filtered #yiv1959442323 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
#yiv1959442323
#yiv1959442323 p.yiv1959442323MsoNormal, #yiv1959442323 li.yiv1959442323MsoNormal, #yiv1959442323 div.yiv1959442323MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"sans-serif";}
#yiv1959442323 a:link, #yiv1959442323 span.yiv1959442323MsoHyperlink
{color:blue;text-decoration:underline;}
#yiv1959442323 a:visited, #yiv1959442323 span.yiv1959442323MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
#yiv1959442323 span.yiv1959442323EmailStyle17
{font-family:"sans-serif";color:windowtext;}
#yiv1959442323 .yiv1959442323MsoChpDefault
{font-family:"sans-serif";}
_filtered #yiv1959442323 {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv1959442323 div.yiv1959442323WordSection1
{}
--></style><div class="yiv1959442323WordSection1"><div class="yiv1959442323MsoNormal">So here’s what the end user is claiming:</div><div class="yiv1959442323MsoNormal"> </div><div class="yiv1959442323MsoNormal">From their laptop when they are on our network:</div><div class="yiv1959442323MsoNormal">CM to CM – 2 way</div><div class="yiv1959442323MsoNormal">CM to PRI – 2 way</div><div class="yiv1959442323MsoNormal"> </div><div class="yiv1959442323MsoNormal">From their laptop when they VPN in (cisco vpn client):</div><div class="yiv1959442323MsoNormal">CM to CM – 2 way</div><div class="yiv1959442323MsoNormal">CM to PRI – 1 way audio</div><div class="yiv1959442323MsoNormal"> </div><div class="yiv1959442323MsoNormal">My initial guess is that the IP communicator client is outthinking itself and changing the codec to something that our Voice Gateway doesn’t understand or isn’t expecting, but only when it’s via VPN. Not
quite sure how to test this yet.</div><div class="yiv1959442323MsoNormal"> </div><div class="yiv1959442323MsoNormal">Suggestions on where to start?</div><div class="yiv1959442323MsoNormal"> </div><div class="yiv1959442323MsoNormal">JonM</div><div class="yiv1959442323MsoNormal"> </div><div class="yiv1959442323MsoNormal"> </div></div></div><meta http-equiv="x-dns-prefetch-control" content="on"><br>_______________________________________________<br>cisco-voip mailing list<br><a ymailto="mailto:cisco-voip@puck.nether.net" 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></div></div></div></body></html>