introduction.sgml

gnugk软交换产品

<item>
Nouvelle option de configuration <tt/RoundRobinGateways/.

<item>
Limites de capacit&#233; d'appel et routage des priorit&#233;s pour les passerelles.
Nouvelles sections de configuration <tt/EP::/ pour des param&#232;tres de configuration
par terminal (voir
<ref id="epconfig" name="Per-Endpoint Configuration Settings">).

<item>
RTP proxy handling moved to a separate RTP proxy threads, so processing
of signaling messages does not block RTP packets. New <tt/RtpHandlerNumber/ 
config option.

<item>
REUSE_ADDRESS option enabled on listening sockets in non-LARGE_FDSET mode 
to fix a bug with the gatekeeper being unable to open listening ports after
restart.

<item>
Ability to set call destination in auth modules. RADIUS based call routing.

<item>
Support for SqlBill tariff table import from an OpenOffice.org Calc spreadsheet.

<item>
Fixed sourceInfo LRQ field handling - now it contains an H.323 identifier 
of the gatekeeper. Nonstandard data and gatekeeperIdentifier fields are set
only when the neighbor is defined as GnuGk.

<item>
Ability to set shared secrets for each radius server separatelly.

<item>
New, much faster, Radius client implementation.

<item>
Called-Party-Number-IE rewrite occured too late, causing auth/acct modules 
to receive the original number instead of the rewritten one.

<item>
Fixed proxying of RTP packets, so RTP sockets are not closed on temporary 
errors (like remote socket not yet ready). This bug affected especially 
NAT traversal and situation, when audio was sent very early, when reverse 
proxy path has not been yet established.

<item>
Fixed handling of RRJ from an alternate GnuGk.

<item>
New direct SQL accounting module (<ref id="sqlacct" name="[SQLAcct]">).

<item>
Handling multiple reply messages (RIP/LCF/LRJ) from neighbors fixed.

<item>
Support for CallCreditServiceControl in RCF and ACF messages, which allows
reporting call duration limit and user's account balance to endpoints. 
Currently RadAuth and RadAliasAuth modules support this feature.

<item>
Log file rotation, new <tt/LogFile/ config section, new <tt/setlog/ 
and <tt/rotatelog/ status interface commands.

<item>
Do not include an invalid access token (with null object identifier) 
in LCF to prevent interoperability problems.

<item>
Better handling of multiple calls over a single signalling channel 
by setting multipleCalls and maintainConnection H.225.0 fields to FALSE 
in all messages passing through the gatekeeper.

<item>
Better User-Name, Calling-Station-Id and Called-Station-Id handling.

<item>
IncludeEndpointIP flag for RadAuth, RadAliasAuth and RadAcct is obsolete,
these modules will always send Framed-IP-Address.

<item>
New Gatekeeper::Auth flag SetupUnreg to toggle Q.931 Setup authentication
for unregistered endpoints only.

<item>
New RADIUS h323-ivr-out=h323-call-id parameter that contains 
an H.323 Call Identifier.

<item>
The SQL billing from the contrib section can now authenticate users only 
by their IP (ignoring User-Name) and has a new, more flexible tariff/rating 
engine.

<item>
RadAliasAuth can authenticate now Setup messages without sourceAddress
field present (it will use Calling-Party-Number instead).

<item>
Better signal handling to prevent accidental gatekeeper crashes 
(due to SIGPIPE, for example).

<item>
CDR rotation per number of lines works correctly.

</itemize>

<p>

Of course, the major functions in version 2.0 are also included:
<itemize>
<item>
The registration table and call record table are redesigned, thread-safe,
and very efficient. Support ten thousands of registrations and thousands of
concurrent calls.

<item>
A new routed mode architecture that support H.225.0/Q.931 routed and
H.245 routed without forking additional threads. Thus the thread number
limit will not restrict the number of concurrent calls.

<item>
Support H.323 proxy by routing all logical channels, including RTP/RTCP
media channels and T.120 data channels. Logical channels opened by H.245
tunnelling and fast-connect procedure are also supported. In proxy mode,
there is no traffic between the calling and called parties directly. Thus
it is very useful if you have some endpoints using private IP behind an
NAT box and some endpoints using public IP outside the box.

<item>
Support gatekeepers cluster by exchanging LRQ/LCF/LRJ (neighboring function).
If the destination of a received LRQ is unknown, the GnuGk can forward it
to next hop. Therefore the GnuGk can work as a directory gatekeeper.

<item>
Support various authentication methods for selectable RAS requests, including
H.235 password (MD5, SHA-1 and CAT), IP pattern and prefixes matching. MySQL and
LDAP are supported as backend database for authentication.

<item>
Support alternate gatekeepers for redundancy and load balancing. If the
GnuGk is overloaded, the endpoints can be redirected to other gatekeepers.

