[cisco-voip] GW IP Address in CCM

[Mike Lydick]

More specific Loopbacks are used for sourcing your traffic. They should be
used when there are multiple routed interfaces ( sub-interfaces, tunnels are
other examples when a loopback may be needed).

Best Regards,

Mike Lydick




On Mon, Jun 14, 2010 at 3:20 PM, Dennis Heim <Dennis.Heim at cdw.com> wrote:

> Loopbacks are only effective if you have more than 1 physical interface
> connected to the network. I have seen too many people think additional
> redundancy is provided simply by using loopback even though there is only
> one network link to the router.
>
>
>
> Dennis Heim
> Network Voice Engineer
> CDW  Advanced Technology Services
> 11711 N. Meridian Street, Suite 225
> Carmel, IN  46032
>
> 317.569.4255 Office
> 317.569.4201 Fax
> 317.694.6070 Cell
>
> dennis.heim at cdw.com
> cdw.com/content/solutions/unified-communications/<http://www.cdw.com/content/solutions/unified-communications/>
>
>
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Lelio Fulgenzi
> *Sent:* Monday, June 14, 2010 3:12 PM
> *To:* Ted Nugent
>
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] GW IP Address in CCM
>
>
>
> I usually go with loop backs. Remember, you need to have routing enabled
> though on the voice gateway so your loopbacks get advertised properly. Seems
> silly, but I don't think routing is turned on by default.
>
> Lelio
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it.
>                               - LFJ (with apologies to Mr. Popeil)
>
>
> ----- Original Message -----
> From: "Ted Nugent" <tednugent73 at gmail.com>
> To: "Jeff Ruttman" <ruttmanj at carewisc.org>
> Cc: cisco-voip at puck.nether.net
> Sent: Monday, June 14, 2010 3:02:27 PM GMT -05:00 US/Canada Eastern
> Subject: Re: [cisco-voip] GW IP Address in CCM
>
> 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
>
>
>
> _______________________________________________ cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> 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/9eb6a794/attachment.html>