[c-nsp] Configured Loopback 0; now we have one-way voice?
Tim Jackson
jackson.tim at gmail.com
Wed Apr 30 10:30:01 EDT 2008
Sounds like you're sourcing RTP from a port that the far end can't send to
(maybe that loopback isn't reachable from your end points?) Even outside of
that, there are a ton of bugs with IOS determining how it binds to an
audio/signaling port for MGCP and SIP, but it definitely could help to use
the bind control & bind media commands (this is if you're using SIP):
voice service voip
sip
bind control source-interface FastEthernet0/0
bind media source-interface FastEthernet0/0
On Wed, Apr 30, 2008 at 9:18 AM, Jeff Cartier <jcartier at acs.on.ca> wrote:
>
> Hey Everyone,
>
> My familiarity with voice is very limited...So I ask this question :)
>
> We've been configuring loopback interfaces on our voice gateways in order
> to use the loopbacks for management purposes. We've noticed that when we
> configure loopback 0 we then get users complaining of one-way
> conversations...
>
> Any thoughts?
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list