Doing more research I found that the syntax: callto:1234+gateway=192.168.1.40+type=phone should work. Unfortunatelly, I cannot check this. Maybe you should try it and examine the gatekeeper log if there is any evidence of call attempt. ----- Original Message ----- From: "Derek Marcotte" <derek@xxxxxxxxxxx> Sent: Wednesday, June 02, 2004 8:54 PM > > You should definitelly review your config. In particular, > > you should not use [Endpoint] section to register your > gatekeeper with itself;) > > I've removed this. > > > The problem is that your call does not pass through the > gatekeeper (proxy) > > - instead, the originating party sends call directly to the > terminating party. > > But you can try to disable the option > ArjReasonRouteCallToGatekeeper > > - maybe it will help. > > I haven't bothered with this yet... Because the eventual goal is > to run this on our NAT box here, we _need_ it to proxy (from my > understanding). > > > But the real solution is to send calls though the proxy, not > directly to the terminating party. > > Maybe something like: tracker@xxxxxxxxxxxx would work in your > example. You would > > need then to change CallSignalPort=1721 parameter to > CallSignalPort=1720 and enable > > ParseEmailAliases option. Try this with the new 2.0.8 release > or 2.2b4, earlier versions > > may not understand tracker@xxxxxxxxxxxx NM syntax. > > I've switched the CallSignalPort=1720, and have > ParseEmailAliases=1 as well. > > Host Tracker (192.168.1.4) logs into the GK (192.168.1.40), with > the account name trackertest (to eliminate the ambiguity with > hostname) > > Host Derek (192.168.1.3) _does not_ log into the GK > (192.168.1.40) > > I'm running : > tcpdump -pnX "src or dst 192.168.1.40 and not src or dst port > ssh" > > On the gatekeeper. > > Using any of the following URLs: > > callto:trackertest+gateway=192.168.1.40 > callto:trackertest@xxxxxxxxxxxx+gateway=192.168.1.40 > callto:trackertest@xxxxxxxxxxxx > > Or typing trackertest@xxxxxxxxxxxx in the phone number box in > netmeeting, and pressing "call" results in the (eventual) > message: > > "NetMeeting could not find the name of the person you are trying > to call on the directory server. Check to make sure the address > is correct, or change the address type in the Using box." > > And there is no traffic generated to/from the GK during these > trials. > > However, if host Derek does log into the GK as derektest, the > call is completed without a hitch. > > I've omitted the gnugk log this time, nothing (besides the > registration of trackertest) gets logged, becuase the traffic > doesn't go to the GK. I have attached my new gnugk.ini (for > completeness).... > > Thanks for your help thus far Michal! > > Cheers, > Derek > > gnugk netmeeting nat h323 gateway callto routeCallToGatekeeper > ParseEmailAliases > ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
