Configuring a Quintum Gateway for GnuGk

Quintum gateways as endpoint

To register Quintum as an endpoint into GnuGk you just configure the H323SIG (H323GW for the older series) and then describe the H323ID and IP (depends on your authentication type at GnuGk) of Quintum at the RRQAuth section of Quintum.

Quintum gateways as permanent endpoint

For direct H.225 signaling (a.k.a. "permanent endpoint"), you just setup a static route (sr) in Quintum pointing to GnuGk. Quintum also allows you to change the call signaling port the other side accepts requests on.

On the GnuGk side you allow GnuGk to accept calls from unregistered endpoints and describe the IP of Quintum as a permanent endpoint.

Here is a sample Quintum config for a permanent endpoint:

config h323gw# print
print
Primary GK Address = 62.176.125.74
Primary Auto Discovery = 0
Secondary GK Address = 0.0.0.0
Secondary Auto Discovery = 0
H.323 ID = quintumlv
Register DN = Register as GW Prefixes(1)
Ignore Bandwidth in ACF = no(0)
Default H245 Tunneling = yes(1)
Round Trip Delay = 0
One Stage Dialing = 0
RRQ Interval = 300
H323 Interop Flags:
        H225 GW Protocol = h323(0)
        Do BRQ = 1
        SlaveSessionId0 = 0
        AllowFastStartOnly = No(0)
        RRQv3plus= No(0)
        ProgressInd Alert= No(0)
        StartH245Flag= Yes(1)
        Automatic Ext IP Update= No(0)
Do Lightweight RRQ = yes(1)

Quintum gateway as neighbor

For LRQ (remote zone routing) you set again a static route, but configure the type of route as gatekeeper, not gateway. In GnuGk you set the IP of Quintum as a neighbor.

In Quintum: config -> be - sroute 1 define a static route for your calls to GnuGk and set gkmode to 1 (destination is a gatekeeper)

Last updated: 25. Dec 2020