LRJ to non-GnuGK gatekeeper

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

I’ve been using GnuGK for few months, so I apologise if his question
has been answered.

The setup we use is as follows: 

Phone_1 --> GK1 --> GK2 --> GK3 --> Phone_2

GK1 is the gatekeeper of my LAN, works in proxy mode (GnuGK 2.2
stable, built on Pandora Release of PWLib and OpenH323). It has only
one neighbour in its configuration, GK2.

GK2 is my main gatekeeper (GnuGK 2.2 stable, built on Pandora Release
of PWLib and OpenH323). It has 2 neighbours in its configuration –
GK1 and GK3.

GK3 is my VoIP provider’s gatekeeper, Netcetrex. 

When Phone_1 calls Phone_2, everything works fine: GK1 receives ARQ
from Phone_1, sends LRQ to GK2, GK2 sends LRQ to GK3, GK2 receives LCF
from  GK3, sends it back to GK1, GK1 sends ACF to Phone_1, call is established.

When Phone_2 tries to call Phone_1, GK2 receives LRQ message from GK3,
but instead of sending LRQ to GK1, it immediately returns LRJ.

The configuration file of GK2 does not set any authorisation
requirements for LRQ messages. The gnugk.log (at "debug trc 3") does
not show any activity which could lead to rejection:

--- gnugk.log ---
2004/11/23 18:17:33.591 2   RasSrv.cxx(152)   RAS     Read from 82.147.143.5:1719
2004/11/23 18:17:33.592 2   RasSrv.cxx(193)   RAS     Received LRQ
2004/11/23 18:17:33.592 1   RasSrv.cxx(312)   RAS     LRQ Received
2004/11/23 18:17:33.593 2   RasSrv.cxx(357)   LRJ|82.147.143.5|10007035924007706:dialedDigits|NETCENTREX|requestDenied;
2004/11/23 18:17:33.593 2   RasSrv.cxx(205)   RAS     Send LRJ to 82.147.143.5:12004
--- /gnugk.log ---

I noticed that the LRQ message of GK3 (Netcetrex) differs from the LRQ
message of GK1 (GnuGK) in two main things (full messages are listed below)

1. The GnuGK includes two "canMapAlias" lines – first one set to
"tue", second one set to  "false" while Netcentrex has only one, set
to "false".

2. The GnuGK includes a hopCount parameter while Netcentrex does not.

Understanding that missing hopCount could trigger GK2 to send LRJ
without any investigation, I tried setting the "AlwaysForwardLRQ" to
"1" inside its configuration. (The GnuGK Manual states that: "Force
the gatekeeper to forward an LRQ even if there is no hopCount in the
LRQ"). However, this did not change the behaviour of GK2.

I’ve seen the same problem reported back in 2002, but did not find any
proposed solution:

http://sourceforge.net/mailarchive/message.php?msg_id=1961932

Actually, there is a workaround: if GK1 get registered with GK2 as an
Endpoint, specifying its own prefixes, the calls go fine both ways.

However,  I still believe the problem should have a solution
based entirely or LRQ messaging.

Below are the two LRQ messages and the relevant part of the GK2
configuration file.

Thanks in advance for any ideas.

Assen Totin
Development Manager
Bulgaria Online

---

gnugk.ini on GK2 (IP addresses & passwords obscured for security reasons):

[RasSrv::Neighbors]
# The GK-Uplink-1 is actually Netcentrex,
# so Cisco seems to be our best bet for it
GK-Uplink-1=CiscoGK
GK-Customer-1=GnuGK

[Neighbor::GK-Uplink-1]
GatekeeperIdentifier=Uplink-Id
Host=a.b.c.d
Password=some_password
SendPrefixes=*
AcceptPrefixes=*
ForwardHopCount=5
NeighborTimeout=5
AlwaysForwardLRQ=0
AcceptForwardedLRQ=1
IncludeDestinationInfoInLCF=1
ForwardResponse=1

[Neighbor::GK-Customer-1]
GatekeeperIdentifier=OnlineBG-Winstar
Host=a.b.c.d
Password=some_password
SendPrefixes=100070359240077
AcceptPrefixes=*
ForwardHopCount=10
NeighborTimeout=5
AlwaysForwardLRQ=0
AcceptForwardedLRQ=1
IncludeDestinationInfoInLCF=1
ForwardResponse=1

---

The GnuGK (GK1) LRQ received at GK2:

locationRequest {
    requestSeqNum = 5
    destinationInfo = 1 entries {
      [0]=dialedDigits "3592180"
    }
    nonStandardData = {
      nonStandardIdentifier = object
      data =  11 octets {
        47 4b 2d 55 70 6c 69 6e  6b 2d 31                  GK-Uplink-1
      }
    }
    replyAddress = ipAddress {
      ip =  4 octets {
        d9 4b 80 2a                                        .K.*
      }
      port = 1719
    }
    sourceInfo = 2 entries {
      [0]=h323_ID  11 characters {
        0041 0073 0073 0065 006e 0020 0054 006f   Assen To
        0074 0069 006e                            tin
      }
      [1]=dialedDigits "10007035924007704"
    }
    canMapAlias = TRUE
    gatekeeperIdentifier =  16 characters {
      004f 006e 006c 0069 006e 0065 0042 0047   OnlineBG
      002d 0057 0069 006e 0073 0074 0061 0072   -Winstar
    }
    hopCount = 5
    canMapSrcAlias = FALSE
  }

---

The Netcentrex (GK3) LRQ received at GK2:

locationRequest {
    requestSeqNum = 57045
    destinationInfo = 1 entries {
      [0]=dialedDigits "10007035924007706"
    }
    nonStandardData = {
      nonStandardIdentifier = h221NonStandard {
        t35CountryCode = 181
        t35Extension = 0
        manufacturerCode = 18
      }
      data =  21 octets {
        83 04 80 11 00 0a c5 f0  9a 3c a4 11 d9 85 05 f5   .........<......
        4d 17 f7 7c 34                                     M..|4
      }
    }
    replyAddress = ipAddress {
      ip =  4 octets {
        52 93 8f 05                                        R...
      }
      port = 12001
    }
    sourceInfo = 1 entries {
      [0]=dialedDigits "359898665463"
    }
    canMapAlias = FALSE
    gatekeeperIdentifier =  10 characters {
      004e 0045 0054 0043 0045 004e 0054 0052   NETCENTR
      0045 0058                                 EX
    }
  }





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

_______________________________________________________

List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id…49
Homepage: http://www.gnugk.org/


[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux