Piyush
The ports to forward for call signalling is TCP 1720 not 1730.
Make sure your INI port ranges reflex the port forwards.
Port Forwards
UDP 1719 RAS
TCP 1720 Q931 (Incoming call)
TCP 30000 - 32000 H245 & Q931
UDP 50000 - 60000 RTP/RTSP
INI entries
[Gatekeeper::Main]
Fortytwo=42
ExternalIP=x.x.x.x
[RoutedMode]
CallSignalPort=1720
Q931PortRange=30000-30999
H245PortRange=31000-31999
[Proxy]
Enable=1
RTPPortRange=50000-59999
Simon
From: Piyush Verma [mailto:[email protected]]
Sent: 25 June 2011 23:33
To: [email protected]
Subject: [Openh323gk-users] gk behind NAT
Dear All,
I have spent ed 1.5 day's to configure gnugk without success.
I have installed gnugk on a server behind NAT.
I have forwarded 1 to 1730 and 30000 to 60000 to the server.
I am able to connect ssh which ensure that port forwarding is working
properly.
I am able to connect to GK from local ip like 192.168.1.35.
But I am unable to connect to same GK using public ip.
I have using NAT.ini and gatekeeper.ini and updated public IP.
Any idea what step I am missing ?
--
Thanks & Regards
Piyush Verma
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________________
Posting: mailto:[email protected]
Archive:
http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users
Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage: http://www.gnugk.org/
