<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
Scot is right i faced the same problem and found there was route missing and when our Routing guy add the route for both direction issue resolved. <BR><BR><FONT color=#0000ff face="Lucida Handwriting, Cursive">Regards,</FONT><BR><FONT color=#0000ff face="Lucida Handwriting">Sheeraz Saeed lodhi.</FONT><BR><BR> <BR>
<DIV>
<HR id=stopSpelling>
Date: Thu, 15 Sep 2011 10:38:55 -0700<BR>From: svoll.voip@gmail.com<BR>To: mikenorton@pwsd76.ab.ca<BR>CC: cisco-voip@puck.nether.net<BR>Subject: Re: [cisco-voip] IP Communicator 1way audio?<BR><BR>Agreed. Look at the ASA or what ever is the head end and make sure you have Routes to the VGW and ACLs allowing the VGW bi-directional.
<DIV><BR></DIV>
<DIV>Scott<BR><BR>
<DIV class=ecxgmail_quote>On Thu, Sep 15, 2011 at 10:31 AM, Norton, Mike <SPAN dir=ltr><<A href="mailto:mikenorton@pwsd76.ab.ca">mikenorton@pwsd76.ab.ca</A>></SPAN> wrote:<BR>
<BLOCKQUOTE style="BORDER-LEFT: #ccc 1px solid; PADDING-LEFT: 1ex" class=ecxgmail_quote>
<DIV lang=EN-CA>
<DIV>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">If it was a codec disagreement, the call would fail. One-way audio is almost always a routing/firewall/NAT issue.<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"><U></U> <U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">-- <U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Mike Norton<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">I.T. Support<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Peace Wapiti School Division No. 76<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Helpdesk: <A target=_blank>780-831-3080</A><U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Direct: <A target=_blank>780-831-3076</A><U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"><U></U> <U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"><U></U> <U></U></SPAN></P>
<DIV>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=ecxMsoNormal><B><SPAN style="FONT-SIZE: 10pt" lang=EN-US>From:</SPAN></B><SPAN style="FONT-SIZE: 10pt" lang=EN-US> <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>] <B>On Behalf Of </B>Madziarczyk, Jonathan<BR><B>Sent:</B> September-15-11 10:37 AM<BR><B>To:</B> <A href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><B>Subject:</B> [cisco-voip] IP Communicator 1way audio?<U></U><U></U></SPAN></P></DIV></DIV>
<DIV>
<DIV></DIV>
<DIV class=h5>
<P class=ecxMsoNormal><U></U> <U></U></P>
<P class=ecxMsoNormal><SPAN lang=EN-US>So here’s what the end user is claiming:<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US><U></U> <U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US>From their laptop when they are on our network:<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US>CM to CM – 2 way<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US>CM to PRI – 2 way<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US><U></U> <U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US>From their laptop when they VPN in (cisco vpn client):<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US>CM to CM – 2 way<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US>CM to PRI – 1 way audio<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US><U></U> <U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US>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.<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US><U></U> <U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US>Suggestions on where to start?<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US><U></U> <U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US>JonM<U></U><U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US><U></U> <U></U></SPAN></P>
<P class=ecxMsoNormal><SPAN lang=EN-US><U></U> <U></U></SPAN></P></DIV></DIV></DIV></DIV><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></BLOCKQUOTE></DIV><BR></DIV><BR>_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip</DIV> </div></body>
</html>