If H.245 is tunneled, the limit is 32 calls per signaling thread, but a lot of video endpoints don't use tunneling and then each thread also needs 2 sockets for the H.245 connection and the limit goes down to 16 calls. Just set CallSignalHandlerNumber to 10 and you should be fine. Regards, Jan -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ pierlu wrote: > Well, that's the point probably. I'm using Windows 2003 for GnuGk. It > was the server on which Radvision gatekeeper run before I switched it > off and used GnuGk instead. > But, if CallsignalHandlerNumber is default to 5 and each thead can > handle 32 calls, shouldn't be the limit of concurrent calls 160? Why > 80? > But 80 is half 160 so this makes sense. So if I set it up to 6 I can > expect to raise the limit to 96 concurrent calls? > Thanks, p. > > On Thursday, April 14, 2011, Jan Willamowius <jan@xxxxxxxxxxxxxx> wrote: > > Hi, > > > > let me guess: You are using Windows and didn't increase the > > CallSignalHandlerNumber ? Then you are probably just running out of > > sockets. The Windows limit per thread is ridiculously low. > > > > Regards, > > Jan > > > > -- > > Jan Willamowius, Founder of the GNU Gatekeeper Project > > EMail : jan@xxxxxxxxxxxxxx > > Website: http://www.gnugk.org > > Support: http://www.willamowius.com/gnugk-support.html > > > > pierlu wrote: > >> Hi, > >> > >> today I run in a limit I was not prepared to encounter. > >> > >> I was managing a large videoconference and I could not go past 80 > >> concurrent calls. I understood that because I had one set top box who > >> could not join the conference: I tried everything that I could to make > >> it so but it succeeded only when I had the idea of disconnecting my > >> own client, the one I use for monitoring. Once the set top box was > >> able to join the conference, it was the turn for my endpoint to be > >> unable to join the conference. > >> The error I received back was "Error Q.931" and on the status port it > >> was listed that the call was normally dropped. > >> > >> I cannot read the log file to give more precise insight about the > >> problem cos it's 446Megs (I guess it's becouse I had some issues with > >> an ISDN gateway which resulted in massive output to the status port > >> and so to the log file) and any software I normally use to view log > >> files refuse to open it due to memory limits. > >> > >> May it be something related to GnuGk configuration? As far as I can > >> tell, it's set so that only signalling is routed thru the GnuGk (to be > >> able to disconnect calls between endpoints via telnet), so I don't > >> think it's bandwidth related (moreover cos there were 5 mcus cascaded > >> in the conference so that connections were balanced among them and I > >> had troubles with connecting to any of the 5 mcus once concurrent > >> calls reached the 80 limit). > >> > >> Do you have any suggestion of what I may look into to go past this > >> limit? I can reproduce this situation only during a real meeting, it's > >> impossible to arrange a test with more than 80 clients, so I need to > >> have an idea of what this problem may be before allowing again a > >> conference with more than 80 clients. > >> > >> I'm using GnuGk 2.3.3 (it works well and I try to stick to the "if it > >> ain't broke don't fix it" rule). > >> > >> The relevant sections of the ini file are listed below. I have to > >> mention that I am no expert in h.323 so I have taken the routed > >> directives from the examples found in the online manual. > >> > >> Thanks for any help. > >> > >> Cheers, pierlu > >> > >> ---------------------------------------------------------------------------------------------------------- > >> > >> [Gatekeeper::Main] > >> FortyTwo=42 > >> Name=GnuGk > >> Home=10.1.12.43 > >> Bind=10.1.12.43 > >> TimeToLive=600 > >> StatusTraceLevel=2 > >> TraceLevel=5 > >> > >> [RoutedMode] > >> ; enable gatekeeper signaling routed mode, route H.245 channel only if > >> neccessary (for NATed endpoints) > >> GKRouted=1 > >> H245Routed=1 > >> AcceptNeighborsCalls=1 > >> AcceptUnregisteredCalls=1 > >> CallSignalPort=1720 > >> > >> ; proxy calls only for NATed endpoints > >> [Proxy] > >> Enable=0 > >> ; if port forwarding is correctly configured for each endpoint, you > >> can disable ProxyForNAT > >> ProxyForNAT=1 > >> ProxyForSameNAT=0 ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________________ 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/
