Michael, you are sending calls to port 1720 on your GnuGk server, but GnuGk still listens to its default port 1721. Add this to your config: [RoutedMode] CallSignalPort=1720 Regards, Jan Michael Bondi wrote: > An update, > > I rebuilt the gnugk on an Ubuntu machine so I could run EtherApe and > Wireshark on the gnugk. > > The gnugk is definitely receiving calls from the WAN if I use > 1234@xxxxxxxxxxxxxx or simply mydomain.co.za, but not passing them to > the LAN endpoint. Etherape shows the call coming in and hitting the > gnugk as well as Wireshark is registering the connect attempt from the WAN. > > When I call from LAN to external IPs I can see the call being proxied by > the gnugk using Etherape > > Wireshark trace attached. 66.8.123.202 is the unregistered WAN endpoint. > > Could someone please correct my config if it is incorrect: > > [Gatekeeper::Main] > Fortytwo=42 > > [GkStatus::Auth] > rule=allow > > [RoutedMode] > GKRouted=1 > H245Routed=1 > AcceptUnregisteredCalls=1 > > [Proxy] > Enable=1 > InternalNetwork=192.168.1.0/255.255.255.0 > > [RoutingPolicy] > default=dns,explicit,internal,parent,neighbor,catchall > > [Routing::CatchAll] > CatchAllAlias=1234 > > [RasSrv::LRQFeatures] > AcceptNonNeighborLRQ=1 > > > Many thanks > > Mike > > > > > > Andrew Struiksma wrote: > > First of all it may be helpful to run WireShark or tcpdump on the gatekeeper to see if you are receiving any packets from the WAN endpoints. Try having your WAN EPs dial just the IP address your GK while watching the packets and see if you get anything. > > > > Secondly, it has been my experience that the <E.164>@<IP address> dialing format does not work for all end points. Actually, for me it only works for xMeeting. You may need to try some alternate dialing strings such as <IP address>##<E.164>. > > > > Andrew > > > > -----Original Message----- > > From: Michael Bondi [mailto:mike@xxxxxxxxxxxxxxxxxxxxxx] > > Sent: Tuesday, October 27, 2009 6:42 AM > > To: GNU Gatekeeper Users > > Subject: Re: Proxy and a single NIC? CatchAll > > > > Simon, > > > > I removed the ExternalIP and ExternalIsDynamic and DefaultDomain settings and the suspect endpoints register fine now, so Problem 1 solved! > > > > Whats more, I can place calls from LAN to WAN no problem. > > > > Problem 2 still exists, I cannot get calls from WAN to reach LAN endpoints. This also affects the catchall/receptionist scenario I am looking for. > > > > I have moved DNS to the front of the routing policy and removed the Cname records for the extensions in the DNS records. > > > > When I make a call to user@xxxxxxxxxxxxxx or 1234@xxxxxxxxxxxxxxx or even just mydomain.co.za or xxx.xxx.xxx.xxx I cannot see anything happening in the trace on gnugk even though AcceptUnregisteredCalls=1 and AcceptNonNeighborLRQ=1 > > > > How do I see if an external call is hitting the gnugk? > > > > Any other pointers? seems I am almost there... -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx 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/
