[cisco-voip] GW IP Address in CCM

Tue Jun 15 08:31:29 EDT 2010

Hey thanks everyone!

I prefer the loopback also if for no other reason for consistency sake
as all the other GWs we have are using loopbacks.  I can try Mr.
Nugent's bind statement suggestion if need be.  I do wonder though how
all our existing sites use loopback but yet there are no bind statements
anywhere as suggested by Ted.  Something about the implementation of our
existing GWs (all pre-date me) must have governed the use of loopbacks,
something I'm doing differently.

Most of our sites have the voice router with a gig connection to a
switch, a serial connection to the home office, maybe an FXO connection,
and the loopback configured--really just like the router I'm currently
working on.  Could be that it would have used the loopback but since
call manager couldn't see it (can't ping it from CM anyway) it used the
gig port instead...though why the loopback isn't available, not sure
yet.  

Thanks again,
jeff

________________________________

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:32 PM
To: Go0se
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] GW IP Address in CCM

The other good thing is that with a loop back, you can relocate a
server/router or respond to a network change request by your networking
team with little impact.

I think there are quite a few advantages that's for sure.

---
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: "Go0se" <me at go0se.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, "Dennis Heim"
<Dennis.Heim at cdw.com>
Cc: cisco-voip at puck.nether.net
Sent: Monday, June 14, 2010 3:57:55 PM GMT -05:00 US/Canada Eastern
Subject: RE: [cisco-voip] GW IP Address in CCM

<captain obvious>One of the biggest benefits of a loopback interface is
that it never drops or goes to a "down" state.</captain obvious>

Thanks,

Go0se

My blog: 

http://atc.go0se.com <http://atc.go0se.com/> 

-------------------------------------

Help Hopegivers International 

feed the orphans of India.

http://www.hopegivers.org <http://www.hopegivers.org/> 

-------------------------------------

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 2:43 PM
To: Dennis Heim
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] GW IP Address in CCM

Correct. I use loopbacks when I configure redundancy....

---
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: "Dennis Heim" <Dennis.Heim at cdw.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, "Ted Nugent"
<tednugent73 at gmail.com>
Cc: cisco-voip at puck.nether.net
Sent: Monday, June 14, 2010 3:20:37 PM GMT -05:00 US/Canada Eastern
Subject: RE: [cisco-voip] GW IP Address in CCM

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 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100615/3b6c28e3/attachment.html>