Did you specify RTPPortRange? I just tested the latest cvs and it is working fine (excluding a scenario when RTPPortRange is not specified, as there is a bug with port allocation). If setting RTPPortRange does not help, try to check the log.
----- Original Message ----- From: "Artur Yakupov" <artur@xxxxxxxxx>
Sent: Monday, January 24, 2005 9:56 AM
No, I have`nt any firewall (iptables stop). Yes, 2.2.1 work fine and the latest cvs not.
ZM> Do you have a firewall? We changed default RTP port ZM> range to be dynamic (OS allocated). ZM> I am also confused about which version works fine ZM> and which not. Does the 2.2.1 work fine and the latest cvs not?
Problem description:
My GK works perfect.
Gatekeeper(GNU) Version(2.2.1) Ext(pthreads=1,radius=0,mysql=0,pgsql=1,large_fdset=32768) Build(Jan 12
2005, 12:51:51) Sys(Linux i686 2.4.26-std-smp-dartel9)
But latest cvs (I tried it) seems has a bug - I can't hear any voice while signalling is ok.
------------------------------------------------------- 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/
