[cisco-voip] gatekeepers - when, why, how?

[Chris Ward (chrward)]

Well, that just means your UCMs can’t join the SAF network. The SAF forwarders and other IOS devices just need a 15.X IOS and they should be able to participate.

 

+Chris

 

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca] 
Sent: Monday, April 12, 2010 10:07 AM
To: Chris Ward (chrward)
Cc: cisco-voip voyp list
Subject: Re: [cisco-voip] gatekeepers - when, why, how?

 

Thanks Chris. Unfortunately we do not have access to 8.X code (no UCSS), we're building our new infrastructure on 7.X code.

That being said, if I were to want to use this just during SRST times and all my devices were running the appropriate IOS code, could I get away with it?

---
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: "Chris Ward (chrward)" <chrward at cisco.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, "cisco-voip voyp list" <cisco-voip at puck.nether.net>
Sent: Monday, April 12, 2010 9:55:25 AM GMT -05:00 US/Canada Eastern
Subject: RE: [cisco-voip] gatekeepers - when, why, how?




Hi Lelio,

 

You may want to investigate using the new Service Advertisement Framework and Call Control Discovery that are included in the new 8.0 release. It can be more distributed and is much simpler than a gatekeeper deployment.

 

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6554/ps6599/ps10822/qa_c67-573463.html

 

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6554/ps6599/ps10822/whitepaper_c11-573461.html

 

+Chris

 

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Monday, April 12, 2010 9:51 AM
To: cisco-voip voyp list
Subject: [cisco-voip] gatekeepers - when, why, how?

 

So, taking off from a previous discussion about requiring MGCP enabled endpoints to support SG3 speeds, I was thinking, how do I get all these devices to talk to each other during SRST/H323 fallback. I could configure a whole bunch of dial-peers, but that doesn't sound like fun with ports assigned with non-consecutive extension ranges.

Do I use a gatekeeper for this? Is gatekeeper still a relevant technology or has it been superceded by something else, i.e. IPIPGW?

Assuming I have a stack of 8 x VG224s and 8 x 2901s (w/ VIC3-2FXS-E/DID for long distances) and 2 x 3945s (to hold all the SCCP registrations) what would be the recommended approach? 

*	Can I get away with only one zone?
*	Can I configure two gatekeepers in some sort of redunant mode?
*	Can a gatekeeper assist with COR lists in anyway?

Hopefully someone can point me in the right direction....


---
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)

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