<item>
Can work as an endpoint (gateway or terminal) by resigtering with a parent
gatekeeper. With this feature, building gatekeeper hierarchies is easily.

<item>
Monitor and control the GnuGk via TCP status port, including registration
and call statistics.

<item>
Output CDR(call detail record) to status port for backend billing system.
The CDR contains call identifier, calling and called IP, start and end time
and call duration.

<item>
Most configurations are changeable at runtime. The GnuGk rereads the
configurations on receiving <tt/reload/ command via status port, or on
receiving <tt/HUP/ signal (Unix platform).
</itemize>

<sect1>T&#233;l&#233;chargement
<label id="download">
<p>
La derni&#232;re version stable et une version de d&#233;veloppement sont disponibles sur
<url url="http://www.gnugk.org/h323download.html" name="la page de t&#233;l&#233;chargement">.

La toute derni&#232;re version du code source est sous CVS sur
<url url="http://sourceforge.net/cvs/?group_id=4797" name="Sourceforge">
(<url url="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/openh323gk/" name="Web-GUI">).
Attention - il s'agit de la pointe de la technologie.

Vous pouvez aussi t&#233;l&#233;charger certains ex&#233;cutables depuis
<url url="http://www.gnugk.org/h323download.html" name="la page de t&#233;l&#233;chargement">.

<sect1>Liste de Diffusion
<p>
Il y a deux listes de diffusion pour le projet, une pour les d&#233;veloppeurs et une pour les utilisateurs.

Les questions d'ordre g&#233;n&#233;ral doivent &#234;tre envoy&#233;es &#224; la
<url url="mailto:[e-mail]" name="liste de diffusion des utilisateurs">.
Vous pouvez trouver les archives de la liste
<url url="http://sourceforge.net/mailarchive/forum.php?forum_id=8549" name="ici">.
Pour vous joindre &#224; cette liste de diffusion, cliquez
<url url="http://lists.sourceforge.net/lists/listinfo/openh323gk-users" name="ici">.

Pour signaler des probl&#232;mes ou des anomalies/patches, envoyer des mails &#224; la
<url url="mailto:[e-mail]" name="liste de diffusion des d&#233;veloppeurs">.
Les archives de la liste sont
<url url="http://sourceforge.net/mailarchive/forum.php?forum_id=3079" name="ici">.
Veuillez envoyer les questions utilisateur &#224; la liste de diffusion des utilisateurs et garder cette liste pour le d&#233;veloppement! Si vous voulez contribuer au projet, veuillez
<url url="http://lists.sourceforge.net/lists/listinfo/openh323gk-developer" name="rejoindre la liste de diffusion">.

<bf/Note/:
Merci de ne pas envoyer vos questions par des mails priv&#233;s aux d&#233;veloppeurs.
Nous sommes habituellement occup&#233;s. Nous ne voulons <bf/pas/ &#234;tre votre
consultant personnel, &#224; moins que vous souhaitiez nous payer.
Envoyez vos probl&#232;mes &#224; la liste de diffusion appropri&#233;e de telle
sorte que tout le monde puisse vous aider.

Merci aussi de ne pas envoyer les probl&#232;mes sp&#233;cifiques de GnuGk &#224;
la liste de diffusion OpenH323, ou vice versa.
Il s'agit de projet distincts, bien que tr&#232;s apparent&#233;s.

Avant d'envoyer un mail, assurez-vous d'avoir lu les documents associ&#233;s
m&#233;ticuleusement. D&#233;crivez votre probl&#232;me clairement et avec pr&#233;cision.
Montrez nous les messages d'erreur ou les logs si il y en a.

<sect1>Participants
<p>
Le coordinateur actuel du projet est
<url url="http://www.willamowius.de/" name="Jan Willamowius">
<tt><htmlurl url="mailto:[e-mail]" name="&lt;[e-mail]&gt;"></tt>

Les principales caract&#233;ristiques et fonctions de la version 2.0 ont &#233;t&#233;
contribu&#233;es par
<url url="http://www.cwhuang.idv.tw/" name="Chih-Wei Huang">
<tt><htmlurl url="mailto:[e-mail]" name="&lt;[e-mail]&gt;"></tt>
et
<url url="http://www.citron.com.tw/" name="Citron Network Inc.">,
incluant l'enregistrement et les tables d'appel thread safe,
une nouvelle architecture de mode rout&#233;, proxy H.323,
authentification H.235 et MySQL backend.

Michal Zygmuntowicz <tt><htmlurl url="mailto:[e-mail]" name="&lt;[e-mail]&gt;"></tt> a fait du bon travail sur le support de Radius et d'autres am&#233;liorations.

La version initiale de gatekeeper a &#233;t&#233; d&#233;velopp&#233;e par
Xiang Ping Chen, Joe Metzger et Rajat Todi.