📄 ch04s05.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from url=(0077)http://www.informatik.uni-bremen.de/~prelle/terena/cookbook/main/ch04s05.html -->
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?><HTML
xmlns="http://www.w3.org/1999/xhtml"><HEAD><TITLE>4.5.燬etting up H.323 services</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1"><LINK
href="ch04s05.files/terena.css" type=text/css rel=stylesheet>
<META content="MSHTML 6.00.2800.1106" name=GENERATOR><LINK
title="IP Telephony Cookbook" href="index.html" rel=home><LINK
title="Chapter 4. Setting up basic services" href="ch04.html"
rel=up><LINK title=4.4. Examples href="ch04s04.html" rel=previous><LINK
title="4.6. Setting up SIP services" href="ch04s06.html" rel=next><LINK
title=Chapter 1. Introduction href="ch01.html" rel=chapter><LINK
title="Chapter 2. Technology Background" href="ch02.html"
rel=chapter><LINK title="Chapter 3. IP Telephony Scenarios"
href="ch03.html" rel=chapter><LINK
title="Chapter 4. Setting up basic services" href="ch04.html"
rel=chapter><LINK title="Chapter 5. Setting up Advanced Services"
href="ch05.html" rel=chapter><LINK
title="Chapter 6. Setting up Value-Added Services" href="ch06.html"
rel=chapter><LINK title="Chapter 7. Global telephony integration"
href="ch07.html" rel=chapter><LINK
title="Chapter 8. Regulatory / Legal considerations" href="ch08.html"
rel=chapter><LINK title="Appendix A. European IP Telephony Projects"
href="apa.html" rel=appendix><LINK
title="Appendix B. IP Telephony Hardware/Software" href="apb.html"
rel=appendix><LINK title=Glossary href="go01.html" rel=glossary><LINK
title="4.5.1. Using a Cisco Multimedia Conference Manager (MCM gatekeeper)"
href="ch04s05.html#d0e3459" rel=subsection><LINK
title="4.5.2. Using a Radvision Enhanced Communication Server (ECS gatekeeper)"
href="ch04s05.html#d0e3530" rel=subsection><LINK
title="4.5.3. Using an OpenH323 Gatekeeper - GNU Gatekeeper"
href="ch04s05.html#sec-gnugk" rel=subsection></HEAD>
<BODY>
<DIV class=navheader>
<TABLE width="100%" summary="Navigation header">
<TBODY>
<TR>
<TH align=middle colSpan=3>4.5. Setting up H.323 services</TH></TR>
<TR>
<TD align=left width="20%"><A accessKey=p
href="http://www.informatik.uni-bremen.de/~prelle/terena/cookbook/main/ch04s04.html">Prev</A> </TD>
<TH align=middle width="60%">Chapter 4. Setting up basic
services</TH>
<TD align=right width="20%"> <A accessKey=n
href="http://www.informatik.uni-bremen.de/~prelle/terena/cookbook/main/ch04s06.html">Next</A></TD></TR></TBODY></TABLE></DIV>
<DIV class=sect1 lang=en>
<DIV class=titlepage>
<DIV>
<DIV>
<H2 class=title style="CLEAR: both"><A
id=sec-setting-h323-services>4.5. Setting up H.323
services</H2></DIV></DIV>
<DIV></DIV>
<P>When setting up H.323 services, the basic component to install is a
gatekeeper, in order to provide initial functionality to an installed base of
H.323 clients. This basic functionality entails: </P>
<P>
<DIV class=itemizedlist>
<UL type=disc compact>
<LI>in-zone calling among endpoints
<LI>out-of-zone calling (incoming/outgoing)
<LI>access to local services (e.g. gateways, multi-point conference servers)
<LI>name resolution during calls, by H.323 alias or E.164 number
<LI>zone management (authentication, bandwidth restriction,
etc.)</LI></UL></DIV>
<P></P>
<P>In this section, we will be presenting guides for running the three most
popular gatekeeper implementations that are available today. A comparison of
these gatekeeper implementations based on their capabilities and requirements
follows <A title="Figure 4.13. Gatekeeper features examples"
href="http://www.informatik.uni-bremen.de/~prelle/terena/cookbook/main/ch04s05.html#gk-table">here</A>:</P>
<DIV class=figure><A id=gk-table>
<P class=title><B>Figure 4.13. Gatekeeper features examples</B></P>
<DIV class=mediaobject align=center>
<TABLE cellSpacing=0 cellPadding=0 width=496
summary="manufactured viewport for HTML img" border=0>
<TBODY>
<TR>
<TD align=middle><IMG alt="Gatekeeper features examples"
src="ch04s05.files/gk-table.png" width=496
align=middle></TD></TR></TBODY></TABLE></DIV></DIV>
<P>Guides for basic operation of the above three gatekeepers follow, but
official documentation for these products should be consulted when advanced
functionality and features are required. </P>
<DIV class=sect2 lang=en>
<DIV class=titlepage>
<DIV>
<DIV>
<H3 class=title><A id=d0e3459>4.5.1. Using a Cisco Multimedia Conference
Manager (MCM gatekeeper)</H3></DIV></DIV>
<DIV></DIV>
<P>The Cisco MCM is a software gatekeeper that runs only on Cisco router
hardware with special IOS images (H.323 feature set). One the one hand, this
makes it easy to find a hardware platform for running it within most
organizations that use Cisco hardware, without regard for underlying operating
system support. On the other hand, it does not allow the flexibility of
installing it on any available PC-based server. It is a commercial grade
implementation, mostly geared towards VoIP gateway services and less towards an
open H.323 community of endpoints that possibly spans organization borders. The
MCM supports either direct mode dialing, or full routing mode, through the use
of an included H.323 proxy server. Multiple H.323 zones can be configured and
controlled on one MCM installation, but only in combination with subnet
restriction rules for groups of endpoints. The MCM has good interzone routing
features with DNS gatekeeper discovery as extra and performs great in a
homogeneous "Cisco" environment, but has only basic support for RADIUS based
authentication (by H.323 alias or E.164 and proprietary piggy-back password
mechanism) and no support for LDAP H.350 authentication. "Cisco MCM VC:
Configuring H.323 Gatekeepers" is available <A
href="http://www.cisco.com/en/US/customer/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a0080080a52.html"
target=_top>here</A>. </P>
<DIV class=sect3 lang=en>
<DIV class=titlepage>
<DIV>
<DIV>
<H4 class=title><A id=d0e3467>4.5.1.1. Installation</H4></DIV></DIV>
<DIV></DIV>
<P>Since the Cisco MCM gatekeeper is only an IOS feature (IOS being the Cisco
router operating system), basic IOS installation procedures are sufficient,
assuming a correct IOS image with MCM functionality has been chosen from the
Cisco support site. Two tools can help you choose an appropriate IOS for your
available router, but they are only available to registered users on the Cisco
web site: </P>
<DIV class=itemizedlist>
<UL type=disc compact>
<LI><A
href="http://www.cisco.com/pcgi-bin/Software/Iosplanner/Planner-tool/iosplanner.cgi"
target=_top>Cisco IOS Upgrade Planner</A>
<LI><A href="http://www.cisco.com/pcgi-bin/Support/CompNav/Index.pl"
target=_top>Cisco Software Advisor</A></LI></UL></DIV>
<P></P>
<P>Look for "High-Performance Gatekeeper" under features and for "IP/H.323"
under feature sets. IOS versioning is a subject difficult to follow in itself.
Add to this the fact that the MCM has been undergoing changes during IOS
development and gatekeeper features available on different IOS versions vary
significantly, and finding the right IOS-MCM combination to use for a specific
hardware configuration can become time consuming. Always prefer the latest
available IOS release for your hardware, assuming enough RAM is available to
accommodate it. </P></DIV>
<DIV class=sect3 lang=en>
<DIV class=titlepage>
<DIV>
<DIV>
<H4 class=title><A id=d0e3484>4.5.1.2. Configuration</H4></DIV></DIV>
<DIV></DIV>
<P>Working with the Cisco IOS command line interface does require some
experience with basic commands, modes of operation, loading software images and
configuration files, none of which procedures will be described here in detail.
If you are not familiar with Cisco IOS basic commands, make sure you read an
introductory guide by Cisco. To configure the Cisco MCM, you must establish
command line access (telnet) to the router that runs the "IP/H.323" feature set
and enter privileged (enable command) mode, indicated by the # at the prompt,
before you can enter configuration commands. Enter configuration mode (config
command) and then specify the "gatekeeper" section. In this section, you will
need to enter the MCM configuration commands, as in the sample below, which
merely initializes the gatekeeper operation: </P><PRE class=programlisting>gkp#config
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line. End with CNTL/Z.
gkp(config)#gatekeeper
gkp(config-gk)#zone local gkp.mydomain.org mydomain.org
gkp(config-gk)#no shutdown
gkp(config-gk)#^Z
</PRE>
<P>The above sample is sufficient to start gatekeeper services on the router,
but a more detailed configuration with comments for a basic gatekeeper set-up
follows. We have dropped the command line prompt for simplicity. The following
commands can be typed at the configuration interface, as shown above. Note that
all user-specified fields are indicated as enclosed in brackets and you must
customize/replace them appropriately for your site. </P><PRE class=programlisting>!
! This section goes outside the gatekeeper configuration section
! as it relates to general AAA settings and RADIUS server communication.
! H.323 endpoint RAS registration will be checked against
! local IOS usernames first and then RADIUS defined usernames.
! Accounting records will be sent to RADIUS server.
!
aaa new-model
aaa authentication login h323 local group radius
aaa accounting connection h323 start-stop group radius
!
radius-server host [radius.mydomain.org] auth-port [1812] acct-port [1813]
radius-server key [radius-server-key-as-defined-in-radius-host]
radius-server authorization permit missing Service-Type
!
! Gatekeeper section
!
gatekeeper
!
! Local zone info, as controlled by this gatekeeper
! The zone name "myzone" is for config purposes only and plays no role,
! while the domain is important for endpoints registering by e-mail alias,
! as endpoints that request to be registered by e-mail address must match
! the specified "mydomain.org" part.
! The zone prefix is important for recognizing
! in-zone calls and endpoints, e.g anything beginning with 0030234
!
zone local [myzone] [mydomain.org]
zone prefix [myzone] [0030234*]
!
! To set-up connectivity with other zones and gatekeepers,
! specify the ip of the neighbouring gatekeeper with a "zone remote"
! and the prefix it services with a "zone prefix" for that zone.
! For example, if you know a neighbour gatekeeper handles
! all calls with prefix 0030248, include the following two lines.
!
zone remote [neighb1] [neighb1-domain.com] [neighb1-gkp-ip] 1719
zone prefix [neighb1] [0030248*]
!
! The VideNet gatekeeper for example is the largest global network
! of H.323 zones, to which you can connect as shown below.
! Any calls beginning with 00, are routed to the VideNet gatekeeper.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -