Hi,
we have more new features in the 2.3.5 development version since my last
update and you are all welcome to test:
- the status port now supports SSH encryption
- H.350 support in H323Plus has been fixed so GnuGk's H.350 feature
should work much better now
- GnuGk now collects H.460.9 QoS statistics as well as RTP statistics
for proxied calls and makes them available through the status port
("PrintEndpointQoS") or Radius
- you can configure GnuGk to send RIP messages in response to ARQs and
LRQs to make the callers wait longer for replies
- a workaround for a VCS bug where it doesn't send the
alternateAliasAddress in a routeCalltoGatekeeper
And there are also a number of bug fixes:
- fix rare crash for H.460.18 calls
- treat empty ExternalIP and NetworkInterfaces settings correctly
- fix setting of the default IP, make sure its include in the
Home= setting, unless explicitly specified in Bind=
- remove callDestSignalAddress from incoming Setup if its the ExternalIP to avoid loops
- populate calledIP field in RouteRequests resulting from ARQs
- jitter values reported through Radius are now in msec (was codec dependent clock rate)
- use PQescapeStringConn() instead of PQescapeString() for PostgreSQL
You can download the current development source code from the CVS.
Please see these notes on compiling
http://www.gnugk.org/compiling-gnugk.html
http://www.gnugk.org/gnugk-manual-14.html#ss14.1
Regards,
Jan
--
Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/
Jan Willamowius wrote:
> Hi,
>
> here is a quick update what is going on in GnuGk development:
>
> Since the 2.3.4 release, a small bug in the bandwidth calculations was
> found and fixed. (I keep hoping for a project that allows me to extend
> the existing bandwidth management to a full blown model with groups and
> zones of endpoints. We'll see.)
>
> Until now call failover used to only retry calls that were ended by the
> remote side. Now the mechanism also covers calls which are released by
> the gatekeeper, because some timeout has expired. So for example if you
> have calls that fail because the remote end doesn't answer at all, those
> will be retried now if you activate failover and have another route for
> this destination.
>
> Another small fix is not to tell endpoints a gatekeeper
> callSignallAddress in the RCF when GnuGk is in direct mode. We've done
> this for ages without any problems, but its just not the right thing to
> do.
>
> All these changes are in the CVS.
>
> Regards,
> Jan
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________________
Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users
Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage: http://www.gnugk.org/
