hi again, i'm still trying to find a workaround to the alternate gk problem i described earlier. i tried to use neighbors instead of relying on the alternate gk but i had no luch with a client - gk_proxy1 - gk_1/2 - gk_proxy2 - client setup, which is what i need (namely, problems with h245 routing and rtp channel establishment). i i then tried to investigate what was wrong when setting AcceptUnregisteredCalls=1 on gk_proxy ; i found out that the option works as advertised when a client connects directly to gk_proxy, ie. without being registered to any gatekeeper. however, when a client is registered to a gk, and tries to make a call to gk_proxy (eg. with a xxxx@gk_proxy_ip), gk_proxy always rejects the call with the "Warning: socket already attached for callid" msg. i re-tested everything with the site's static version (2.2.1-2) and the latest cvs after the various rtp ports fixes, and with various clients (hardware, ohphone, gnomemeeting) but with no luck any help or pointer to where to look at in the code will be really appreciated... ivan On Mon, 24 Jan 2005 11:27:45 +0200, ivan mitev <ivan.mitev@xxxxxxxxx> wrote: > hi michal, > > i initially thought that calls wouldn't be rejected with > AcceptUnregisteredCalls=1 > > however, a quick test gives (on gk_proxy): > > RasSrv.cxx(168) RAS Read from [gk_1_ip]:1719 > RasSrv.cxx(209) RAS Received ACF > RasSrv.cxx(1238) RAS Trapped ACF > RasTbl.cxx(1969) CallTable::Insert(CALL) Call No. 9, total sessions : 1 > gkacct.cxx(959) GKACCT Successfully logged event 1 for call no. 9 > ProxyChannel.cxx(1342) Q931 Warning: socket already attached for > callid [callid] > gkacct.cxx(959) GKACCT Successfully logged event 1 for call no. 9 > RasTbl.cxx(2140) CDR ignore not connected call > gkacct.cxx(959) GKACCT Successfully logged event 2 for call no. 9 > RasSrv.cxx(221) RAS Send DRQ to [gk_1_ip]:1719 > RasSrv.cxx(168) RAS Read from [gk_1_ip]:1719 > RasSrv.cxx(209) RAS Received DCF > RasSrv.cxx(1238) RAS Trapped DCF > [...] > > i was planning to do a small patch to allow unregistered calls from > the altgk, but the "Warning: socket already attached for callid" > message let me think that it's more complicated than that. > > another little bug is that messages output the ip of gk_1 but a > tcpdump shows that for this call there are only packets from/to gk_2, > and none from/to gk_1 > > let me know if i can help you > > thanks for your help > ivan > > > From: Zygmuntowicz Michal <m@xxxxx> > > Re: bug? : gk as client rejects calls from alternate gk > > > The tricky part here is that the proxy should send > > an ARQ to the actual alternate gatekeeper which > > sent the call. I"ll take a look to see what can be done. > ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
