|
If it’s not easy to fix this problem
in gnugk, you may be able to work around it with proxy ARP. First, verify that a gateway or endpoint
on the 192.168.13.x LAN can register with the GK and call with no problems. Then, set the
NIC on the GK to netmask 255.255.0.0 and configure the router at 192.168.13.249
(Planet ?) to do proxy ARP. When the GK tries to send a packet to 192.168.1.45, it will
think it is on the local LAN and send an ARP request. The router will reply with its
own MAC, the GK will send the RCF to the router, which will forward it to the GW. However,
ExternalIP should not be inserted into the CallSignalAddress, because the GK believes
that the GW is on the local LAN. If your router cannot do proxy ARP, or
your policies prohibit you from using it, you may be able to solve the problem with an
additional router between the GK and the present LAN connection. --Stewart From: Simon Horne
[mailto:s.horne@xxxxxxxx]
----- Original Message ----- Sent: Tuesday, February 06, 2007 5:15 PM Subject: Re: Is it a BUG? Hi Stewart You are quite right! Your offer to locate GK
on the 192.168.1.0/LAN is impossible, cause it is not my locations and i have
not access to it. I think such substitution
the callSignalAddress depending on the InernalNetwork settings is very good
idea and resolve this problem. Best redards. Andrey Shabanov emaito:shabanow@xxxxxxxxxx tel: +7(495)760-35-85 ========================================================================== Hi Simon, Andrey, If I understand the
situation correctly, the GK is on the 192.168.13.0/24 LAN, which is connected to the Internet via a NAT
router, but is also connected to the 192.168.1.0/24 LAN via a non-NAT router. There should be no proxy
needed for calls within or between the two LANs. For calls from/to either
LAN to/from the Internet, the
GK should substitute ExternalIP where needed and, if suitable port forwarding to the GK is configured
on the NAT, it should all work. IMHO, the GK should look
at InternalNetwork to determine when *not* to substitute the value of
ExternalIP into callSignalAddress,
etc. Since setting InternalNetwork=192.168.0.0/16 does not help, perhaps
this is another manifestation
of the problem you describe as fixed in the CVS. Alternatively, would it
be feasible to locate the GK on the 192.168.1.0/24 LAN? --Stewart -------------------------------------------------------------------------------- From: ??????? ??????
?????????? [mailto:shabanow@xxxxxxxxxx]
Sent: Monday, February
05, 2007 10:46 PM To: ' Subject: Re:
Is it a BUG? Cause the VoIP gateways
connected to the GK through the router, the installations of new LAN card to
the GK unfortunately isn’t useful. Will you plan to fix this
problem in the not too distant future? Best redards. Andrey Shabanov emaito:shabanow@xxxxxxxxxx tel: +7(495)760-35-85 -----Original
Message----- From: openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx] On
Behalf Of Simon Horne Sent: Monday, February
05, 2007 8:50 AM To: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Subject: Re:
Is it a BUG? Andrey Remove the Internal
Network entry. It is not required if you are setting the externalIP value. see http://www.gnugk.org/gnugk-manual-5.html#ss5.2 It will automatically
detect the internal network of all interfaces directly connected to the
gatekeeper. Is there a direct
192.168.13.0/24 interface card in the Gatekeeper box. There appears not to be.
You are calling from an internal LAN which is on another LAN which contains
GnuGK connected to the internet. Besides from the difficulty registering you
will also have a lot a difficulty calling as GnuGk will not be able to provide
NAT traversal support to the internal sub LAN so you will have a lot of one way
audio issues and will not be able to call any phone on the 192.168.13.0/24 LAN
from outside. I suggest you add an
interface card for the 192.168.13.0/24 LAN directly to the Gatekeeper box to
ensure it can provide proper call routing and media proxy onto that LAN. There was a problem
calling between two internal LAN's which I fixed in the CVS unfortunately it
did not make the v2.2.5 release. Simon ----- Original Message
----- From: ( ) To: Sent: Monday, February
05, 2007 4:24 AM Subject:
Is it a BUG? VoIP gateway
(ip=192.168.1.45) send RRQ to GNUGK (ip=192.168.13.244). GNUGK has the next rules: [Gatekeeper::Main] ExternalIP=195.94.241.186 Home=192.168.13.244 [RoutedMode] GKRouted=1 H245Routed=1 CallSignalPort=1720 SupportNATedEndpoints=1 TranslateFacility=1 [Proxy] ProxyForNAT=1 Enable=1 ProxyForSameNAT=0 InternalNetwork=192.168.13.0/24 And GNUGK answer
the RCF with its External_IP_address regardless of rules on section [Proxy]
InternalNetwork=192.168.13.0/24 Here is part of packet
decoder: 192.168.13.244
192.168.1.45
H.225.0 RAS: registrationConfirm Ethernet II, Src:
Tackle_GK (00:16:17:41:eb:c3), Dst: 192.168.13.249 (00:30:4f:4c:67:ac) Internet Protocol, Src: 192.168.13.244
(192.168.13.244), Dst: 192.168.1.45 (192.168.1.45) ß-------- User Datagram Protocol, H.225.0 RAS
RasMessage: registrationConfirm (4)
requestSeqNum: 11493
protocolIdentifier: 0.0.8.2250.0.4 (itu-t(0) recommendation(0) h(8)
h225-0(2250) version(0) 4)
callSignalAddress: 1 item
Item 0
Item: ipAddress (0)
ipAddress
ip: 195.94.241.186 (195.94.241.186) ß-----------------!!!!!!!!!!!!
port: 1720
terminalAlias: 5 items
gatekeeperIdentifier: TACKLE_GK
endpointIdentifier: 3348_endp Best redards. Andrey Shabanov emaito:shabanow@xxxxxxxxxx tel: +7(495)760-35-85 -----Original Message----- From:
openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx [mailto:openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx]
On Behalf Of Stewart Nelson Sent: Tuesday, February 06, 2007
10:29 AM To: ' Subject: Re: Is it a BUG? Hi Simon, Andrey, If I understand the
situation correctly, the GK is on the 192.168.13.0/24 LAN, which is connected to the Internet via a NAT
router, but is also connected to the 192.168.1.0/24 LAN via a non-NAT router. There should be no proxy
needed for calls within or between the two LANs. For calls from/to either
LAN to/from the Internet, the
GK should substitute ExternalIP where needed and, if suitable port forwarding to the GK is configured
on the NAT, it should all work. IMHO, the GK should look
at InternalNetwork to determine when *not* to substitute the value of
ExternalIP into callSignalAddress,
etc. Since setting InternalNetwork=192.168.0.0/16 does not help, perhaps
this is another manifestation of
the problem you describe as fixed in the CVS. Alternatively, would it
be feasible to locate the GK on the 192.168.1.0/24 LAN? --Stewart |
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
