According to the child-parent GK setup problems discussed recently,
I made the following test scenario:
EP1---------------------GK1-------------NATBOX--------------GK2-------------------------EP2
192.168.3.112 192.168.3.114 192.168.3.1/213.x.x.x 213.y.y.y.y 213.z.z.z
[77771] CHILD PARENT
[zvision]
Proxy=0 Proxy=0
ProxyForNAT=0 ProxyForNAT=1
GKRouted=1 GKRouted=1
InternalNetwork=192.168.3.0/24
AcceptUnregisteredCalls=0 AcceptUnregisteredCalls=0
AcceptNeighbourCalls=1
Prefixes=7777
EP1 is a H.323 endpoint that is NAT aware (e.g. is sending/receiving rtp streams on a single
socket), so it can work through NAT without proxy. It is registered with alias "77771".
GK1 is a child gatekeeper placed on a machine with private IP (single eth interface) behind NAT box.
NAT box is a typical symmetric NAT that allows only return-path traffic to rach private network.
GK1 is configured without proxy and proxynat features. If EP1 would not be NAT aware, then Proxy=1
should be specified, in order to proxy rtp traffic. No neighbour sections are setup, [Endpoint] section
contains "Prefixes=7777". It is important to enable "AcceptNeighbourCalls=1".
GK2 is a parent gatekeeper placed on a machine with public IP. It has Proxy disabled, ProxyNAT enabled.
In this scenario both outgoing (from 77771 to zvision) and incoming (from zvision to 77771) calls
are working very well.
A few important notes:
*) child GK has to have AcceptNeighbourCalls enabled, otherwise calls routed from parent GK
will be rejected;
*) if endpoints behind NAT box are NAT aware, there is not need to enable neither Proxy not ProxyNAT;
*) parent GK has to have ProxyNAT enabled, otherwise child-parent calls are not proxied at parent GK
and child GK will not spawn NAT handling thread, so no incoming calls will be possible at child GK;
*) child GK (and its endpoints) must be configured with E164-like numbering plan and prefix(-es).
Either by specifying "Prefixes" option for child GK and AcceptGatewayPrefixes for parent GK
or RasSrv::GWPrefixes for parent GK. Otherwise endpoints registered with child GK will not be
reachable from parent GK;
*) no neighbour sections should be set up at parent GK.
Question:
If I would like to setup child GKs and route calls based on h323id, not E164 prefix I need to
setup childs as neighbour GKs, to force parent GK to send LRQ to child GKs.
After LCF is received should not parent GK check if destination call signal address does not
refer to registered child GK and checked if signalling should not be sent using NAT handling thread?
Regards:
---
Zygmuntowicz Michal
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
List: Openh323gk-users@lists.sourceforge.net
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/
