[cisco-voip] IP Communicator 1way audio?

[Scott Voll]

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.

Scott

On Thu, Sep 15, 2011 at 10:31 AM, Norton, Mike <mikenorton at pwsd76.ab.ca>wrote:

>  If it was a codec disagreement, the call would fail. One-way audio is
> almost always a routing/firewall/NAT issue.****
>
> ** **
>
> -- ****
>
> Mike Norton****
>
> I.T. Support****
>
> Peace Wapiti School Division No. 76****
>
> Helpdesk: 780-831-3080****
>
> Direct: 780-831-3076****
>
> ** **
>
> ** **
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Madziarczyk, Jonathan
> *Sent:* September-15-11 10:37 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] IP Communicator 1way audio?****
>
> ** **
>
> So here’s what the end user is claiming:****
>
> ** **
>
> From their laptop when they are on our network:****
>
> CM to CM – 2 way****
>
> CM to PRI – 2 way****
>
> ** **
>
> From their laptop when they VPN in (cisco vpn client):****
>
> CM to CM – 2 way****
>
> CM to PRI – 1 way audio****
>
> ** **
>
> 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.****
>
> ** **
>
> Suggestions on where to start?****
>
> ** **
>
> JonM****
>
> ** **
>
> ** **
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110915/f220d608/attachment.html>