GNU Gatekeeper Logo

Home
· Download
· Support
· Success Stories
· Imprint

Documentation
· English Manual
· French Manual
· Spanish Manual
· Persian Manual
· Portuguese Manual
· Chinese Manual
· FAQ
· Interoperability
· Intro to H.323
· Usage Examples
· Configuration Notes
· GnuGk and SIP

Tools & Addons
· Java GUI
· ISDN Gateway
· CTI / ACD
· GnuGk Addons
· Endpoints
· Gateways
· MCUs
· IVRs
· Billing
· Commercial Addons

Development
· Compiling
· Development
· NAT Traversal
· Tools
· Authors

Misc
· Events
· Logos
· Recommended Books
· Site Map

Configuring a Swyx Server for GnuGk

Thanks to Roberto Piola for these hints:

It works if I configure the link between Swyx and GnuGk as "locally managed" on the Swyx server, i.e.: if Swyx registers as a gateway on the GnuGk, not if I try to register GnuGk as an endpoint of Swyx (that should act as a gatekeeper). Moreover, the Swyx server must have some registry tweaking:

[HKEY_LOCAL_MACHINE\SOFTWARE\Swyx\LinkMgr\CurrentVersion\Options]
"RemoteServerIsThirdParty"="Yes"

[HKEY_LOCAL_MACHINE\SOFTWARE\Swyx\LinkMgr\CurrentVersion\Options\GeneralLink
Configuration]
"ReplacementL2R_1"="'+999','00999'"
Where the 999 in the replacement string is the prefix I want to use to reach GnuGk from Swyx.

Swyx Server 6.x and 7.x

It appears that Swyx Server version 6.x and up require the name of the H.323 trunk as an additional alias in the Setup message. To add it automatically, GnuGk starting with version 2.3.4 has a new config option:

[EP::TEST-TRUNK]
AdditionalDestinationAlias=TEST-TRUNK

 




Last updated: 03. Mai 2011
Page maintained by Jan Willamowius