I am having a similar problem: I have a GK and 3 GW registered against it and some ATA's Registered. Too I have another GK with same GW as permanent EndPoint and other ATA's registered. When a place a call from ATA on 1st GK, all is OK. But, when I place a call from ATA on 2nd GK, it obviusly send call to GW, and EVER call is unconnected after 160-170 secs. Too, I don't know why, I can see trhough status port on 1st GK calls made from 2nd GK, but without CALLER-IP. Somebody can help me?.. I don't know why call is unconnected on 2nd GK after 160-170 secs. -----Mensaje original----- De: openh323gk-users-admin@lists.sourceforge.net [mailto:openh323gk-users-admin@lists.sourceforge.net] En nombre de James Lertora Enviado el: Miércoles, 26 de Noviembre de 2003 10:55 a.m. Para: openh323gk-users@lists.sourceforge.net Asunto: RE: Calls drop after 3 mins Michal, We are running : GKRouted=1 H245Routed=1 So I should check to see if the GK is getting a connect message back. Thanks! James Lertora Technical Support Patton Electronics Reply /=\=/=\=/=\=/=\=/=\=/=\=/=\=/ 0101010101010101010101010101010101 \=/=\=/=\=/=\=/=\=/=\=/=\=/=\ -----Original Message----- From: openh323gk-users-admin@lists.sourceforge.net [mailto:openh323gk-users-admin@lists.sourceforge.net] On Behalf Of Zygmuntowicz Michal Sent: Tuesday, November 25, 2003 7:35 PM To: openh323gk-users@lists.sourceforge.net Subject: Re: Calls drop after 3 mins Another reson can be that the gatekeeper somehow does not know the call has been connected (Connect message received). Default timeout to disconnect not connected calls is 180s. What does the status line shows after '!' command (the last two numbers are call duration and timeout). Make sure you did not set DefaultCallDurationLimit parameter to 180. Is the gatekeeper running signalling routed mode? ----- Original Message ----- From: "James Lertora" <jlertora@patton.com> Sent: Wednesday, November 26, 2003 12:17 AM > Yeah, the trace showed the GK ending the call. > I did play around with the TTL, but did not think this could affect > it. It is pretty consistent regarding the time, so it might not be the > RTCP. Our gateways (smart nodes) request 90 seconds when registering > with the GK. I read that if you set the TTL higher than requested by a > gateway then the GK will default to 60secs thus it seemed to cause > lots of RRJ requiring full registrations. It is strange that the TTL > is set to 90 and the hang-up is happening at twice that. Hmm.. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/ ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id?49 Homepage: http://www.gnugk.org/ ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id?49 Homepage: http://www.gnugk.org/
