[cisco-voip] GW IP Address in CCM
Ted Nugent
tednugent73 at gmail.com
Mon Jun 14 15:02:27 EDT 2010
my experience has been that it will pick the hard interface that is
connected closest to CM (Serial on WAN and ethernet on LAN)
I typically lock in the interface that I prefer with the mgcp bind commands
to make certain i know where its getting bound
mgcp bind control source-interface FastEthernet0/1
mgcp bind media source-interface FastEthernet0/1
HTH Ted
On Mon, Jun 14, 2010 at 12:33 PM, Jeff Ruttman <ruttmanj at carewisc.org>wrote:
> Hi,
>
> I have a voice router configured, and in CCM an MGCP GW configured. I put
> the router on the LAN and all is well except CCM can't see the loopback
> interface, so the IP address on the CCM GW is the gig interface that is
> connecting the router to the network. Otherwise it appears that CCM did its
> MGCP config on the router just fine. Turns out CCM can't ping the loopback
> interface on the router.
>
> I have the router connected ad hoc, not even on the specific network where
> it WILL be connected once in production. I assume there is something about
> the networking here that is preventing CCM from seeing the loopback as I'm
> currently setup. My questions:
>
> When a newly configed CCM GW and voice router first meet, does CCM look for
> a loopback by default? And since it couldn't find one on the voice router,
> it chose the gig interface instead?
>
> If I were to put the router on the proper network with the final IP address
> on the gig interface, and assuming the loopback interface is indeed now
> available to CCM, will it then use the loopback IP, or will I have to do
> something to make that happen.
>
> Loopback interface on router is Up Up.
>
> Thanks
> jeff
>
>
>
>
> _______________________________________________
> 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/20100614/a38000a3/attachment.html>
More information about the cisco-voip
mailing list